Project FOSSIL (v1.0): Use MV plugins in MZ! 300+ plugins Fossilized!

Restart · 2021-04-16T09:31:04+0900

Project FOSSIL V1.0 By: FOSSIL TEAM Introduction Project FOSSIL (Fixing Old Software / Script Interoperability Layer) is a single RPG Maker MZ plugin designed to expand the use and usefulness of RPG MAKER MV plugins, by allowing them to work in RPG MAKER MZ projects. FOSSIL doesn't port plugins. FOSSIL makes porting unnecessary! I got a copy of RPG Maker MZ a little while ago, and I think the editor is even better than RPG Maker MV. The only problem is that it's competing with RMMV's deep library of plugins. MV had such a huge number of great plugins (thanks to the tireless work of Yanfly, Moghunter, SRD, Galv, and too many other authors to list here) that it will be a long time before they all get rewritten to work with the new engine. I decided to try to figure out a way to speed things up. Instead of having to change every single MV plugin to work with MZ, I'm going to see if we can change MZ so it can work with the old plugins, and still keep all the engine upgrades. That way, we'll have the best of both worlds. What I came up with was FOSSIL. FOSSIL does basic interoperability things - it makes MZ able to understand commands from old MV plugins. For instance, when you make a window in MZ, the engine expects you to hand it a single 'rectangle' which tells it exactly where the window should go, and how big it should be. In MV, when you make a window, what you hand the engine can be very different - it might just be 'how many lines of text there are in this window', or it could be 'the x coordinate, y coordinate, width, and height'. Before any of those commands get to the core engine, FOSSIL converts them into the rectangle that MZ expects. That way, you don't have to actually change how the plugin tries to create a window - FOSSIL just translates it into terms MZ can understand, and then it's fixed everywhere. Plus, this way, we can make old MV plugins work in MZ while still respecting any licensing they have. Instead of having to track down people who might have left the community, and asking them if we can copy their plugin and make a changed version, we can just use FOSSIL and make MZ understand what the plugin is trying to do. I have tried my best to minimize any side-effects from FOSSIL's existence. In my test projects there weren't any noticeable changes, but it's entirely possible I accidentally broke something. If that's the case, please post about it in this thread. I'm super excited about the possibilities with FOSSIL, and I hope a lot of people join in (hence why I'm crediting FOSSIL TEAM). I don't want this to be 'my' plugin, I want the whole community to be able to use all the MV and MZ plugins with the newest engine, and I think everyone here who makes MV plugins knows enough to help improve it. How to Use FOSSIL is a single plugin that must go at the beginning of your plugin list. There are no settings to tweak. Since FOSSIL isn't a port, you still need to have the original, unaltered MV plugins, and put them into your game as usual. So far I have tested over three hundred working plugins (see list), and there's a good chance that even if they aren't listed, most simple plugins will just work 'out of the box' with no tweaks. How to Write a Fix for Fossil FOSSIL now automatically detects where plugins are in the list, and applies patches directly before or after the appropriate plugin. For example, WAY_Core needs us to back up the plugin manager commands before WAY_Core actually runs and changes them. Since we need to run the code before WAY_Core executes, this requires a PreFix. Here's the code in FOSSIL that makes that happen: Code: Fossil.loadPreFix('WAY_Core',function() { Fossil.backupPluginManagerCommands=PluginManager._commands; }) //^ see that closing bracket and parenthesis? //That's important not to forget. The 'WAY_Core' parameter in loadPreFix tells FOSSIL which plugin it should be looking at. The code for the fix itself is within the function: Code: function() { Fossil.backupPluginManagerCommands=PluginManager._commands; } Because this is loadPreFix, the code will be run just before WAY_Core is executed. If you need to be before multiple plugins, you can list all of them in an array ['pluginA','pluginB','pluginC'], and it will run immediately before the first one in plugin order (ignoring plugins that aren't in your project). If we use loadPostFix instead, the code would be run immediately after WAY_Core. (And listing multiple plugins in loadPostFix will result in applying the fix immediately after the last one in the list). Plugin Order There is only one order possible: 1) FOSSIL.js (First plugin) 2) All other plugins. Other than that, put the plugins ordered the same way you'd put them in MZ or MV. Put plugins that extend each other together like usual. I can't really give more specific instructions than that, it'll all be on a case-by-case basis as normal. Using Old Plugin Commands You have three ways of using plugin commands for MV projects A: use the built in plugin comman…

● ARCHIVED · READ-ONLY

Started by Restart Apr 16, 2021, 12:31 AM 603 posts Page 4 of 31 View original ↗

PandaDance

#61 Apr 25, 2021, 06:36 PM Source

OH! Will try that now! Results soon!
PandaDance

#62 Apr 25, 2021, 06:51 PM Source

Thank you so much for helping out a Github newb! That fixed that error!

The plugins now throw no console errors. The texts shakes! But, this is what my text looks like now:

The error is coming from VisuMZ_1_MessageCore plugin; when I deactivate it, shaking text works fine. But I need MessageCore for other things! Is there any way to have both work?

For reference, here is how I have my plugins arranged:

Thank you so much!

EDIT: Put up easier-to-read screenshot.
PandaDance

#63 Apr 25, 2021, 07:08 PM Source

I tried to live without MessageCore and just use YEP's wordwrap etc. functions, but couldn't figure out what to enable/disable to get them to play nicely. Hoping, having gotten this far, it won't be too hard to get this working all the way!
Restart

#64 Apr 25, 2021, 07:55 PM Source

Well we're getting closer, anyway. I'm guessing that these plugins are conflicting with each other when trying to parse the escape characters. I don't have any VS plugins so it's going to be difficult to debug (and unfortunately YEP message core's wordwrap still isn't working, which I assume is a big feature for you)

I'll see if I can make a skinny shaketext module and see if that interferes less.

EDIT: actually, looks like I can just incorporate the things I need into Fossil_Pre and Post without a dedicated module. Try it now.
Neosss19

#65 Apr 26, 2021, 05:32 AM Source

Restart said:
I should have it working, try it now. Basically it was choking on finding the default font.

can you link me to the plugin, and a demo of it working in MV?

Sorry for the delay, but here you go.
The JS script = https://www.mediafire.com/file/otjic3nxffqgxyj/SRD_ShakingText.rar/file
And demo proyect = https://www.mediafire.com/file/wnxjodbw72cfil4/Project2.rar/file
Restart

#66 Apr 26, 2021, 05:38 AM Source

Neosss19 said:
Sorry for the delay, but here you go.
The JS script = https://www.mediafire.com/file/otjic3nxffqgxyj/SRD_ShakingText.rar/file
And demo proyect = https://www.mediafire.com/file/wnxjodbw72cfil4/Project2.rar/file
ah it's the SRD shakingtext? Try it now, I just got it working for panda (if you have visuastella message also installed apparently word wrap in that conflicts, but if you turn off wordwrap before producing shakeytext it's fine)
Neosss19

#67 Apr 26, 2021, 06:24 AM Source

Restart said:
ah it's the SRD shakingtext? Try it now, I just got it working for panda (if you have visuastella message also installed apparently word wrap in that conflicts, but if you turn off wordwrap before producing shakeytext it's fine)
Yes works!!.

Many thanks ^^
Restart

#68 Apr 27, 2021, 04:10 AM Source

Silenity said:
Tested YEP Equip Battle Skills, EBS Allowed Types, and EBS Skill Tiers.

All of them technically work, just some menus that need to be adjusted.
I finally got around to looking at these. I did a couple of tweaks, I think the menus should be fine now. Can you check?
Restart

#69 Apr 28, 2021, 06:45 AM Source

Just added support for more, including @waynee95 's WAY_Core and WAY_Achievements.

With them working in MZ, I can officially announce that we hit a hundred plugins!

I think that's worth a version bump. We're on v0.2 now!
PandaDance

#70 Apr 28, 2021, 08:49 AM Source

Congrats, @Restart! I know I must be speaking for hundreds of MZ users when I say thank you!

A question: if things are working fine with a previous version of the FOSSIL plugins, do you still recommend people update to the most recent versions?
Restart

#71 Apr 28, 2021, 02:54 PM Source

PandaDance said:
Congrats, @Restart! I know I must be speaking for hundreds of MZ users when I say thank you!

A question: if things are working fine with a previous version of the FOSSIL plugins, do you still recommend people update to the most recent versions?
Updates shouldn't break anything (most of what I do is redirect calls to functions that don't exist in MZ), but if everything is working fine and you aren't tweaking your plugin stack further I'd probably leave things as is.
weso12

#72 Apr 29, 2021, 10:33 PM Source

I've tested the YEP_MapSelectEquip and it kind of works but they are two quirks I'd like to report:

Let's say I try this situation and

The text and the Map Select overlap, this is probably the important thing that's really worth finishing but their another minor thing I would enjoy being fixed

(The cancel in the middle is mostly their to show the overlap issues occur with multiple commands):

If you combine it specifically with VisuMz_1_ItemsEquipsCore the selection menu gets messed up in ratio especially with higher aspect ratios. It might not be fixed but just FYI.
LyraVultur

#73 Apr 30, 2021, 07:29 AM Source

Tested Jay_BattleVAManager, and while the game launches now, after the start of a battle involving an enemy with any <voice> tags, I'll get the classic circular reference error:
Error: Object too deep at Function.JsonEx._encode (rmmz_core.js:6380)
Interestingly, if it's a battlestart line, the line will still play, then this error happens. As well, if you use the name of a sound effect eg
<voice> hurt|/Cat </voice>
you need a leading backslash now, which I don't think you used to.
Restart

#74 Apr 30, 2021, 03:04 PM Source

weso12 said:
I've tested the YEP_MapSelectEquip and it kind of works but they are two quirks I'd like to report:

View attachment 187894
Let's say I try this situation and

View attachment 187895
The text and the Map Select overlap, this is probably the important thing that's really worth finishing but their another minor thing I would enjoy being fixed

View attachment 187896
(The cancel in the middle is mostly their to show the overlap issues occur with multiple commands):
Thanks for the report. I'll have to look at that (custom windows often need a bit of tweaking).

LyraVultur said:
Tested Jay_BattleVAManager, and while the game launches now, after the start of a battle involving an enemy with any <voice> tags, I'll get the classic circular reference error:
Error: Object too deep at Function.JsonEx._encode (rmmz_core.js:6380)
Interestingly, if it's a battlestart line, the line will still play, then this error happens. As well, if you use the name of a sound effect eg
<voice> hurt|/Cat </voice>
you need a leading backslash now, which I don't think you used to.
I'm not familiar with the plugin. Do you have a demo project for that one, so I can see how it's supposed to look when working?
Restart

#75 Apr 30, 2021, 05:23 PM Source

anyway try the new PRE and see if you can get it to crash in an empty project.

FossilMZ/fossil-MV-MZ
I'm wondering if maybe your stack overflow error is caused by a conflict with a different plugin?
weso12

#76 Apr 30, 2021, 06:32 PM Source

BTW if anyone like me was wanting to know if HIME_HiddenChoiceConditions works, well I tested and found out it works, and in fact, seems to fully without FOSSIL and seems compatible with VisuMZ_1_MessageCore (including the extended choices, i managed to get an extended choice with hidden stuff just find), just remember to fully the instructions closely (making sure to use script call like the instructions ask not a Plugin command).

I know modern HimeWorks stuff is designed to work for both, but since this is a plugin that hasn't been updated since 2016 just thought I'd report.
Restart

#77 Apr 30, 2021, 06:34 PM Source

weso12 said:
BTW if anyone like me was wanting to know if HIME_HiddenChoiceConditions works, well I tested and found out it works, and in fact, seems to fully without FOSSIL and seems compatible with VisuMZ_1_MessageCore (including the extended choices, i managed to get an extended choice with hidden stuff just find), just remember to fully the instructions closely (making sure to use script call like the instructions ask not a Plugin command).

I know modern HimeWorks stuff is designed to work for both, but since this is a plugin that hasn't been updated since 2016 just thought I'd report.
That's good! I'm not sure if I should add those in a separate list or not; I feel like there's a lot of value in knowing which MV plugins can be used but this might not be the appropriate thread. I'll have to think about it.
Eliaquim

#78 Apr 30, 2021, 10:49 PM Source

Wow!!! Nailed it! Very nice initiative!!
:MV1:
LyraVultur

#79 May 1, 2021, 01:23 AM Source

Restart said:
anyway try the new PRE and see if you can get it to crash in an empty project.

FossilMZ/fossil-MV-MZ
I'm wondering if maybe your stack overflow error is caused by a conflict with a different plugin?
Interestingly, you fixing the AudioManager.createBuffer hook seems to have stopped the crashes? Or I can't get it to crash again anyway. I tried it in a larger project too with a bunch of VisuStella plugins and it ran fine! So hopefully that did the trick!
Restart

#80 May 1, 2021, 02:59 AM Source

LyraVultur said:
Interestingly, you fixing the AudioManager.createBuffer hook seems to have stopped the crashes? Or I can't get it to crash again anyway. I tried it in a larger project too with a bunch of VisuStella plugins and it ran fine! So hopefully that did the trick!
Glad it's working. I guess there are probably some hardcoded calls in there somewhere?

Anyway, that fix should make any other plugins that do sound stuff more likely to work in the future :)