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

Arthran

#344 Jan 7, 2022, 11:32 PM Source

Pondis said:
Evening all. I am having trouble getting WAY_StorageSystem to work with FOSSIL, but I suspect I am doing something wrong.

FOSSIL says both are compatible with it, I have FOSSIL, then WAY_Core, then WAY_StorageSYstem in my plugin list which I think is right.

I havent updated the FOSSIL.js, I am not sure I need to, though the front page of this thread mentions it.

Long story short, I dont know what I am doing and I need a storage system!

Thanks
Can you describe the manner in which it's failing to work?
Skurge

#345 Jan 8, 2022, 04:09 AM Source

I'm very new to MZ and currently testing it out on a trial version, I've been struggling to get the particle animations working alongside the older MV Yanfly battle plugins, sideview-sequences etc.
Followed the steps as accurately as possible and for whatever reason playtest boots up to a frozen blank screen, the bottom of the plugin manager will keep referring to the next plugin down the list "may not support MZ" despite being on the working list. I'll try to figure out what's happening.
Pondis

#346 Jan 8, 2022, 01:40 PM Source

Arthran said:
Can you describe the manner in which it's failing to work?
Of course, sorry I should have thought of that.

If I use the script call "oldCommand($gameStorageSystems.open(0))" I get "Cannot read property 'split' undefined"

If I use the script call "oldCommand(gameStorageSystems.open(0))" I get "gameStorageSystems is not defined"
Raven Guertena

#347 Jan 8, 2022, 05:45 PM Source

zerobeat032 said:
actually the input combo plugin isn't considered YEP as far as I can see. it's one of the few visustella plugins for MV, along with Active Chain Skills. https://visustella.itch.io/input-combo-skills... but yeah, neither have been ported to MZ as of yet it seems.

https://forums.rpgmakerweb.com/index.php?threads/quick-time-events-r2-26-11.71268/ this is a good alternative tho and it does work with FOSSIL.
Ah thanks, someone who actually did their bit of research on the MZ visualstella plugins @-@ Not trying to blame anyone here, but when I said that I did not found the said pluging in the Mz line and only with the mv line, then I really meant that.

and thanks, might take a look to that
Raven Guertena

#348 Jan 8, 2022, 06:45 PM Source

zerobeat032 said:
https://forums.rpgmakerweb.com/index.php?threads/quick-time-events-r2-26-11.71268/ this is a good alternative tho and it does work with FOSSIL.

just uuh....how do I turn it into a js file- I literly do not have the program and I didn't found a proper download link for it

edit, nvm
Arthran

#349 Jan 8, 2022, 09:06 PM Source

Pondis said:
Of course, sorry I should have thought of that.

If I use the script call "oldCommand($gameStorageSystems.open(0))" I get "Cannot read property 'split' undefined"

If I use the script call "oldCommand(gameStorageSystems.open(0))" I get "gameStorageSystems is not defined"
No problem. Luckily, it looks like your problem should be simple to solve. The issue is that you're using oldCommand() incorrectly. You only need to use it to execute old plugin commands, but what you're sticking inside of it is not a plugin command (it's a script call). Try $gameStorageSystems.open(0); by itself, without oldCommand(), and see if that works.
Pondis

#350 Jan 9, 2022, 03:24 PM Source

Arthran said:
No problem. Luckily, it looks like your problem should be simple to solve. The issue is that you're using oldCommand() incorrectly. You only need to use it to execute old plugin commands, but what you're sticking inside of it is not a plugin command (it's a script call). Try $gameStorageSystems.open(0); by itself, without oldCommand(), and see if that works.
I expected it was me not using something correctly!

However its still not working.

I get "Cannot read property 'replace' of null"

EDIT Never mind, I figured it out. The settings has an Info Window Title which I left blank, but after adding it in I found it works.
NikaraWorld

#351 Jan 19, 2022, 02:47 AM Source

welp this would've been nice to know about before I requested a mz plugin for movement

EDIT: It seems that SRD SummonCore doesn't work even though it's supposed to it crashes with TypeError: Cannot read property 'length' of undefined
EDIT 2: I had a plugin that was also summoning actors which I turned off but now i'm getting Maximum Call Stack exceeded which seems to happen when something is infinitely calling itself, am I doing something wrong it's still the SRD SummonCore MV plugin
Arthran

#352 Jan 19, 2022, 04:45 AM Source

NikaraWorld said:
welp this would've been nice to know about before I requested a mz plugin for movement

EDIT: It seems that SRD SummonCore doesn't work even though it's supposed to it crashes with TypeError: Cannot read property 'length' of undefined
EDIT 2: I had a plugin that was also summoning actors which I turned off but now i'm getting Maximum Call Stack exceeded which seems to happen when something is infinitely calling itself, am I doing something wrong it's still the SRD SummonCore MV plugin
I tested SRD SummonCore with FOSSIL about a month ago, and it worked just fine. TBH, you're probably doing something wrong, or you've got some kind of conflict between your plugins.
NikaraWorld

#353 Jan 19, 2022, 05:17 PM Source

Arthran said:
I tested SRD SummonCore with FOSSIL about a month ago, and it worked just fine. TBH, you're probably doing something wrong, or you've got some kind of conflict between your plugins.
Well it wouldn't be the first time i'm doing something wrong. Has anybody tested SRD SummonCore with visual stella plugins. The game loads with the summon core plugin above all VisuMZ plugins but when I go into battle it crashes again.

EDIT: I sorta got it figured out, but how do you actually battle with the summoned actor, it seems I can't select or battle with summoned actor.
Arthran

#354 Jan 19, 2022, 07:29 PM Source

When I tested it, I also had VisuStella Battle Core active, and it worked just fine. IIRC, you don't manually select the summoned actor. Just go about the battle like normal, and the summoned actor will get turns too, just like everybody else.
NikaraWorld

#355 Jan 19, 2022, 07:54 PM Source

Arthran said:
When I tested it, I also had VisuStella Battle Core active, and it worked just fine. IIRC, you don't manually select the summoned actor. Just go about the battle like normal, and the summoned actor will get turns too, just like everybody else.
The problem is that the summoned actor doesn't do anything, they just stand there, they don't attack or anything. I even added the Auto-Battle flag in actor info, either I'm just having bad luck or something broke since you last tested it
Arthran

#356 Jan 19, 2022, 11:06 PM Source

@NikaraWorld
Neither Summon Core nor FOSSIL have changed over the past month, so I dunno why it wouldn't be working for you. But if you wanna upload your project (or a demo project that replicates the same issue) somewhere, and PM me a link, I can take a look at it for you and see if I can locate the issue.
NikaraWorld

#357 Jan 20, 2022, 12:32 AM Source

Arthran said:
@NikaraWorld
Neither Summon Core nor FOSSIL have changed over the past month, so I dunno why it wouldn't be working for you. But if you wanna upload your project (or a demo project that replicates the same issue) somewhere, and PM me a link, I can take a look at it for you and see if I can locate the issue.
I will make it but not today as it's not all that crucial
McSundae

#358 Jan 27, 2022, 09:54 PM Source

Hello there,
first let me say that this script is absolutely genius. So much good scripts that are simply not lost :)

Sadly i found a plugin that doesn't seem to work out of the box, it's also not included in your list, but i would love to see it happen:
GitHub - munokura/Warehouse-MV-plugin: This plugin allows the creation of warehouses where you can store items in the game.
Game is able to start, and the create Storage Command works, but when i call the show storage command i get following crash: "Cannot read property 'constructor' of undefined
DarkSearinox92

#359 Feb 16, 2022, 08:30 PM Source

So... news about Restart? Or about the maintenance of this project?
ScytheX

#360 Feb 18, 2022, 12:52 AM Source

how do i use this? its just text and idk now to make it in to a js file :/
_SynergyOfLove_

#361 Feb 18, 2022, 03:58 AM Source

ScytheX said:
how do i use this? its just text and idk now to make it in to a js file :/
On the Raw, hit Ctrl+s.
It'll download the .js
ScytheX

#362 Feb 18, 2022, 06:00 AM Source

_SynergyOfLove_ said:
On the Raw, hit Ctrl+s.
It'll download the .js
ty c:
DarkSearinox92

#363 Feb 19, 2022, 05:43 PM Source

ScytheX said:
how do i use this? its just text and idk now to make it in to a js file :/

If you have text, on browser you can use right click and do "save as".

Or you can copy all of the text, put it into a notepad and then save it as "nameoftheplugin.js"