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 19 of 31 View original ↗

ScytheX

#364 Feb 19, 2022, 06:24 PM Source

hey so small problem the plugin doesn't seem to work well with some MZ plugins mainly Visustella's class change system, i made a thread about but it seems to try to load up mv files for a mz plugin and that causes an error.

MZ - VisuStella MZ Class Change System error
NikaraWorld

#365 Feb 20, 2022, 12:38 AM Source

ScytheX said:
hey so small problem the plugin doesn't seem to work well with some MZ plugins mainly Visustella's class change system, i made a thread about but it seems to try to load up mv files for a mz plugin and that causes an error.

MZ - VisuStella MZ Class Change System error
Do you have the FOSSIL at the very top before any other plugins. I'm using all visustella's plugins and I haven't encountered any errors
Roninator2

#366 Feb 20, 2022, 01:04 AM Source

NikaraWorld said:
I'm using all visustella's plugins and I haven't encountered any errors
with just fossil, visu core and class change gives the error.
do a class change and you'll see. the animation playing gives an error
ScytheX

#367 Feb 20, 2022, 01:11 AM Source

NikaraWorld said:
Do you have the FOSSIL at the very top before any other plugins. I'm using all visustella's plugins and I haven't encountered any errors
yeah . i can't run at all if its not a the top. anyway i have a fix for it thanks to Roninator2

Roninator2

#368 Feb 20, 2022, 07:41 AM Source

ScytheX said:

causes an error

My monkeying around has this as a solution.
It does the same thing as what I told you in the other thread. The animation does not play.
Add into Fossil somewhere. I have it inserted at line 4970.

JavaScript:

    Fossil.loadPostFix('VisuMZ_2_ClassChangeSystem',function()
    {
        Sprite_AnimationMV.prototype.updateFrame = function() {
                if (this._duration > 0) {
                        const timings = this._animation.soundTimings.concat(this._animation.flashTimings);
                        const frameIndex = this.currentFrameIndex();
                        this.updateAllCellSprites(this._animation.frames[frameIndex]);
                        for (const timing of timings) {
                                if (timing.frame === frameIndex) {
                                        this.processTimingData(timing);
                                }
                        }
                }
        };
        
    })

I don't understand nearly enough to get it to play the animation.

limsoonchiong

#369 Mar 14, 2022, 01:58 PM Source

FOSSIL does not seem to work with Cordova. I can't port RPGMaker to Android with Fossil enable. Anyone else found a work around?
Xiamon

#370 Mar 15, 2022, 01:23 AM Source

So we are removing all of our Visustella plugins and opting to go with Fossil and Yep plugins. the first problem came up with just fossil and yep core engine installed text displays in windows but not in the answer windows and some of the menu option windows. any ideas?
kwijibo

#371 Mar 20, 2022, 10:00 PM Source

Attempting to use Gimmer_ControllerType results in this error as soon as I use the arrow keys. Any idea on how to fix this?
BenSD

#372 Mar 27, 2022, 01:26 AM Source

limsoonchiong said:
FOSSIL does not seem to work with Cordova. I can't port RPGMaker to Android with Fossil enable. Anyone else found a work around?
Unless I'm doing something wrong, I don't think this is specific to Cordova, but to any web deployment; I haven't been able to get FOSSIL to work when I upload my game as HTML either and was hoping somebody could tell me I was doing something simple and stupid wrong. I love the options this plugin opens up, but I'm pretty attached to web and android deployment, so any help would be appreciated.
limsoonchiong

#373 Mar 27, 2022, 02:27 AM Source

schvanckque said:
Unless I'm doing something wrong, I don't think this is specific to Cordova, but to any web deployment; I haven't been able to get FOSSIL to work when I upload my game as HTML either and was hoping somebody could tell me I was doing something simple and stupid wrong. I love the options this plugin opens up, but I'm pretty attached to web and android deployment, so any help would be appreciated.
Right, that make sense. I could only test my HTML version with Cordova and it works after I disable FOSSIL so I tot it was Fossil's vs Cordova. So it could be Fossil vs HTML. Perhaps we're suppose to use FOSSILIndex.html instead of the normal index.html?
BenSD

#374 Mar 27, 2022, 03:33 AM Source

limsoonchiong said:
Perhaps we're suppose to use FOSSILIndex.html instead of the normal index.html?
Um...wow...why didn't that occur to me? I went ahead and uploaded my current files to test the theory and it turns out... (dramatic pause)
Yeah, that definitely works. I feel kind of silly now, but I'm glad you found the answer to our problem! :D
limsoonchiong

#375 Mar 27, 2022, 04:14 AM Source

schvanckque said:
Um...wow...why didn't that occur to me? I went ahead and uploaded my current files to test the theory and it turns out... (dramatic pause)
Yeah, that definitely works. I feel kind of silly now, but I'm glad you found the answer to our problem! :D
Two minds are greater than one. I think we both found the solution by giving each other the right hints. :)
Lokystaz

#376 Mar 31, 2022, 09:36 AM Source

Note: Some authors have made ports of their own plugins to MZ. If you aren't trying to port over an existing project, or have extension plugins, I recommend you use a plugin that was actually ported to be MZ native. It's a lot less likely to be buggy
Hey that is amazing... Thanks a lot for your work !!
But as you said in that note, it's better to use native plugins of course, sadly many plugins are not ported to MZ or became paid plugins in the process..
I'm sorry if the question has already been asked but I don't have time to read the 19 pages...
So, does there is any drawback in using MV plugins in MZ ? I mean about performances and major issues ?

(I'm starting to think about going back to MV just because of some plugins, but the few update of MZ are really great, the layers, the particle engine, the overall performance, export map for parallax mapping at proper size..etc)
alltheyuriz

#377 Apr 9, 2022, 11:19 PM Source

fossil isn't detecting that it's the first plug in help?
BenSD

#378 Apr 10, 2022, 01:48 AM Source

alltheyuriz said:
fossil isn't detecting that it's the first plug in help?
Do you have it as the very first, in front of MZ plugins also, or just first of the MV plugins? It has to be above everything. Hope that helps!
alltheyuriz

#379 Apr 10, 2022, 02:10 AM Source

@BenSD yea it's above everything
Richard John S

#380 Apr 21, 2022, 06:10 AM Source

When trying to use YEP Equip Battle Skills, I get "Undefined" in the menu and the game freezes.

EDIT: It seems to work with an older version of the plugin but not the latest version.
Megablackdragon31

#381 Apr 27, 2022, 06:05 AM Source

Sorry to bother yourselves,anyone else has a compatibility issue between this plugin and NRP AnimationActorCommand?
darkand

#382 May 12, 2022, 01:19 AM Source

i can make work Qabs and Qmovement? or dont is supported?
FrigidGaze

#383 May 16, 2022, 06:27 PM Source

Heya!

First of all, I just wanted to thank the people responsible for this wonderful plugin, as it's been a real lifesaver in a lot of ways, and just seems like outright sorcery to me, haha.

I'm sure if it's been mentioned before--but if so, I apologise--but there appears to be a small quirk regarding the compatibility with the YEP_Instantcast plugin. It does as it should in most cases, but there's a graphical glitch that happens, where the command window remains on screen while the instant skill takes place, as per my screenshot:

Screenshot

I'm using the 'border' battle layout for reference, but I believe it happens for any of the battle layouts in conjunction with Visustella's battle core.

BUT, the command box only lingers during the move if it's one that bypasses the target selection, so 'User', 'All Allies and Enemies', etc. Which I suppose means there's nothing closing the box down as it should before the skill. So I'm not sure if that helps give any hints as to where, or how a possible tweak or fix might be possible?

Otherwise, if in the meantime any native MZ instant cast style solutions have come out I would be more than happy to use those instead. I know Visustella technically has one, but it seems constrained to a specific battle type, right? Or does it work across them all?

I thank you for your time, either way!