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

Krystek_My

#204 Jun 13, 2021, 08:31 PM Source

Restart said:
odd, I'll look at it. One of the things I've been trying to do is get the animation.frames.length shortcut used by MV plugins to assess the duration of an animation to work on MZ-native animations (which don't have any frames), so it's possible that this has messed up something somewhere. Do you have the latest version?
I have everything latest, the author said that the handling of animation in your plugin makes the problem. I can provide sample project
Restart

#205 Jun 13, 2021, 08:47 PM Source

Krystek_My said:
I have everything latest, the author said that the handling of animation in your plugin makes the problem. I can provide sample project
I just pushed a fix, try it now. Basically I now fall back to original behavior for detecting MV vs MZ animations if my startup code hasn't run on a particular animation.

So long as nobody has a both a plugin that makes a separate animation database which contains MZ animations (which I don't think exists ATM), and also a MV plugin that uses the animation.frames.length trick at the same time, it shouldn't be an issue again, and I can always do a patch to address it at that point.
Solar_Flare

#206 Jun 13, 2021, 11:05 PM Source

This is pretty amazing, and the list of compatible plugins is quite something too. I wonder if anyone has tried using the Actors Friendship System with FOSSIL? I seem to recall at least one person asking if it's MZ compatible.

I'm also kind of curious how many of my own plugins would work with FOSSIL, but they're probably not widely-used enough to justify you spending time checking them.
Restart

#207 Jun 13, 2021, 11:58 PM Source

Solar_Flare said:
This is pretty amazing, and the list of compatible plugins is quite something too. I wonder if anyone has tried using the Actors Friendship System with FOSSIL? I seem to recall at least one person asking if it's MZ compatible.

I'm also kind of curious how many of my own plugins would work with FOSSIL, but they're probably not widely-used enough to justify you spending time checking them.
You can always try them yourself :) If it works I'll add it to the list.
Solar_Flare

#208 Jun 14, 2021, 04:14 AM Source

I would, but I don't have MZ yet.

If I ever get MZ, and no-one has tried it by then, then I'll try it.
DarkSearinox92

#209 Jun 14, 2021, 08:05 AM Source

Hey @Restart , some news about YEP Sideview enemies?
Restart

#210 Jun 14, 2021, 05:08 PM Source

DarkSearinox92 said:
Hey @Restart , some news about YEP Sideview enemies?
this one?
Animated Sideview Enemies (YEP) - Yanfly.moe Wiki
should be working last I checked
Restart

#211 Jun 16, 2021, 01:44 AM Source

Just got Knight Editor Visual Doodad Editor working with FOSSIL.

Knight Editor is an add-on for grid free doodads which gives it a much improved user interface (with features like undo and selecting doodads by clicking on them). If you use doodads on your map I highly recommend it.

I also added ALOE conditional choices, a nice plugin that lets you disable or hide commands in a choice list by putting tags directly into the choice text.
DarkSearinox92

#212 Jun 16, 2021, 07:27 AM Source

Restart said:
this one?
Animated Sideview Enemies (YEP) - Yanfly.moe Wiki
should be working last I checked

I will try it again!! This project is becoming amazing, really!!!
BrentBAM

#213 Jun 17, 2021, 07:18 AM Source

Restart said:
Okay, I think I found the issue - your project probably has an older version of MZ which lacks a few functions. Update to 1.2.1

Hey Restart. I updated my MZ. I'm still getting that issue when using YEP_victory aftermath. I still get the label measure width error.

It may be another plugin but I'm not sure. The Fossil and Victory Aftermath DO work when I make a new project w/o other plugins. But for some reason it doesn't work in my game and not sure what plugin would be affecting it.

Have any other ideas about a fix?
Restart

#214 Jun 19, 2021, 03:05 AM Source

BrentBAM said:
Hey Restart. I updated my MZ. I'm still getting that issue when using YEP_victory aftermath. I still get the label measure width error.

It may be another plugin but I'm not sure. The Fossil and Victory Aftermath DO work when I make a new project w/o other plugins. But for some reason it doesn't work in my game and not sure what plugin would be affecting it.

Have any other ideas about a fix?
I am travelling so don't have time to do anything with code, so this is just a guess:

Check to make sure you updated the project's core files as well as the editor. there's a dropdown in the editor menu to do it somewhere, ask someone else on the forums about it since I can't check it myself
BrentBAM

#215 Jun 19, 2021, 07:02 AM Source

Restart said:
I am travelling so don't have time to do anything with code, so this is just a guess:

Check to make sure you updated the project's core files as well as the editor. there's a dropdown in the editor menu to do it somewhere, ask someone else on the forums about it since I can't check it myself
Restart! Thanks so much!

That fixed it perfectly. Victory Aftermath works now. I never knew I had to use update the core files too. Even made my game slightly faster too lol.

Wow, thanks again though. appreciate the help in this.
Oiram19

#216 Jun 21, 2021, 01:03 PM Source

Hi!! First of all, i want to congratulate you for this awesome plugin! I want to use YEP_WeaponAnimation and i don't know why, it doesn´t work. I'm using YEP_EquipCore (which works correctly) and YEP_WeaponAnimation, maybe i have to change the notetags <Weapon Image: x>?
Lranger

#217 Jun 22, 2021, 04:50 PM Source

Hi, first of all, thanks for making this plugin. This is truly amazing and I really appreciate your effort. However I can't seem to get it to work with SRD Camera Core and the error below poped up. Is there any possible solution to this? I have little programming knowledge so I'm clueless on what to do to troubleshoot.
rafman2k

#218 Jun 24, 2021, 11:55 AM Source

@Restart any chance to use this to get your chrose engine project file working in MZ ?
Restart

#219 Jun 24, 2021, 06:42 PM Source

rafman2k said:
@Restart any chance to use this to get your chrose engine project file working in MZ ?
not likely, it's more a byproduct of my own gamedev than something I'm actively working on as a standalone project. Since I do some version-specific pixi stuff, ironically I can't actually port my own project. So it goes.
If anyone wants to do a spinoff of cross engine it they are free to do so.

Anyway hopefully should be able to resume work soonish,
kamster94

#220 Jun 26, 2021, 09:40 PM Source

Hi. Has anyone tried to run YEP Turn Order Display with Visustella plugins? I need YEP battle core for this of course. When I try to load both of them with visustella core + battle core, it crashes when battler move. However, when I disable visustella battle core but leave core engine enabled, YEP turn order display is not showing at all. Does anyone have a solution for that?
Restart

#221 Jun 27, 2021, 12:50 AM Source

kamster94 said:
Hi. Has anyone tried to run YEP Turn Order Display with Visustella plugins? I need YEP battle core for this of course. When I try to load both of them with visustella core + battle core, it crashes when battler move. However, when I disable visustella battle core but leave core engine enabled, YEP turn order display is not showing at all. Does anyone have a solution for that?
Odd, I've tried YEP_BattleEngineCore and YEP_X_TurnOrderDisplay together and they worked for me. Is it possible there's a plugin conflict?

Otherwise, you can try moghunter's MZ-native turn order plugin and see if that works.
kamster94

#222 Jun 27, 2021, 08:35 AM Source

Restart said:
Odd, I've tried YEP_BattleEngineCore and YEP_X_TurnOrderDisplay together and they worked for me. Is it possible there's a plugin conflict?

Otherwise, you can try moghunter's MZ-native turn order plugin and see if that works.
Yeah, there is a conflict for sure, but not between YEP plugins, but between YEP and Visustella's. I sudpect it would be hard to make both battle cores work togerher, as they touch the same aspects, but when I disable visustella battle core, but leave core engine enabled for other visustella plugins, turn order display is not showing at all
Jrrkein

#223 Jun 27, 2021, 08:45 AM Source

Can you least try the alternative -_-