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

AquaEcho

#486 Oct 22, 2023, 10:53 PM Source

Unfortunately I do not and it's not something I can look into myself as I don't have MZ. Presumably it's a general MV/MZ save data incompatablity issue and not specific to ChronoEngine.
jackass__

#487 Oct 22, 2023, 11:05 PM Source

ATT_Turan said:
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:
I did search and post about it but all I found was mostly about mv save problems (buzz sound) and hudell orange circular json, but nothing about this (as it's not obvious, the save works at start but won't when use certains items skill or else).

AquaEcho said:
Unfortunately I do not and it's not something I can look into myself as I don't have MZ. Presumably it's a general MV/MZ save data incompatablity issue and not specific to ChronoEngine.
I really think it is linked to how ChronoEngine handle saving and clash with mz, I've done a test project with only fossil and the chronoengine plugin, were the save work but when using an item it block saving and if I copy this item in another slot (of the items id list) and select It in the property event same works.
I just don't really understand why and so have a hard time to correct it instead of some weirds workaround like copying every item and skill in the database and relink them to events.

I tried even with the chrono engine demo and fossil in mz and same problem occurs.
AquaEcho

#488 Oct 22, 2023, 11:18 PM Source

That sounds like it might have something to do with the json file holding the premade item data(maybe skills, enemies, etc too) if the existing items don't work but newly created ones do.
jackass__

#489 Oct 22, 2023, 11:28 PM Source

AquaEcho said:
That sounds like it might have something to do with the json file holding the premade item data(maybe skills, enemies, etc too) if the existing items don't work but newly created ones do.
Both items works but in the first case the save is blocked, maybe just the id impact the save but not sure how.
As before this test project to search for the bug, I've ported my entire game on mz and everything works (items skills) only the save I sometimes compromised
AquaEcho

#490 Oct 22, 2023, 11:39 PM Source

jackass__ said:
Both items works but in the first case the save is blocked, maybe just the id impact the save but not sure how.
As before this test project to search for the bug, I've ported my entire game on mz and everything works (items skills) only the save I sometimes compromised
Check the entries in the json files to see if there is any difference in the formatting between the preexisting entries and the newly created ones.
jackass__

#491 Oct 23, 2023, 12:11 AM Source

AquaEcho said:
Check the entries in the json files to see if there is any difference in the formatting between the preexisting entries and the newly created ones.
So I just check in item.json and there's none in the code line other than the id

screenshot
this line is the item id 7 ho block saving, on the bottom of the list the id 16 is the copy of 7 i made in database and the save works, and below it the id 17 is a copy of the line of the id 7 where i just changed 7 to 17 and I tried in game saving work like with id 16.

this is the event line where I change from id 7 (block save) to id 16 or 17
AquaEcho

#492 Oct 23, 2023, 12:41 AM Source

Without being able to test it myself I can't help you that much, and I feel like this isn't really a big issue since it just involves pre-made data being unable to save which you've said you can get around by just copying them to a new database entry.
jackass__

#493 Oct 23, 2023, 12:45 AM Source

AquaEcho said:
Without being able to test it myself I can't help you that much, and I feel like this isn't really a big issue since it just involves pre-made data being unable to save which you've said you can get around by just copying them to a new database entry.
Thanks again for your time, I know you don't use mz but appreciate your help.
The problem is I'm not sur if it's only caused by this since even when I copied every item and skill in a new slot in the database the bug occurs sometimes so it's hard to troubleshoot the error and fix it.
daveycadaver

#494 Nov 11, 2023, 04:07 AM Source

YokoSan said:
Git Mirror https://github.com/EerFree/fossil-MV-MZ/
Last ver. 1.0.13
TY!!
DrapeauNoir

#495 Nov 13, 2023, 11:50 PM Source

Thanks fot the plugin ! it's perfect ^^
Ancient_Eagle

#496 Nov 19, 2023, 12:40 PM Source

I do have problem of AltimitMovement that cross engine was made in mv, so I am convert to MZ, and this is how I got:

Does anyone know how to fix this problem?
Arthran

#497 Nov 19, 2023, 12:42 PM Source

Ancient_Eagle said:
I do have problem of AltimitMovement that cross engine was made in mv, so I am convert to MZ, and this is how I got:

View attachment 284357

View attachment 284358

Does anyone know how to fix this problem?
Someone released a MZ version of Altimit. You'll have to search through the Altimit thread to find it.
Ancient_Eagle

#498 Nov 19, 2023, 12:52 PM Source

Ok, I tried it, but still got error

Edit: Nevermind that, I solved the problem.
Puppet Knight

#499 Jan 19, 2024, 04:02 AM Source

Posting to be able to send a link elsewhere.

xD
Roninator2

#500 Jan 19, 2024, 12:28 PM Source

Puppet Knight said:
Posting to be able to send a link elsewhere.

xD
Is that a different version than
Project FOSSIL (v1.0): Use MV plugins in MZ! 300+ plugins Fossilized! or
GitHub - Arthran2/fossil-MV-MZ: Project Fossil (Fixing Old Software / Script Interoperability Layer) is a series of RPG Maker MZ plugins designed to expand the use and usefulness of RPG MAKER MV plugins, by allowing them to work in RPG MAKER MZ proje or
Project FOSSIL (v1.0): Use MV plugins in MZ! 300+ plugins Fossilized!
Aerosys

#501 Jan 19, 2024, 12:30 PM Source

Well, there's an easy way to check that: https://www.diffchecker.com/
Roninator2

#502 Jan 19, 2024, 12:54 PM Source

Aerosys said:
Well, there's an easy way to check that: https://www.diffchecker.com/
Go ahead and let me know what you find.
Morganis

#503 Jan 23, 2024, 12:01 AM Source

The links to this are broken, any one know where it can be downloaded from?
ATT_Turan

#504 Jan 23, 2024, 01:02 AM Source

Morganis said:
The links to this are broken, any one know where it can be downloaded from?
Did you look at anything besides the very first post? :stickytongue:

If you look three posts back from yourself, there's a post that literally has three links for you to choose from.
Morganis

#505 Jan 23, 2024, 01:22 AM Source

Yeah I found it, thanks. Should have said something. I went through all the posts lol