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

Naridar

#526 May 10, 2024, 06:45 PM Source

There's a minor visual bug with VE Materia System plugin: when changing actors with PageUp/PageDown on the Materia screen, their HP and MP values overlap/glitch/don't update. This is most likely an issue with FOSSIL, as it's not present in MV.

To replicate, just create a blank project, install VE Basic Module and VE Materia (no need to configure anything) , and look at the materia screen with the default actors.

Haven't tested if other plugins with similar screens suffer from the same issue. Also probably not worth fixing it, as it's incompatible with VisuMZ Core (and therefore all of their plugins) anyway.
firestalker

#527 May 19, 2024, 06:07 AM Source

I'm really sad now... the JS Link and the Demo Link are broken. Can't get this plugin anymore now...
Animebryan

#528 May 19, 2024, 06:41 AM Source

firestalker said:
I'm really sad now... the JS Link and the Demo Link are broken. Can't get this plugin anymore now...

Arthran said:
My link still works like a champ.
firestalker

#529 May 19, 2024, 08:05 AM Source

Thnk you thank you!
FrankVector

#530 Jun 7, 2024, 08:27 PM Source

YEP_PartyLimitGauge Cost per skill doesn't work.
Aerosys

#531 Jun 7, 2024, 09:25 PM Source

It sometimes still bugs me how this plugin was advertised as silver bullet for every MV plugin, but the reality is, when an MV plugin works with it, feel happy, when it doesn't, then there's no realistic chance rn. You should look for something else.
maxdevige

#532 Jun 30, 2024, 08:40 PM Source

Hello,

Thank you for your wonderful work. FOSSIL has helped me run a very important plugin for my game and it works great in playtesting.

Unfortunately, it's a web game and when I put it online, I get the error :

ReferenceError
nw is not defined

How can I get around this?

Thank you for your help
Aerosys

#533 Jun 30, 2024, 09:00 PM Source

maxdevige said:
Hello,

Thank you for your wonderful work. FOSSIL has helped me run a very important plugin for my game and it works great in playtesting.

Unfortunately, it's a web game and when I put it online, I get the error :

ReferenceError
nw is not defined

How can I get around this?

Thank you for your help

FOSSIL creates a 'FOSSILindex.html' file at runtime, and switches to use it
instead of the original index.html. This works seamlessly in both playtest
and deploy on my computer. However, it is possible this might not be
possible in web or mobile environments (I can't test it). However, if you
just rename an existing FOSSILindex.html to index.html it'll bypass the
html creation step and proceed onwards.
If you want to edit the index.html yourself directly, just replace
'main.js'
with
'plugin/FOSSIL.js'
Basically I replace 'main.js' in index.html with 'FOSSIL.js' so I can
control when plugins are added.
maxdevige

#534 Jul 1, 2024, 07:20 AM Source

Thanks for your reply,

I tried to rename FOSSILindex.html to index.html but it doesn't change anything. Same thing, of course, replacing 'main.js' with 'plugin/FOSSIL.js' in index.html...

I keep getting "ReferenceError nw is not defined", I don't even know what nw refers to...
I tried to create a new project with RMMV to see if I could find a "nw.js" or something like that somewhere that I could drag into my RMMZ project, but nothing...

Would you have an idea of a "nw" reference I could add somewhere, in combination with the change to index.html perhaps?

Thanks a lot for your help

Aerosys

#535 Jul 1, 2024, 08:29 AM Source

You are right, nw is not included in the game, so I really have to guess here.

Can you try starting your game in another browser or on another device (iPhone, Android Phone, etc.)?

Furthermore, I would try doing this: In FOSSIL, look for:

Code:

writeNewIndexFile = function(rawIndexHtml) {
        //next, we take the newIndexHtml and replace 'main.js' with '/plugins/Fossil.js'
        rawIndexHtml = rawIndexHtml.replace("main.js", "plugins/FOSSIL.js");
        var fs = require("fs");
        var path = require('path');
        var base = path.dirname(process.mainModule.filename);
        var filePath = path.join(base, 'FOSSILindex.html');
        //var data = createWrapperObject(, orderedResult, unknownPlugins);
        fs.writeFileSync(filePath, rawIndexHtml);
        //synchronous writing means that we can guarantee this is in place 
        //for when we ridirect to the new html.
        
    };

and replace it with

Code:

writeNewIndexFile = function(rawIndexHtml) {
    // just do nothing
    };

maxdevige

#536 Jul 1, 2024, 12:35 PM Source

Hello,

Thanks a lot, I tried that:

- By changing the portion of code you suggest, I unfortunately still have the same "ReferenceError nw is not defined"
- same thing with other browsers.

I'm trying to install on Android, but the goal is for it to work on a browser. I've already found that it works without a problem on Windows in any case.
Aerosys

#537 Jul 1, 2024, 01:27 PM Source

When you see the error, please to this:

1. Right-click, inspect
2. Go to "Console" tab
3. When you see that some lines are "collapsed", expand them (see screenshot) so we can see everything.

4. Screenshot the entire dialog and share it here for us

Last but not least, tell us which OS and browser you are using, e.g. Chrome on Windows 11
maxdevige

#538 Jul 1, 2024, 02:35 PM Source

Thanks. Ok so here is the screenshot of the console :
(I'm using Mozilla Firefox on Windows 10)
Aerosys

#539 Jul 1, 2024, 02:36 PM Source

You need to go to "Console" tab.
maxdevige

#540 Jul 1, 2024, 06:53 PM Source

Sorry... :aswt:
Aerosys

#541 Jul 1, 2024, 07:25 PM Source
As you can see, multiple plugins throw errors, e.g. "nw is not defined" comes from YR_CCEx...

Unfortunately, this console doesn't tell you whether...
- FOSSIL is the troublemaker or
- the plugin does not work on MZ in any way and cannot be carried by FOSSIL, or
- the plugin creator forgot to make their plugin compatible with browser games; then it has nothing to do with FOSSIL.
I just looked into the one plugin and claim that nr 3 hit here.

Open the plugin, and look for
Code:
GameWindowManager.window = (Utils.RPGMAKER_NAME == "MZ") ? nw.Window.get() : require('nw.gui').Window.get();
Replace it with
Code:
if (Utils.isNwjs()) { GameWindowManager.window = (Utils.RPGMAKER_NAME == "MZ") ? nw.Window.get() : require('nw.gui').Window.get(); }
If that still doesn't work, I suggest opening a new thread and asking about this plugin in particular because the problem isn't really connected to Fossil itself.
ATT_Turan

#542 Jul 1, 2024, 08:15 PM Source

@maxdevige None of those errors are coming from FOSSIL.

The first one is that it isn't loading an xml file required by SRD's Character Creator.

The rest of the errors read like there's a typo or incomplete file which is causing all the code of the other plugins to be read incorrectly because it talks about things being not defined or not functions which are.

But the SRD stuff is probably the root of your problem - there are several threads which discuss some of his plugins not working correctly on mobile. You would have to look up whether Character Creator (or anything else in your project) is one of them.
maxdevige

#543 Jul 2, 2024, 08:37 AM Source

Hello and thank you for your answers.

When I noticed the bug, I started by deactivating the various plugins one by one. I thought I noticed that the error was appearing even though only the FOSSIL plugin was activated (which is why I came to ask the question here in the first place).

So I started again from scratch: I don't know what I've screwed up, but the problem actually seems to come from "YR_CCEx_Xs_no_GameUpgrade", which I added on top of FOSSIL to make "CharacterCreatorEx" work.

Aerosys, I made the modification you suggested in "YR_CCEx_Xs_no_GameUpgrade" and now the game runs.

I then add the next plugin on my list which is "SRD_SuperToolsEngine". This time I get a "ReferenceError process is not defined" error. In the console, I again see problems coming from "FOSSIL", so I redo the manipulation to replace the content of index.html with that of FOSSILindex.html. This eliminates quite a few errors, but I still get "ReferenceError process is not defined".

Here's the screen:

When I click on the error in the console, this is what I get:

I won't say it every time, but I want you to know that I'm extremely grateful to you for taking the time to help a noob like me with his little game.
Thank you. very. much.
Aerosys

#544 Jul 2, 2024, 09:09 AM Source

"FOSSIL is now running as main", only tells you that FOSSIL is running - that's fine.

As ATT_Turan and I already mentioned, the problems are more likely to come from SRD than FOSSIL. Apparently, SRD forgot to check whether his work works on mobile/web deployment, so you are probably better by googling "SRD plugins web deployment" or opening a new thread.

I'm happy to help fixing one or maybe 2 plugins, but not a whole bunch of them :)
maxdevige

#545 Jul 2, 2024, 01:04 PM Source

Thanks again for your answers and help, I'll ask on the super-tools-engine forum. If I get anything, I'll come back and post the solution here.