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

myarichuk

#304 Oct 19, 2021, 12:11 PM Source

DarkSearinox92 said:
Well, 4 month without any news it's a bit worrying xD There are only problem posts and, although Restart said that this started as an open project, no one skilled is really participating in its improvement. It's a shame....
Indeed. If I have time I will try looking at least on *some* issues the project has, for example I think I traced the exact reason why Yanfly Core fails with FOSSIL (or at least one of the reasons)
But so far I didn't discover what would be the best way to fix this. I guess the best way in this case would be to compare relevant core script areas beween MV and MZ, because there is zero documentation I could find about those areas of code
DarkSearinox92

#305 Oct 19, 2021, 12:16 PM Source

myarichuk said:
Indeed. If I have time I will try looking at least on *some* issues the project has, for example I think I traced the exact reason why Yanfly Core fails with FOSSIL (or at least one of the reasons)
But so far I didn't discover what would be the best way to fix this. I guess the best way in this case would be to compare relevant core script areas beween MV and MZ, because there is zero documentation I could find about those areas of code

We just need lot of people with good skills in javascript... I appreciate your help, in any case! The help of all people is very important.
dewolf

#306 Oct 21, 2021, 03:40 AM Source

Does anyone know why running Moghunter's MZ version of Battle HUD clashes with FOSSIL? The game crashes in battle when anyone attacks, throwing the following error.
Nereid

#307 Oct 21, 2021, 04:08 AM Source

Does Quest Journal System (YEP) work with it?
BrandyMoon

#308 Oct 22, 2021, 07:05 PM Source

Is there any recent progress on this? I haven't heard an update for a while, makes me worry the project is no longer being actively worked on.
Decinbr

#309 Oct 23, 2021, 04:47 PM Source

Please!
try to put SDR_Auto_Updater
LyraVultur

#310 Oct 24, 2021, 10:14 AM Source

Just thought I'd mention that the plugin RS_MirrorArea causes this crash with FOSSIL. The author has a test project up in MV that opened fine.

Also Restart hasn't posted anything since Aug 15, so we can only hope they are just busy with IRL stuff for the last few months :)
Shuck

#311 Oct 24, 2021, 07:00 PM Source

Just dropping into to say that this plugin is my hero! Porting my game to MZ has been been possible only due to FOSSIL. I was devastated to learn that MacOS support for MV was being discontinued...I literally thought all those years of development were going to be tossed out the window; but then I found this Plugin! I was actually almost brought to tears when my game got up and running. Thanks to everyone who is a part of this!!
Enes44

#312 Oct 25, 2021, 08:53 AM Source

Hello https://forums.rpgmakerweb.com/index.php?threads/galvs-fishing-mini-game.70494/
can you convert it to mz
DarkSearinox92

#313 Oct 26, 2021, 02:23 PM Source

I think that VISUSTELLA Team killed Restart to prevent him from ruining the business. That's why he disappeared. :LZSlol::LZSlol::LZSlol:
Arthran

#314 Nov 3, 2021, 10:41 AM Source

magnumwhisper said:
Has anyone had success with deploying their game to mobile/web well using the Fossil plugin? For whatever reason my game does not work when I deploy it for mobile/web when using the fossil plugin.

Thanks in advance!
Did you follow the advice in the original post?

Mobile and Web Deployment Note

FOSSIL creates a 'FOSSILindex.html' file at runtime, and switches to use it instead of the original 'index.html'. This works seamlessly in both playtest and deploy on my computer. However, it is possible this might not be possible in web or mobile environments (I can't test them). However, if you just rename an existing FOSSILindex.html to index.html, you will bypass the html creation step, and proceed with the rest of the plugin. (Basically I need to replace 'main.js' in index.html with 'FOSSIL.js' so I can control when plugins are added).
TenraiEmiko

#315 Nov 4, 2021, 07:25 AM Source

Ummm... I heard that this one allows several MV plugins to work on MZ, so I decided to give it a try by bringing some really nice plugins from MV to MZ. I already have a really nice plugin that allows Undertale-styled bullet hell to occur inside battles, but when I slide the plugin into MZ, below the FOSSIL layer, but nothing happens. Battles don't start and instead it throws an error. Is that the plugin's fault, or is it RMMZ's code base's fault?
LyraVultur

#316 Nov 4, 2021, 01:20 PM Source

CaraPrincess said:
Ummm... I heard that this one allows several MV plugins to work on MZ, so I decided to give it a try by bringing some really nice plugins from MV to MZ. I already have a really nice plugin that allows Undertale-styled bullet hell to occur inside battles, but when I slide the plugin into MZ, below the FOSSIL layer, but nothing happens. Battles don't start and instead it throws an error. Is that the plugin's fault, or is it RMMZ's code base's fault?
if it works in MV but not in MZ, then it may be that the plugin is doing something that FOSSIL doesn't currently 'translate' to MZ - or it could just be a missing image. Without knowing what plugin you mean and what the error message/console error output is, I'm not sure beyond that.
DarkSearinox92

#317 Nov 4, 2021, 02:22 PM Source

As i said, Visustella has kidnapped Restart. We will never have updates for the project XD :LZSlol:
SpritesOnInstinct

#318 Nov 6, 2021, 09:52 PM Source

Why can't this just work for me... I'm trying to do Kino's https://forums.rpgmakerweb.com/index.php?threads/eis-shop-system.63514/ shop system to no avail... . . .
Nereid

#319 Nov 22, 2021, 02:37 AM Source

Anyone knows if this is due to fossil? https://forums.rpgmakerweb.com/index.php?threads/galvs-roll-credits.66829/page-3#post-1230410
SpritesOnInstinct

#320 Nov 22, 2021, 04:52 PM Source

Is there anyway to make this plugin a sought with this plugin. the Plugin was to have a shop with a limited stock for each item and could replenish stock of item(s) to a shop. I Really really need this for mz game.
Arthran

#321 Nov 24, 2021, 06:06 AM Source

lupecavem said:
Does anyone know why running Moghunter's MZ version of Battle HUD clashes with FOSSIL? The game crashes in battle when anyone attacks, throwing the following error.
That doesn't seem related to Fossil. Looks like you're missing Face_6.png in your battlehud folder.
Arthran

#322 Nov 24, 2021, 07:51 AM Source

SpritesofImagiNation said:
Why can't this just work for me... I'm trying to do Kino's https://forums.rpgmakerweb.com/index.php?threads/eis-shop-system.63514/ shop system to no avail... . . .
I made it work with Kino's EISShopSystem. I made a pull request to see if Restart will add my changes to the main project, but in the meantime, you can grab my edited version here.
BlueDragon28

#323 Dec 9, 2021, 07:29 AM Source

Hey am I having a problem getting my game to work with gridfreedoodads can someone help me problem solve? It gives this error code when I try to start the game. I have tried turning off of ther plugins and still gives same error HELP!