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

JoeLore

#506 Jan 29, 2024, 09:21 PM Source

Is the project dead?
AquaEcho

#507 Jan 29, 2024, 10:06 PM Source

JoeLore said:
Is the project dead?
The creator left the RPG Maker community so it's no longer updated but the plugin still works.
Choraß

#508 Feb 5, 2024, 09:35 AM Source

Hello, anyone had a same issue and find a solution maybe, with Fossil - Yanfly Battle Engine Core - Battle CTB - Yanfly Party System, where the battle kinda freeze after you open the Formation Scene and return to battle scene?

After open and close the Formation Scene again, there is no input possible.

At MV there is no kind of issue like that. I run some tests to exclude other plugins incompatibility. It's the CTB plugin under Fossil - MZ.
Arglax

#509 Apr 4, 2024, 03:41 AM Source

anybody still got the fossil plugin?
ATT_Turan

#510 Apr 4, 2024, 03:43 AM Source

Arglax said:
anybody still got the fossil plugin?
There are multiple download links over the last few pages of this thread, is there a problem with all of them?
Arthran

#511 Apr 4, 2024, 03:53 AM Source

My link still works like a champ.
ATT_Turan

#512 Apr 4, 2024, 04:36 AM Source

Arthran said:
My link still works like a champ.
I figured it would, just...it's the fashion to not read, for some reason :stickytongue:

Six posts up on this very page is the same question, with the same answer. And if one clicks back a single page there are no fewer than three posts with links (and an attached download) for the plugin.
Arglax

#513 Apr 4, 2024, 04:53 AM Source

Arthran said:
My link still works like a champ.
Used yours. Thank you!

(my bad lmao I skipped past to the final page)
Puppet Knight

#514 Apr 4, 2024, 12:04 PM Source

To be fair at this point it might be easier to just alter the original post to have @Arthran 's link xD
AdriR50

#515 Apr 19, 2024, 08:40 AM Source

Please, I'm new to this FOSSIL thing, I didn't know it existed.
Can anyone help me how to add Yanfli (YEP) plugins? I don't understand.
I'm having errors all the time, and I don't know if I should add the CoreEngine or the other plugins directly
Puppet Knight

#516 Apr 19, 2024, 07:38 PM Source

AdriR50 said:
Please, I'm new to this FOSSIL thing, I didn't know it existed.
Can anyone help me how to add Yanfli (YEP) plugins? I don't understand.
I'm having errors all the time, and I don't know if I should add the CoreEngine or the other plugins directly
You're gonna have to give a lot more context here.

Adding in the YEP plugins should just be a matter of putting them into your plugin manager as usual. Any dependencies they have will be listed in their plugins. FOSSIL has to be at the very top of your plugin order
AdriR50

#517 Apr 19, 2024, 10:33 PM Source

Puppet Knight said:
You're gonna have to give a lot more context here.

Adding in the YEP plugins should just be a matter of putting them into your plugin manager as usual. Any dependencies they have will be listed in their plugins. FOSSIL has to be at the very top of your plugin order
I want to use Yanfli plugins. When I add the CoreEngine, the screen gets narrower, and when I try to fix it, it doesn't change. Then, I add OptionCore and it bugs. The same happens to me with any other Yanfli Core. I have tried separately and nothing.

Does anyone know what's happening or what I should do to make them work?

Additional note: I already added Visutella plugins at other time and it was working great with the plugins I have. The only problem is with the Yanfli plugins. Yes, I first placed the FOSSIL plugin above, it's just not visible in the screenshot.
Arthran

#518 Apr 19, 2024, 11:32 PM Source

AdriR50 said:
I want to use Yanfli plugins. When I add the CoreEngine, the screen gets narrower, and when I try to fix it, it doesn't change. Then, I add OptionCore and it bugs. The same happens to me with any other Yanfli Core. I have tried separately and nothing.

Does anyone know what's happening or what I should do to make them work?

Additional note: I already added Visutella plugins at other time and it was working great with the plugins I have. The only problem is with the Yanfli plugins. Yes, I first placed the FOSSIL plugin above, it's just not visible in the screenshot.View attachment 302391
YEP Core Engine isn't supported. There is a list of supported plugins in the first post of this thread.
AdriR50

#519 Apr 20, 2024, 04:52 AM Source

Arthran said:
YEP Core Engine isn't supported. There is a list of supported plugins in the first post of this thread.
Yes, I read it. But then how do I make the other Yanfli plugins work without CoreEngine? Or are they not necessary?
Puppet Knight

#520 Apr 20, 2024, 06:39 AM Source

Do any of the other YEP Core plugins say they need Core Engine in their help file or on the website?
Gunmetal_Dreams

#521 Apr 27, 2024, 04:28 PM Source

Puppet Knight said:
You're gonna have to give a lot more context here.

Adding in the YEP plugins should just be a matter of putting them into your plugin manager as usual. Any dependencies they have will be listed in their plugins. FOSSIL has to be at the very top of your plugin order
Ok, so it's enough to just delete the plugins in the plugin manager and re install them starting with Fossil? Or delete the plugins folder and copy the plugins back in a fresh folder? I only have four plugins so neither is really much of a task.
Aerosys

#522 Apr 27, 2024, 05:24 PM Source

Gunmetal_Dreams said:
Ok, so it's enough to just delete the plugins in the plugin manager and re install them starting with Fossil? Or delete the plugins folder and copy the plugins back in a fresh folder? I only have four plugins so neither is really much of a task.
I think, you can just drag&drop them.
Gunmetal_Dreams

#523 Apr 27, 2024, 06:32 PM Source

Aerosys said:
I think, you can just drag&drop them.
Even better. Thanks!
Zeq

#524 May 10, 2024, 09:20 AM Source

@Restart
dude what the hell, I can use YEP in MZ? Thanks!
I needed this because RPG Maker MV has stopped working for me..it's high time to migrate to shiny marvelous MZ :D
ItsMeDevRoland

#525 May 10, 2024, 06:32 PM Source

Im Having Issue's when i use SRD_Hud... no clue if this is fossil's fault, currently testing if this is other plugin's compatibility issue.. any experience with this having conflict issue with SRD UltraHud?