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

Restart

#244 Jul 10, 2021, 10:47 PM Source

oh, sorry, I misread LTBS as LMBS, I was thinking of the mog one since people have asked about that before
Frostorm

#245 Jul 10, 2021, 11:12 PM Source

Restart said:
oh, sorry, I misread LTBS as LMBS, I was thinking of the mog one since people have asked about that before
Ah, that makes sense. I was wondering how/where LTBS uses a scrolling battleback lol. Anyway, what does that mean in terms of LTBS compatability?
Lostsouls46

#246 Jul 11, 2021, 03:13 PM Source

Restart said:
Honestly not sure. If you can get it to happen with yanfly's battle core I might be able to figure it out, but anything involving VS isn't really possible to work with.

My *guess* would be that it somehow is getting the location set to a noninteger, like NaN or undefined or 'fish' or something.
I just finished testing everything I have (Visustella stuff and Yanfly stuff) with YEP_RowFormation and everything played super nicely with regards to my bug report on the enemies disappearing, until I put in the Visustella Core Engine. Everything worked perfectly without it, but for some reason, it doesn't want to play nicely with YEP_RowFormation's row switching capabilities, but only in the instance that the enemy goes first and uses a move that moves the actors row. IDK if this is a fixable thing, I know you cant work with Visustella stuff due to their terms.

The only thing I can think of is if the Visustella Core Engine modifies enemy and actor locations, which in turn shows a NULL value like you suggested Restart. Ill dig deeper and see what I can come up with, but until then if anyone has some suggestions I'm all ears.
Restart

#247 Jul 12, 2021, 06:31 AM Source

Frostorm said:
Ah, that makes sense. I was wondering how/where LTBS uses a scrolling battleback lol. Anyway, what does that mean in terms of LTBS compatability?
Haven't looked at LeTBS yet - there's a lot of plugins out there
OverTheTop123

#248 Jul 13, 2021, 11:35 PM Source

First of all, amazing job! Thank you so much for this. One question. Would this be able to work under FOSSIL?

Edit: Scratch that, works like a charm!
EAP

#249 Jul 17, 2021, 01:46 AM Source

So I am getting this error code when I am using VisuMZ_2_Crafting
System to be something within the Scene part of things.

I have disable FOSSIL and it works and also test all the others it seems to be only FOSSIL that sadly is having a hang up.

If there is anything you could help with this would be greatly helpful.

"UPDATE"

I go it to work but sadly had to disable the Animation Settings on the plugin..
FrancoBash

#250 Jul 18, 2021, 11:47 PM Source

Thanks so much for this -- really incredible stuff!

I've been using it with Frog Magic and, functionally, it all works great! The only issue is that while in combat the game fails to count down spell uses. They actually are working correctly, it just won't actually show the spell slots count down lol. I have no other plugins and am purely running tests right now.
SangHendrix

#251 Jul 21, 2021, 12:38 PM Source

So I did some test on my Android device (Note 9). Fossil 0.1 runs fine but when I updated it to 1.0 version, the screen turned black after the loading icon showed up. I can still here the music but yeah that's what happened. I switched back to 0.1 version and it ran fine.
Edit: Actually nvm, now it's all messed up. I'll try to figure out the reason.
TheGentlemanLoser

#252 Jul 22, 2021, 02:09 AM Source

First off, I'm delighted this exists. My failure to have a killer finished game to sub to starjam today means I probably won't be making the jump to MZ after all, sadly, but I did want to put in a request in favor of FOSSILIZING Orange Screenshot Saver. It seems insane to have to give this guy ten dollars a month to get access to the only plugin written for MZ that I've found that fulfills this extremely basic convenience/quality-of-life function.
ItinerantProcrastinator

#253 Jul 22, 2021, 12:56 PM Source

Hi, I'm having an issue using YEP_MessageCore via FOSSIL. For some reason whenever I try to use the name window it crashes.

I know my copy of MessageCore works fine normally because it works just fine in an MV project. Also the only 2 plugins I have active in the MZ Project are FOSSIL -> YEP_MessageCore.

Apparently it's treating the NameWindow as undefined and thus trying and failing to call the refresh function on it per the Yanfly script.

I can't tell whether this is a bug or something I'm doing wrong considering YEP_MessageCore supposedly has confirmed functionality via FOSSIL. It seems that followed all the FOSSIL instructions correctly but it's not working.

Edit: Grammar.
TheCosmicSlug

#254 Jul 25, 2021, 10:42 AM Source

I tried SRD_CharactorChoices (https://sumrndm.site/character-choices/) but it still did not work in MZ, the error stated:

rmmz_managers.js:2030 TypeError: Cannot read property 'active' of undefined at Window_Message.isAnySubWindowActive (SRD_CharacterChoices.js:171
fizzly

#255 Jul 28, 2021, 06:02 AM Source

I can't even tell how grateful I am for this plugin. THANK YOU.
gamel001

#256 Aug 3, 2021, 01:51 AM Source

Hi man, please help me to use SRD_SummonCore plugin, summon appear and not attack, can help me?
Restart

#257 Aug 4, 2021, 04:32 PM Source

Hey, quick update.

As has been pretty obvious, updates have slowed down on FOSSIL significantly. Partly that's due to no longer being fully WFH - I don't have the free time to do the 5 plugins a day I was averaging at the start of the project. I was also told that some of the site admins thought that FOSSIL was having a negative effect upon the plugin making community, and while they didn't tell me to stop working on it, it kind of took the wind out of my sails and made working on this project a lot less fun.

It's not abandoned but my updates to the plugin will be less frequent - and of course, I'm still accepting community help to help make FOSSIL bigger and better, if anyone else wants to step up to the plate :).
Furia25

#258 Aug 4, 2021, 04:39 PM Source

Fossil will in a future update make the MZ plugin can be on mv ? It would be amazing to allow cross-compatibility
Restart

#259 Aug 5, 2021, 02:12 AM Source

Furia25 said:
Fossil will in a future update make the MZ plugin can be on mv ? It would be amazing to allow cross-compatibility
That's RETRO
MV - RETRO - MZ Plugins on MV Drakkonis is doing that one
RyanBram

#260 Aug 9, 2021, 12:28 AM Source

Restart said:
... I was also told that some of the site admins thought that FOSSIL was having a negative effect upon the plugin making community, and while they didn't tell me to stop working on it, it kind of took the wind out of my sails and made working on this project a lot less fun.

It's not abandoned but my updates to the plugin will be less frequent - and of course, I'm still accepting community help to help make FOSSIL bigger and better, if anyone else wants to step up to the plate :).

Hi, Restart.

Through this message I just want to express my gratitude to you who have created Fossil.

Fossil allows us to enjoy the latest features of RPG Maker MZ without losing the benefits of RPG Maker MV plugins. Fossil allows every work and code that has been created will not be wasted just because of compatibility issues. Fossil allows large projects such as the SRPG Engine MV to be utilized by RPG Maker MZ users without the enormous effort and expense of rewriting the code.

I want to show my support to you, that Fossil is a very useful project and there are no negative effects at all. Everyone is free to use the plugin that is specifically for RPG Maker MZ without losing access to the plugin that has been made for RPG Maker MV.

You have done what developers of this software is supposed to do, which is to maintain compatibility for each latest version release.

Thank you for your hard work and keep enjoying the work you have created.
KARAKURT

#261 Aug 9, 2021, 11:31 AM Source

Hi, Restart.

I need to ask you something. There is such a plugin Random Dialogue v1.03a. Is it possible to make it work on the RPG Maker MZ with your plugin (FOSSIL).
Thank you!
CCCreations

#262 Aug 11, 2021, 06:48 PM Source

Is there support to add in compatibility to SRD's CCEX?
Decinbr

#263 Aug 11, 2021, 07:15 PM Source

Please fossilize SRD. Auto updater plugin