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

Aurawhisperer

#426 Nov 18, 2022, 02:08 AM Source

Tactics System 1.2.1 (Tactical Battle System)
Unless I did something wrong, I can confirm FOSSIL won't work with the plugin above + its addons. It errors out :/
Animebryan

#427 Dec 5, 2022, 01:30 PM Source

Here's the FOSSIL plugin for anyone who still needs it.
ATT_Turan

#428 Dec 6, 2022, 03:52 AM Source

Animebryan said:
Here's the FOSSIL plugin for anyone who still needs it.
Just for clarity for readers - is that a copy of Arthran's updated fork, or the most recent version from Restart?
Animebryan

#429 Dec 7, 2022, 10:01 PM Source

I have no idea. I believe this is just the most recent version. Here is the header of the plugin if it helps:
/*: * @plugindesc Fossil is an interoperability layer for RMMZ, designed to make MV plugins work in MZ. * So far, we support over 300 plugins. You can help! * @author FOSSIL TEAM * @target MZ * @command useOldPlugin * @text 'Enter MV plugin commands' * @desc 'They're back! Enter them the same way you used to.' * @arg OldPluginCommand * @text * @ desc Identical to MV's commands. * @help FOSSIL goes at the start, before all other plugins. Fixing Old Software / Special Interoperability Layer (FOSSIL) Version 1.0.12
MrBluee

#430 Dec 29, 2022, 06:59 AM Source

Can anyone help me ‍‍
Aerosys

#431 Dec 29, 2022, 09:03 AM Source

MrBluee said:
View attachment 249222
Can anyone help me ‍‍
I think the error message is clear. Open up your Plugin Manager and move FOSSIL to the top!
MrBluee

#432 Dec 29, 2022, 03:27 PM Source

Aerosys said:
I think the error message is clear. Open up your Plugin Manager and move FOSSIL to the top!
It work thank u
Splatterguy

#433 Dec 29, 2022, 10:20 PM Source

MOG CHRONO ENGINE

Hi guys!

I have converted my MV project to MZ.
But now MOG'S CHORNO ENGINE no longer works.

Whenever I press the key to hit, I get the following error.

Any ideas how to fix that?
Tsunar

#434 Jan 5, 2023, 02:57 AM Source

I get an error 404 when trying to download the plugin =O
Roninator2

#435 Jan 5, 2023, 11:48 AM Source

Tsunar said:
I get an error 404 when trying to download the plugin =O
check page 21. the plugin has been saved by another person. Post #411
Even my post above #425 will lead you there.
Also post #427 has a copy that may be the latest one.
Nortas

#436 Jan 7, 2023, 12:41 AM Source

Download links are 404 not found :(
Salyhin

#437 Jan 16, 2023, 01:20 AM Source

The links don't work.
Sword_of_Dusk

#438 Jan 16, 2023, 01:42 AM Source

@Nortas @Salyhin If you both would check the post right above Nortas', you should find your solution.
Nortas

#439 Jan 16, 2023, 10:23 AM Source

Sword_of_Dusk said:
@Nortas @Salyhin If you both would check the post right above Nortas', you should find your solution.
Found it! Ty!!!!!
Puppet Knight

#440 Jan 19, 2023, 01:45 PM Source

Animebryan said:
Fixing Old Software / Special Interoperability Layer (FOSSIL) Version 1.0.12
My version is at 1.0.13 in case that helps anyone?
Puppet Knight

#441 Jan 19, 2023, 01:46 PM Source

mobiusclimber said:
I'm getting this same error.
@Vuono87

I've only gotten VE Materia to work without VS Core Engine and ItemEquip Core
mobiusclimber

#442 Jan 20, 2023, 05:36 PM Source

I'll try that. I've actually decided to avoid using VS plugins in this game, so that works for me.
Seedspreaderent

#443 Feb 26, 2023, 05:57 PM Source

Anyone else have this error from fossil or know solutions? Never had this issue before MZ 1.6.0
Animebryan

#444 Mar 5, 2023, 03:53 PM Source

Seedspreaderent said:
Never had this issue before MZ 1.6.0
And that's where you messed up. Every time RPG Maker gets an update, it breaks something. Always better to stick with a previous version, like 1.5.0. It's part of RM's "2 steps forward, 1 step backward" policy. Also, your plugin error may not be exclusively caused by FOSSIL. It shows that it's looking for a png file with %5B%5D in it's name. Not sure if the %s are really part of the filename, but something in your game is calling for that file but it doesn't exist.
Solar_Flare

#445 Mar 9, 2023, 05:53 AM Source

%5B%5D is URL escape syntax for [], so it's probably looking for a png file containing square brackets.