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

Jrrkein

#124 May 9, 2021, 02:03 AM Source

I changed everything you said about x, y and weight, but got this error
rmmz_managers.js:2030 ReferenceError: x is not defined
at Window_AchievementTitle.initialize (HO_AchievementSystem.js:2675)
at new Window_AchievementTitle (HO_AchievementSystem.js:2668)
at Scene_Achievements.createWindows (HO_AchievementSystem.js:2627)
at Scene_Achievements.create (HO_AchievementSystem.js:2616)
at Function.SceneManager.changeScene (rmmz_managers.js:2084)
at Function.SceneManager.updateMain (rmmz_managers.js:2056)
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)

Restart

#125 May 9, 2021, 02:27 AM Source

did you change the function to this?

Code:

Window_AchievementTitle.prototype.initialize = function() {
	var x = Math.round(eval(Horsti.AS.titleX));
	var y = Math.round(eval(Horsti.AS.titleY));
	var rectA= new Rectangle(x, y, this.windowWidth(), this.windowHeight())
	Window_Base.prototype.initialize.call(this, rectA);
	this._openness = 255;
	this.refresh();
	this.open();
};

because if so I have no clue why it thinks x is undefined.

Jrrkein

#126 May 9, 2021, 02:53 AM Source

Whoops! I guess I didn't and just overwrite everything different and what did I do wrong this time.

rmmz_managers.js:2030 TypeError: Cannot convert undefined or null to object
at Function.values (<anonymous>)
at Window_AchievementData.Window_Selectable.<computed>.<computed> [as hideNewLabelSprites] (VisuMZ_1_ItemsEquipsCore.js:2672)
at Window_AchievementData.Window_Selectable.<computed>.<computed> [as refresh] (VisuMZ_1_ItemsEquipsCore.js:2672)
at Window_AchievementData.initialize (HO_AchievementSystem.js:2887)
at new Window_AchievementData (HO_AchievementSystem.js:2875)
at Scene_Achievements.createWindows (HO_AchievementSystem.js:2629)
at Scene_Achievements.create (HO_AchievementSystem.js:2616)
at Function.SceneManager.changeScene (rmmz_managers.js:2084)
at Function.SceneManager.updateMain (rmmz_managers.js:2056)
at Function.SceneManager.update (rmmz_managers.js:1938)

Maybe you can tweak it for me because I'm not much of a coder
Restart

#127 May 9, 2021, 04:44 AM Source

Well seems like VisuMZ_1_ItemsEquipsCore just doesn't like it. Sorry, but nothing I can do there.
Jrrkein

#128 May 9, 2021, 04:54 AM Source

oh darn
Restart

#129 May 9, 2021, 07:51 AM Source

Well, I am happy to say I'm about 95% sure that word wrap is finally working properly in message core with fast text

If someone would be willing to stress test it I'd appreciate it.
Jrrkein

#130 May 9, 2021, 11:23 AM Source

I would give it a try with loads of lorem ipisum
Rose Guardian

#131 May 9, 2021, 02:57 PM Source

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?
Restart

#132 May 9, 2021, 06:30 PM Source

I haven't tried that one yet, I'll take a look at his project.

EDIT: I just put up
FossilMZ/fossil-MV-MZ which might help with MZ/MV window cross-compatibility. No promises, it's a rough draft at this point.
TimothyMV

#133 May 10, 2021, 07:13 PM Source

Wait a minute does that mean that there's a possibility that my database will be wiped?!?!
Also, now I feel like I have to make my own bestiary by google docs.
hyacinthh

#134 May 10, 2021, 08:31 PM Source

Restart said:
Hello,

I've had this reported before. Are you using a plugin that does word wrap (MZ or MV)? If so, turn off wordwrap before reaching the shakeytext, and enable it afterwards. I still haven't worked out the kinks for getting wordwrap to work in general, and sometimes it has glitchy interactions with other plugins.

Hi! So sorry for the late reply!

Unfortunately even with all my other plugins turned off, the shaking text still likes to overlap onto the other text boxes. I thought it might be something to do with the YEP message core, but word wrapping is off :(

Here's a screenshot of the plugins and the arrangement, maybe I'm doing something wrong there?
Restart

#135 May 10, 2021, 08:32 PM Source

Reid looks in the mirror!

Horrified by his bad haircut, he drinks to forget!

Perhaps a little too much.

So yeah, I got Gimmer's mirror effect and drunk effect plugins working.

They're a couple of fun little features to add some visual flair. You'll need Gimmer Core to make them work.

TimothyMV said:
Wait a minute does that mean that there's a possibility that my database will be wiped?!?!
No, sorry, I'll clear that up.

Basically the issue is that MZ window functions take in one argument for size, and MV window functions use four of them.

So when MZ code does stuff with windows, it will often lose the other three when handing things between functions (because it doesn't expect the other 3 to exist).

What beastbook are you trying to use? STV_Beastbook should be working unless some update I did accidentally broke it.

EDIT: tested, it still works. What's your plugin order?

hyacinthh said:
Hi! So sorry for the late reply!

Unfortunately even with all my other plugins turned off, the shaking text still likes to overlap onto the other text boxes. I thought it might be something to do with the YEP message core, but word wrapping is off :(

Here's a screenshot of the plugins and the arrangement, maybe I'm doing something wrong there?

Put post_messagecore right after messagecore (and before shakeytext). Grab the latest version as well, it's improved.

Fossil_Pre should go ALL the way at the start, if you are using messagecore the order should be

-Fossil_Pre
MV plugins
-Fossil_Pre_MessageCore
MessageCore + YEP_X messagecore exentions
-Fossil_Post_MessageCore
More MV plugins
-Fossil_Post
MZ plugins
-WindowFixer (optional, only if you have window size issues due to mixing plugins)

Shakeytext works for me both with and without message core (or word wrap) now.
alltheyuriz

#136 May 10, 2021, 11:49 PM Source

I keep getting a syntax error when i try to play the game
Restart

#137 May 11, 2021, 02:19 AM Source

alltheyuriz said:
I keep getting a syntax error when i try to play the game
you're going to have to be more specific
Alemillach

#138 May 11, 2021, 05:13 AM Source

I was trying to make this plugin, PIXI SpriteSheetsAnimations, work using Fossil, but the game doesn't go past new game. I tried on a blank project with just Fossil Pre, PIXI SpriteSheetsAnimations and Fossil Post, but it doesn't work.

There is a debug line in the js with a comment to delete which gives an error even before the mainscreen, but after deleting it, there is the mentioned error.

Error is:

TypeError
this._balloonSprites is not iterable
There is an option that say that without animations may give problems if on, so I turned it off from the beggining, so it isn't the problem.

Tried without Fossil and it is the exact same error.

I haven't found anything equivalent for MZ. Dragonbones is similar reagrdina usin animations as sprites, but it doesn't allow frame animations like this plugin, only those made with dragonbones, and I am rendering my animations, so Dragonbones won't work at all for my project.

I guess it may be hard to make it work, but regarding MV and MZ environments I am still a newbie, so maybe it isn't that much of an issue.
Restart

#139 May 11, 2021, 05:50 AM Source

a3xgf said:
I was trying to make this plugin, PIXI SpriteSheetsAnimations, work using Fossil, but the game doesn't go past new game. I tried on a blank project with just Fossil Pre, PIXI SpriteSheetsAnimations and Fossil Post, but it doesn't work.

There is a debug line in the js with a comment to delete which gives an error even before the mainscreen, but after deleting it, there is the mentioned error.

Error is:

There is an option that say that without animations may give problems if on, so I turned it off from the beggining, so it isn't the problem.

Tried without Fossil and it is the exact same error.

I haven't found anything equivalent for MZ. Dragonbones is similar reagrdina usin animations as sprites, but it doesn't allow frame animations like this plugin, only those made with dragonbones, and I am rendering my animations, so Dragonbones won't work at all for my project.

I guess it may be hard to make it work, but regarding MV and MZ environments I am still a newbie, so maybe it isn't that much of an issue.

I'll take a look but it probably will be too difficult. Do you have a demo project I can work with? The link in the OP is dead.
Alemillach

#140 May 11, 2021, 02:56 PM Source

Restart said:
I'll take a look but it probably will be too difficult. Do you have a demo project I can work with? The link in the OP is dead.
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.

Uncaught TypeError: Cannot read property 'texture' of undefined
Although most likely it is me doing something wrong because I get the same error on MV.
alltheyuriz

#141 May 11, 2021, 06:47 PM Source

Restart said:
you're going to have to be more specific
I'll get a screen shot when I get home
@Restart

Set up

Error
hyacinthh

#142 May 11, 2021, 07:53 PM Source

Restart said:
Put post_messagecore right after messagecore (and before shakeytext). Grab the latest version as well, it's improved.

Fossil_Pre should go ALL the way at the start, if you are using messagecore the order should be

-Fossil_Pre
MV plugins
-Fossil_Pre_MessageCore
MessageCore + YEP_X messagecore exentions
-Fossil_Post_MessageCore
More MV plugins
-Fossil_Post
MZ plugins
-WindowFixer (optional, only if you have window size issues due to mixing plugins)
oh my gosh, thank you so much!! works perfectly now!! :D
Restart

#143 May 11, 2021, 09:15 PM Source

alltheyuriz said:
I'll get a screen shot when I get home
@Restart

Set up
View attachment 189030

Error
View attachment 189031

can you show me the console log and stacktrace?