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

Restart

#21 Apr 18, 2021, 10:57 PM Source

thenerdmansion said:
I understand. Thank you for your honest attempt at trying to fossil this plugin :D.
I did try to skip animations by having the plugin play animation 0 but it would still
crash, at least we tried :D/
To be clear, if you use the animations file from a MZ project it won't crash. The crash is caused by trying to reference a MV animations file in MZ

ImaginaryVillain said:
All of these were done with a brand new MZ project, core script 1.2.1. Regrettably none of them worked. I'd be happy to test a lot of the other QPlugins once the QPlus problem is resolved.

qplus
View attachment 186602

Gradient Wipe
View attachment 186603

Ultra Mode 7
View attachment 186604

Yeah I'm not touching ultramode7 with a 10 foot pole :p. I have heard there are a lot of under-the-hood changes with pixi and trying to do a roundabout interface layer seems like a real nightmare. Same goes for MV3D and other big rendering engine changes (as well as any plugin that tweaks the MV animation system).

I'll poke at QPlus and see if I can get something together to make it behave.

Anyway, have pushed another update to github.

YEP_BuffStatesCore and YEP_AutoPassiveStates are now functional in MZ.

I think I have StatusMenuCore fossilized to an acceptable level now. The most noticeable difference is that I didn't bother making the parameter graph as pretty as it is in MV

MV:

MZ:

but TBH I never really used found that graph useful anyway, and since all the information is being displayed in a comprehensible fashion, I think that's Someone Else's Problem.
ImaginaryVillain

#22 Apr 18, 2021, 11:23 PM Source

Entirely fair. I mostly just added Ultra Mode 7 on there as a joke since I already made the MV3D joke last time. To be honest I'm a bit hard pressed to find a plugin that doesn't already have a replacement plugin for MZ. Most of what isn't, is the extreme plugins that do drastic changes.

On the plus side, the QPlugins don't have a complete port yet. I suspect a lot of people would love to see those working correctly on MZ.
Restart

#23 Apr 19, 2021, 12:40 AM Source
Anyway, qplus is freely redistributable and editable, so if you wanna make a port that's totally fine. It's also wrapped, which limits interoperability; once again, porting seems to be the best option (and honestly, it seems like this plugin has features that aren't documented in the intro, so I can't really test whether or not they're working).

If you want to just get it to not crash, comment out these sections
Code:
//----------------------------------------------------------------------------- // Graphics //----------------------------------------------------------------------------- // Scene_Boot //----------------------------------------------------------------------------- // Scene_Map
You'll lose the quick test option and the tweaked error information, but whatever. Technically the quick test 'works', but it forgets to load the graphics so the game is running with the screen totally blank.

Anyway, Shaz_TileChanger works.
ImaginaryVillain

#24 Apr 19, 2021, 01:19 AM Source

Oh yeah, a couple of months back I did something similar to that. Did some quick edits for 8 of the plugins and tossed them up on my GitHub. They currently break with MZ's menu system, which isn't really a problem for me since I don't use it. However I was just hoping this would solve the problem for other people looking to use them.

Anyway, I'll likely end up testing some other plugins later, and see how it goes. Now that I know you're looking to avoid wrapped code that should help limit which plugins are worth looking at.
Restart

#25 Apr 19, 2021, 06:51 PM Source

Blaon said:
I think it does not make SRD summon core plugin from MV work.
Summon Core – MV Plugin – RPG Maker MZ Plugins I get a can't read length from undefined error.
Other plugins seem to work tho! Great work!
Try summoncore now.
SirTophamHakurei

#26 Apr 19, 2021, 07:15 PM Source

This is fantastic! I tried this out with the Gameus Quest System and it works! Text is a bit small, BUT IT WORKS! Haha! Now I have an easier to use Quest system in MZ! Thank you man!
Restart

#27 Apr 19, 2021, 07:18 PM Source

AeroPergold said:
This is fantastic! I tried this out with the Gameus Quest System and it works! Text is a bit small, BUT IT WORKS! Haha! Now I have an easier to use Quest system in MZ! Thank you man!
Thanks! I'll add it to the list :)
RustyVanBurace

#28 Apr 19, 2021, 07:36 PM Source

The premise of this sounds really interesting and I commend your team on their incredible work.

But I am also concerned about something. I know that with the Yanfly Engine, Yanfly had explicitly expressed in his retirement message that he does not permit the porting of his scripts outside of the VisuStella team. To do so would be breaking his terms.

Although while yes this is not actual porting by technicality, it still makes me wonder if this would still fall under disallowed usage and break Yanfly's terms. Especially when the VisuStella team themselves have been porting his scripts, which have to be bought.

I don't have MZ. And if I did, I would buy VisuStella's ports. I'm just a little concerned and wondering if any of the above has been discussed.
SirTophamHakurei

#29 Apr 19, 2021, 07:38 PM Source

Restart said:
Thanks! I'll add it to the list :)
Okay so a few things: It only works if added to the bottom of the list and if at the bottom of the list and the sample quest is complete the game and then the ESC button is pressed this appears:

If placed at the top of the plugin list it works as intended except for the UI:

So yeah it works but not at 100%
Restart

#30 Apr 19, 2021, 07:44 PM Source

HiddenAlchemist said:
The premise of this sounds really interesting and I commend your team on their incredible work.

But I am also concerned about something. I know that with the Yanfly Engine, Yanfly had explicitly expressed in his retirement message that he does not permit the porting of his scripts outside of the VisuStella team. To do so would be breaking his terms.

Although while yes this is not actual porting by technicality, it still makes me wonder if this would still fall under disallowed usage and break Yanfly's terms. Especially when the VisuStella team themselves have been porting his scripts, which have to be bought.

I don't have MZ. And if I did, I would buy VisuStella's ports. I'm just a little concerned and wondering if any of the above has been discussed.

The specific issue yanfly had was with people redistributing his scripts - if you make a port of YEP_doodads or whatever for yourself that's not an issue. The problem arises when someone takes YEP_doodads, makes their own YEP_doodads_MZ, then starts giving it to other people.
SirTophamHakurei

#31 Apr 19, 2021, 07:49 PM Source

Restart said:
The specific issue yanfly had was with people redistributing his scripts - if you make a port of YEP_doodads or whatever for yourself that's not an issue. The problem arises when someone takes YEP_doodads, makes their own YEP_doodads_MZ, then starts giving it to other people.
Not to be a bugbear and to come at the risk of being mildly annoying, I have provided some feedback as played around with the plugin with Gameus Quest System. It works but has some odd quirks dependent if you put it at the top of a list of plugins or at the bottoms, as well as the text appearing small and not using the fonts set in the database.
RustyVanBurace

#32 Apr 19, 2021, 07:53 PM Source

Restart said:
The specific issue yanfly had was with people redistributing his scripts - if you make a port of YEP_doodads or whatever for yourself that's not an issue. The problem arises when someone takes YEP_doodads, makes their own YEP_doodads_MZ, then starts giving it to other people.
Ah, yes that makes much more sense. Thanks for the clarification. :thumbsup-left:
Restart

#33 Apr 19, 2021, 08:04 PM Source

AeroPergold said:
Okay so a few things: It only works if added to the bottom of the list and if at the bottom of the list and the sample quest is complete the game and then the ESC button is pressed this appears:
View attachment 186728
View attachment 186729
If placed at the top of the plugin list it works as intended except for the UI:
View attachment 186733

So yeah it works but not at 100%
Okay, I've filed it under WIP in the OP. I'll fiddle around with a demo later
SirTophamHakurei

#34 Apr 19, 2021, 08:06 PM Source

Restart said:
Okay, I've filed it under WIP in the OP. I'll fiddle around with a demo later
Thank you, if you need help or extra info I'll provide it.
Equinox-ThiefofHearts

#35 Apr 19, 2021, 09:18 PM Source

Hi! This is a personal suggestion very likely, but do you think you can get this working with JM's Earthbound Backgrounds?

*EDIT*
Can also confirm, aside from Circle and Clock, SRDude's Timed Attack System works.
thenerdmansion

#36 Apr 20, 2021, 02:37 AM Source

Does anyone have the Moghunter Chrono engine on their computer? Now that moghunters website, youtube and twitter have been deleted the only way to get it is from someone that already has it :(. I hope all is well with moghunter as well.
jad4321

#37 Apr 20, 2021, 06:45 AM Source

thenerdmansion said:
Does anyone have the Moghunter Chrono engine on their computer? Now that moghunters website, youtube and twitter have been deleted the only way to get it is from someone that already has it :(. I hope all is well with moghunter as well.
Hey I got you, hopefully, this is it, had it sitting around my back ups. Hope all is going good as well, woke up and everything was gone. <snip>

Also I'll be checking this script out as soon as I get some time. It's great more is being done to port over MV scripts to MZ.
slimmmeiske2

#38 Apr 20, 2021, 07:27 AM Source

@jad4321 I've removed that link. Please see this message why.
@thenerdmansion Please don't request plugins in this thread, unless it is to get them to work with Project FOSSIL. Regarding the Moghunter situation, please see this message.
jad4321

#39 Apr 20, 2021, 09:12 AM Source

slimmmeiske2 said:
@jad4321 I've removed that link. Please see this message why.
@thenerdmansion Please don't request plugins in this thread, unless it is to get them to work with Project FOSSIL. Regarding the Moghunter situation, please see this message.
Hey gotcha sorry about that.
Restart

#40 Apr 20, 2021, 04:11 PM Source

YEP_BattleEngineCore now works, except for the 'Select Help Window' parameter.

That's the one that brings up a window saying 'all enemies' or '3 random targets' or 'yourself' or whatever on skills that normally don't ask for targeting.

With the parameter enabled it technically 'works', but it also brings up a confusing 'select targets' window that gets ignored every time you use a nonselecting skill. Since it's on by default, for the time being I'm just scanning the plugin parameters and having FOSSIL tell you it's turning 'select help window' off in the console.

I think this probably isn't a make-or-break feature for most users, so I'm counting it as 'done'.

Onwards to Gameus Quests!