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

Gigadragon78

#324 Dec 11, 2021, 04:31 AM Source

BlueDragon28 said:
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!
Just remember that not all Yanfly plugins are supported.
ItsMeDevRoland

#325 Dec 16, 2021, 01:05 PM Source

I Really Hope This Plugin, Still Continue... Im Not Here To Request A Plugin, But.. To All Of Those Who Help This Plugin, Stay Safe, Keep Continuing this Wonderful Plugin, If Only I Have Skills:rtear:
Makeratore

#326 Dec 16, 2021, 06:19 PM Source

Is this plugin development dead?
DarkSearinox92

#327 Dec 17, 2021, 11:21 AM Source

Makeratore said:
Is this plugin development dead?

Apparently restart has disappeared. If no one takes matters into their own hands, it will no longer be continued. It is a beautiful project and I am really frustrated that no one continues it.
Aerosys

#328 Dec 17, 2021, 12:00 PM Source

Scanning through the plugin's code, wouldn't make it easier to write generic conversion code between MV and MZ rather than manually monkey-patch 3rd Party Plugins?
jgdeutsch

#329 Dec 22, 2021, 08:38 AM Source

In RMMZ, getting the error:

Error
FOSSIL needs to be the first plugin. If FOSSIL is not the first plugin, everything will break!

Even though I've put the plugin at the top of the list.
Animebryan

#330 Dec 22, 2021, 09:17 AM Source

BlueDragon28 said:
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 their plugins and still gives same error HELP!
It's a well known fact that FOSSIL is incompatible with Yanfly's Battle Engine Core.
ShadowDragon

#331 Dec 22, 2021, 11:22 AM Source

@jgdeutsch FOSSIL MUST be the first plugin above MV plugins,
not above MZ plugins, otherwise, MZ might not function as normal.

aswhile, you have it names with lowercase, it should be capitalized FOSSIL.js

FOSSIL does work with the YEP library. most of them at least.
Gigadragon78

#332 Dec 22, 2021, 12:21 PM Source

Hi ShadowDragon,long time no see. Nope,it must be at the top of all plugins. I tried to change the order (putting the MZ plugins above MV including fosil) and the warning window appears. It says,FOSIL needs to be the first plugin. If FOSIL is not the first plugin everything will break.
ShadowDragon

#333 Dec 22, 2021, 12:48 PM Source

there used to be 2 plugins before, so you have
FOSSIL-Pre
mv plugins
FOSSIL-end

I beliee MZ plugins
FOSSIL.js
mv plugins

if FOSSIL must be on the very top,
FOSSIL.js
MV plugins
MZ plugins below those

I dont think you can mix it up like
FOSSIL.js
mz plugin
mv plugin
mv plugin
mz plugin
mv plugin etc etc.

so correct me if im wrong.
Gigadragon78

#334 Dec 22, 2021, 03:06 PM Source

I dont know what exactly happens. At least for me it works in this order.
FOSIL
MZ
MV
Other metods give me the same error.
ShadowDragon

#335 Dec 22, 2021, 03:25 PM Source

I dont own MZ, so I cannot really check, but there are samples on teh first
page how to add some plugin patch if they needed, if you know JS
it would be an easy add/modifications.

otherwise, you need to see if they port it, if they dont, ask permission
if you can make or others a port from it.

but good luck otherwise on your project :)
Gigadragon78

#336 Dec 22, 2021, 03:41 PM Source

T

ShadowDragon said:
I dont own MZ, so I cannot really check, but there are samples on teh first
page how to add some plugin patch if they needed, if you know JS
it would be an easy add/modifications.

otherwise, you need to see if they port it, if they dont, ask permission
if you can make or others a port from it.

but good luck otherwise on your project :)
Thanks you very much,actually im working with evented systems but i will learn javascript sometime in the future. :)
jgdeutsch

#337 Dec 22, 2021, 07:17 PM Source

Thank you! Capitalizing the plugin file to FOSSIL.js did the trick :)

ShadowDragon said:
@jgdeutsch FOSSIL MUST be the first plugin above MV plugins,
not above MZ plugins, otherwise, MZ might not function as normal.

aswhile, you have it names with lowercase, it should be capitalized FOSSIL.js

FOSSIL does work with the YEP library. most of them at least.
Raven Guertena

#338 Dec 29, 2021, 05:13 PM Source

any ideas for making some of the Visustella plugins avaible for this? like the Input combo plugin?
Shaz

#339 Dec 29, 2021, 09:39 PM Source

@Raven Guertena this plugin allows you to use MV plugins in MZ. Visustella plugins ARE for MZ, so don't need to use this.
Raven Guertena

#340 Dec 30, 2021, 07:05 PM Source

Shaz said:
@Raven Guertena this plugin allows you to use MV plugins in MZ. Visustella plugins ARE for MZ, so don't need to use this.
not the one I was trying to go with sadly, they do not have the input combo plugin for mz yet only one avaible for mv. So I was just asking to know ^^"
estriole

#341 Jan 3, 2022, 05:08 AM Source

Raven Guertena said:
not the one I was trying to go with sadly, they do not have the input combo plugin for mz yet only one avaible for mv. So I was just asking to know ^^"
what shaz means... plugins with prefix "VISUSTELLA" means it already for MZ...
the one you want is not visustella...
yanfly plugin in MV like input combo you want have "YEP" prefix...
that what shaz means i think...

hope this help.
zerobeat032

#342 Jan 3, 2022, 05:16 AM Source

actually the input combo plugin isn't considered YEP as far as I can see. it's one of the few visustella plugins for MV, along with Active Chain Skills. https://visustella.itch.io/input-combo-skills... but yeah, neither have been ported to MZ as of yet it seems.

https://forums.rpgmakerweb.com/index.php?threads/quick-time-events-r2-26-11.71268/ this is a good alternative tho and it does work with FOSSIL.
Pondis

#343 Jan 7, 2022, 10:24 PM Source

Evening all. I am having trouble getting WAY_StorageSystem to work with FOSSIL, but I suspect I am doing something wrong.

FOSSIL says both are compatible with it, I have FOSSIL, then WAY_Core, then WAY_StorageSYstem in my plugin list which I think is right.

I havent updated the FOSSIL.js, I am not sure I need to, though the front page of this thread mentions it.

Long story short, I dont know what I am doing and I need a storage system!

Thanks