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

alltheyuriz

#144 May 11, 2021, 09:27 PM Source

Restart said:
can you show me the console log and stacktrace?
How do I get to that?
Restart

#145 May 11, 2021, 09:44 PM Source
a3xgf said:
I downloaded the unCompress dev plugin only because the sample project is down. I tried to follow the video, but if the game doesn't go past the start screen there is not much I can do to test. I will try to ask the creator if it is possible to reupload the sample project.

Edit: I created a project with MV and put the plugin there, same config and no animations set, and in MV doesn't give the error, so there is a problem of compatibility even before being able to put any animations.

Edit2: I am testing on MZ by commenting parts of the code to try to find where is the error, and having uncommented until line 1936 doesn't provoke the crash, same with having from 1997 onwards uncommented (PIXI_extras_AnimatedSprite section).

The culprit seems to be on Sprite_Character_Spriteset_Map between those two sections, as while having only that part commented it doesn't crash. Excluding comments, the code that provokes the error is between 1944 and 1992.

I don't know if it works or not, but at least it isn't instacrash after new game just due to having the plugin active.

Edit3: Managed to cut it down further. The mentioned error is provoked by the lines of code between 1944 and 1947.

It is really two lines of code, so if that is the only problem, I think there is only need to fix these two lines. I don't even know what is their funtion on the script at a whole, but shouln't influence any outside ot the Sprite_Character_Spriteset_Map section.

Spriteset_Map.prototype.initialize = function() { Spriteset_Base.prototype.initialize.call(this); };

Here it is the problem, one of these two lines, or both, provokes instacrash with MZ after starting game.

Most likely Spriteset_Base is the culrpit as it isn't used anywhere else of the scripr, while Spriteset_Map is.

Edit4.
I managed to fix it with nothing commented. Now I need to check if it works as expected, but no crashing is already a big thing.
There have been a chance on how Spriteset_Map.prototype.initialize = function() works.

On MV it was required:
Spriteset_Map.prototype.initialize = function() { Spriteset_Base.prototype.initialize.call(this); };

However, on MZ, it is required:
Spriteset_Map.prototype.initialize = function() { Spriteset_Base.prototype.initialize.call(this); this._balloonSprites = []; };

Any plugin that used the MV version will fail to work due to the lack of that extra line there that the new core requires.

I can just add the line it manually for my project, but it would be great is Fossil added it when a plugin use this and lacks the line as to improve general compatibility, and not everyone dares to touch the plugin files. There is no default launch errors even without using Fossil (I guess because the plugin requires updating MV Pixi to v5 and MZ used v5 by default).

Now I need try if it works properly, not only not crashes

Edit5: Well, as expected, when I try to put animations it doesn't work.

Although most likely it is me doing something wrong because I get the same error on MV.

There's something weird about what it's doing, since both MZ and MV crash for me because it's expecting
Code:
var _debugWindow=require('nw.gui').Window.get().showDevTools();
to store a window reference to _debugWindow, but the showDevTools function doesn't even have a return.

So yeah I'll look at it with a working MV project but otherwise it'd be a bit too far to try to figure out how to make it work in MZ.

alltheyuriz said:
How do I get to that?

F8 or F12
Alemillach

#146 May 11, 2021, 10:16 PM Source
Restart said:
There's something weird about what it's doing, since both MZ and MV crash for me because it's expecting

Code:
var _debugWindow=require('nw.gui').Window.get().showDevTools();

to store a window reference to _debugWindow, but the showDevTools function doesn't even have a return.

So yeah I'll look at it with a working MV project but otherwise it'd be a bit too far to try to figure out how to make it work in MZ.

F8 or F12
I don't get crash unless I try to put an animation, but since I am nor managing to make it work on MV either, I can't look more into it. If the author replies me and reuploads the sample project, it will be easier.

The error you are getting is because you must delete that line, there is comment asking to delete it.

if(Utils.isNwjs()&&Utils.isOptionValid('test')){var _debugWindow=require('nw.gui').Window.get().showDevTools();console.log('_debugWindow: ',_debugWindow);_debugWindow.moveTo(0,0);_debugWindow.height=800;_debugWindow.width=1100;window.focus();}; // delete me, show debug console

This is the debug line I mentioned on my first post about this topic. If you delete this, and add the line missing I mention on my previous post, it already not crashes just existing. It still does when trying to put animations, although as said, that is perfeclty possible me doing it wrong as it fails on MV too.
alltheyuriz

#147 May 11, 2021, 11:34 PM Source

@Restart

Screenshot
xabileug

#148 May 12, 2021, 12:21 PM Source

I still dont have MZ, but does all of tomoaky's plugin in MV can get fossilized? especially the card game?
Restart

#149 May 12, 2021, 10:40 PM Source

xabileug said:
I still dont have MZ, but does all of tomoaky's plugin in MV can get fossilized? especially the card game?
I've looked at the card game before, and IIRC I could get it to a point where it doesn't crash, but a lot of stuff is pretty tied to the old-style animations so it looks quite ugly.

alltheyuriz said:
@Restart

Screenshot
View attachment 189037

It looks like you might be renaming plugins. Don't rename plugins; the only clue fossil has to what is attached is the plugin name, and if it isn't identical (including capitalization), then it won't enable compatibility fixes for that plugin.

Also, please click on the underlined Fossil_Pre and fossil_post on the right hand side and screenshot what shows up
Jrrkein

#150 May 13, 2021, 12:23 PM Source

I decide to do the ordering of the plugins, but this one is whacked.

The bar shouldn't be in the category window details.
Restart

#151 May 13, 2021, 11:59 PM Source

That ought to be eliminated when the window refreshes
Jrrkein said:
I decide to do the ordering of the plugins, but this one is whacked.
View attachment 189164

The bar shouldn't be in the category window details.
please show me the plugin list and make sure you are on the latest version; there's a function in Fossil_Post that erases stray gauges whenever the achievement window runs an updateItem.
Jrrkein

#152 May 14, 2021, 12:17 AM Source

Whoops! using old version one.. It fixed now. Kinda afraid to test with VS itemcore
Restart

#153 May 14, 2021, 12:43 AM Source

Jrrkein said:
Whoops! using old version one.. It fixed now. Kinda afraid to test with VS itemcore
Glad it's working :)

Cleaning up stray gauges is necessary since my custom gauge persists without needing to be redrawn continuously; this is useful in some cases and not useful in others, I'm considering whether I need to change the default behavior.
Jrrkein

#154 May 14, 2021, 01:08 AM Source

Kinda afraid to see if it acting whacked again if I use item core.
Restart

#155 May 15, 2021, 08:26 AM Source

Rose Guardian said:
I don't mean to complain but I cannot get this to work with Mog Hunter's Liner Motion battle system it just keeps giving me this error. What I am doing wrong?

View attachment 188795
Hey just wanted to say I'm still working on LMBS, it seems to be mostly working now, except for the battlebacks (which aren't applied at the right location or scale, look hideous and ruin the experience entirely).

I might see if there's a free existing MZ-native plugin for scrolling/tiled/otherwise custom battlebacks that I can link with it instead, if anyone has suggestions I'm willing to try.
alltheyuriz

#156 May 15, 2021, 06:10 PM Source

@Restart
It seems to be the @ 2021 git hub inc lines

here are the images

Also i didn't change the names these are how they came out of the zip file
Restart

#157 May 15, 2021, 09:42 PM Source

I have no idea how that's happening - it looks like the page was copy-pasted including the header at the bottom

What you need to do is click on the plugin in the list

and click on the raw button

then download it

That is how you get a file off of github.
alltheyuriz

#158 May 16, 2021, 12:41 PM Source

@Restart it worked im just a dumb who doesn't know how to work git
Jrrkein

#159 May 17, 2021, 03:43 AM Source

Vlue isn't working properly for me.
Opening quest log -> Working
Quest track is visible
When viewing info about a quest, results in this error

error
Only one argument and not a rectangle. Could be help window inheriting form something that isn't updating, or it could just be RMMV behavior (it takes one number indicating how many lines of text there are)
rmmz_managers.js:2030 TypeError: Cannot read property 'name' of undefined
at Window_SceneDetail.refresh (questsystem.js:814)
at Window_SceneDetail.quest (questsystem.js:731)
at Scene_Quests.update (questsystem.js:582)
at Function.SceneManager.updateScene (rmmz_managers.js:2097)
at Function.SceneManager.updateMain (rmmz_managers.js:2057)
at Function.SceneManager.update (rmmz_managers.js:1938)
at Function.Graphics._onTick (rmmz_core.js:800)
at TickerListener.emit (pixi.js:9474)
at Ticker.update (pixi.js:9928)
at Ticker._tick (pixi.js:9679)

quest askturnin/askaccept resulted same error, other command still function expect that
Restart

#160 May 17, 2021, 08:27 AM Source

Like Minigames?

Great!
Because have I got some fabulous prizes for you!

First off, @mjshi's quicktime events, match card lottery, and 5-way RPS game.
mjshi's ChainCommand Quicktime Events
mjshi's MatchCardLottery
mjshi's Wuxing Minigame

The card collection framework @SkottyTV made
STV_MonsterCards

And finally, Galv's roulette wheel of death
GALV_PrizeWheel

And let me tell you, these games are rigged - no matter what cards you draw, you'll end up getting

200 Fossilized Plugins!
Jrrkein

#161 May 17, 2021, 03:25 PM Source

Vlue seems to be not working all the time
Restart

#162 May 17, 2021, 07:50 PM Source

Jrrkein said:
Vlue isn't working properly for me.
Opening quest log -> Working
Quest track is visible
When viewing info about a quest, results in this error

error
Only one argument and not a rectangle. Could be help window inheriting form something that isn't updating, or it could just be RMMV behavior (it takes one number indicating how many lines of text there are)
rmmz_managers.js:2030 TypeError: Cannot read property 'name' of undefined
at Window_SceneDetail.refresh (questsystem.js:814)
at Window_SceneDetail.quest (questsystem.js:731)
at Scene_Quests.update (questsystem.js:582)
at Function.SceneManager.updateScene (rmmz_managers.js:2097)
at Function.SceneManager.updateMain (rmmz_managers.js:2057)
at Function.SceneManager.update (rmmz_managers.js:1938)
at Function.Graphics._onTick (rmmz_core.js:800)
at TickerListener.emit (pixi.js:9474)
at Ticker.update (pixi.js:9928)
at Ticker._tick (pixi.js:9679)

quest askturnin/askaccept resulted same error, other command still function expect that
Seems like a problem with your quest.txt, I'm guessing you set the wrong quest reward.
Jrrkein

#163 May 17, 2021, 08:30 PM Source

Ah heck.. I forgot that and realized made an error