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

Sketchguy1248

#466 Sep 21, 2023, 03:18 AM Source

Animebryan said:
Here's the FOSSIL plugin for anyone who still needs it.
THANK YOU!!!
YokoSan

#467 Sep 21, 2023, 06:42 PM Source

Git Mirror https://github.com/EerFree/fossil-MV-MZ/
Last ver. 1.0.13
Puppet Knight

#468 Sep 21, 2023, 06:45 PM Source

YokoSan said:
Git Mirror https://github.com/tonymichaelhead/fossil-MV-MZ
Last ver. 1.0.13
File in that Git has '1.0.12' in line.
YokoSan

#469 Sep 22, 2023, 12:30 AM Source

Yes. I fix the link
Roninator2

#470 Sep 22, 2023, 02:56 AM Source

YokoSan said:
Yes. I fix the link
You fixed the text not the link. clicking on it still goes to the 1.0.12 version.
Copying the text and pasting into a browser address bar goes to the 1.0.13 version.
Jrrkein

#471 Sep 22, 2023, 03:37 AM Source

Anyone have that link with window fix?
Thorion

#472 Oct 4, 2023, 03:37 PM Source

Guys, good afternoon.
I intend to use this plugin MOG_BattleCommands no RPG Maker MZ.
Can anyone help me how I do this, because it is not on the FOSSIL list.
ATT_Turan

#473 Oct 4, 2023, 03:43 PM Source

Thorion said:
I intend to use this plugin MOG_BattleCommands no RPG Maker MZ.
Can anyone help me how I do this, because it is not on the FOSSIL list.
Then why post in the FOSSIL thread? :rolleyes:

You should start a new thread and list what you've already tried to do. But to quickly answer, if:
- it doesn't work just by itself (include the plugin and try)
and
- it doesn't work with FOSSIL (whether or not it's on the list)

then you'll just have to rewrite the code.
Nyaa

#474 Oct 7, 2023, 09:33 AM Source

Hello, I just wanted to mention that the opening post for this thread links to "live" version of the FOSSIL which isn't accessible. Rather than the current "archival" read-only version that's accessible

TYVM for making this work, just tested with FROG series and it works!

*edit* this said is there chance to make Frog Health work?
Tested to see if it'd work and it gives "this.windowWidth is not a function"
Aerosys

#475 Oct 7, 2023, 01:28 PM Source

Nyaa said:
Hello, I just wanted to mention that the opening post for this thread links to "live" version of the FOSSIL which isn't accessible. Rather than the current "archival" read-only version that's accessible

TYVM for making this work, just tested with FROG series and it works!

*edit* this said is there chance to make Frog Health work?
Tested to see if it'd work and it gives "this.windowWidth is not a function"
It's probably better to start a new thread requesting a plugin conversion. This thread here is basically dead.
Nyaa

#476 Oct 7, 2023, 01:31 PM Source

Aerosys said:
It's probably better to start a new thread requesting a plugin conversion. This thread here is basically dead.
Aw, that's too bad. I did make new thread in JS Plugin Requests.

Didn't notice thread was dead because last post before mine was this week. Sorry.
Edael

#477 Oct 8, 2023, 10:39 PM Source

Splatterguy said:
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?

View attachment 249282
Anyone have a fix for this at all, running into the same error ever time any attack happens.
ATT_Turan

#478 Oct 8, 2023, 10:46 PM Source

Nyaa said:
Didn't notice thread was dead because last post before mine was this week. Sorry.
It's not that the thread is dead so much as the OP (and author) is no longer on the site. I know quite a while ago @Arthran made some additions/improvements to it, but I have no idea if anyone is interested in taking any requests to add further compatibility beyond what it already supports.

Personally, I think you're also unlikely to find people interested in converting other authors' plugins to be compatible with MZ for free - presuming the author's terms of use even allow it.
AquaEcho

#479 Oct 8, 2023, 11:13 PM Source

ATT_Turan said:
Personally, I think you're also unlikely to find people interested in converting other authors' plugins to be compatible with MZ for free - presuming the author's terms of use even allow it.
And yet Restart did it which is a bummer he left.
jackass__

#480 Oct 8, 2023, 11:16 PM Source

Edael said:
Anyone have a fix for this at all, running into the same error ever time any attack happens.
You just need to add a "?" at this line 11496 after animationSprites in the Mog_chronoengine.js

Also disable Mog_damagepop.js plugin, it doesn't work on Fossil since it use font instead of .png to showcase damage popups.
ATT_Turan

#481 Oct 8, 2023, 11:19 PM Source

AquaEcho said:
And yet Restart did it which is a bummer he left.
He did? I'm not familiar with that.

Regardless, I think my point stands :stickytongue:
Edael

#482 Oct 9, 2023, 03:07 AM Source

jackass__ said:
You just need to add a "?" at this line 11496 after animationSprites in the Mog_chronoengine.js

View attachment 279502

Also disable Mog_damagepop.js plugin, it doesn't work on Fossil since it use font instead of .png to showcase damage popups.
I appreciate you very much sharing this,
I'm glad someone could help out
Thank you :)
Edael

#483 Oct 16, 2023, 06:35 PM Source

So I'm using mog_battlehud and It seems there's a bug when selecting a skill and then selecting an enemy, as normally when selecting an enemy the skill window would be hidden, however instead it's only hiding the graphic used but not the skills themselves

When selecting skill

When selecting target

Have all my other plugins disabled besides FOSSIL(1.0.13) and mog_battlehud
nothing I've done has worked, anyone know a fix for this? Maybe a way to hide the help window as well, thanks.
jackass__

#484 Oct 22, 2023, 10:34 PM Source

Anyone else having trouble saving using chrono engine with fossil ?
Can find a way to fix it, seems caused by how mz handle saving..
ATT_Turan

#485 Oct 22, 2023, 10:46 PM Source

jackass__ said:
Anyone else having trouble saving using chrono engine with fossil ?
Yes, if you search for it there are a number of threads about it.

@AquaEcho probably has specific information off the top of her head. Or you could Google it while you're waiting :wink: