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

Restart

#102 May 8, 2021, 02:19 AM Source

Okay, let's try turning off the other plugins, it's impossible to predict if VS will break things. Maybe we can narrow down the issue.

Also, I pushed a new Fossil tweak to the github that will fix the gauges on the achievement window so they appear and disappear properly, so try pulling the latest down.
Jrrkein

#103 May 8, 2021, 02:29 AM Source

So far it fits if I turn off anything then slowly turning on expect fossil and the achievement of course

Other than core and main menu core, the other core and higher tier than 1 would make it tight squeeze as soon I turn them on
Restart

#104 May 8, 2021, 02:30 AM Source

If you want a workaround, you can try hardcoding the numbers in the plugin parameters. It might work if you just say it's 300 wide (or whatever you want it to be) instead of having it autocalculate.
Jrrkein

#105 May 8, 2021, 02:35 AM Source

I think no matter I tweak it, the box kinda tight squeeze.
Restart

#106 May 8, 2021, 02:51 AM Source

try replacing every instance of Graphics.boxWidth
with 952 in the plugin params
Jrrkein

#107 May 8, 2021, 03:23 AM Source

Still tight squeeze

Restart

#108 May 8, 2021, 03:56 AM Source

Including all the ones where it's being divided by something? Darn, I guess VS is doing something weird.

I'd suggest putting a breakpoint in this function in achievments

Code:

Window_AchievementData.prototype.initialize = function() {
	var x = Math.round(eval(Horsti.AS.dataX));
	var y = Math.round(eval(Horsti.AS.dataY));
	Window_Selectable.prototype.initialize.call(this, x, y, this.windowWidth(), this.windowHeight());
	this._openness = 255;
	this._item = undefined;
	this._lastItem = undefined;
	this._currentHeight = 0;
	this.resetFontSettings();
	this.calcAllTextHeight();
	this.open();
};

and seeing if you can figure out what is going on with this.windowWidth(), and then if that is the correct number, step into the window_selectable initialize and follow it all the way down.

Jrrkein

#109 May 8, 2021, 04:05 AM Source

The data window seems tight squeezing. So what should I do next I opened the js on the notepad
Restart

#110 May 8, 2021, 04:15 AM Source

I'd suggest you use the console instead. You want to see what happens when it's actively executing
Restart

#112 May 8, 2021, 04:25 AM Source
can you show my your plugin order? I'm guessing VS is jumping into the initialization midway and using .call(this, rect) instead of passing through the entire arguments, so it's stealing the data.

EDIT: screw it, take this line:
Code:
Window_Selectable.prototype.initialize.call(this, x, y, this.windowWidth(), this.windowHeight());
change to these two lines
Code:
var rectA= new Rectangle(x,y,this.windowWidth(),this.windowHeight()) Window_Selectable.prototype.initialize.call(this, rectA);
Jrrkein

#113 May 8, 2021, 04:40 AM Source

Pre fossil is at the very top and post one is below weakness display

Even changing the codes still tight squeeze
Restart

#114 May 8, 2021, 05:01 AM Source

Did you replace every occurrence of Window_Selectable.prototype.initialize.call? What does your console look like?

Fossil_Post is supposed to be after your MV plugins (and if possible before all MZ plugins - mixing them can be unpredictable as you can see).

You can also try the backwards order of doing MZ - > Fossil_Pre -> MV ->Fossil_Post but I can't guarantee results on that.
Restart

#116 May 8, 2021, 05:43 AM Source

okay, not all of them have been updated to pass a rect

did you change
Window_AchievementTitle.prototype.initialize
Window_AchievementList.prototype.initialize
Window_AchievementData.prototype.initialize
and
Window_AchievementTitle.prototype.initialize
Jrrkein

#117 May 8, 2021, 07:52 AM Source

Haven't changed it yet
Tuomo L

#118 May 8, 2021, 08:18 AM Source

Does this work with SRD's Data Compressor?

https://sumrndm.site/data-compressor/
Alemillach

#119 May 8, 2021, 01:50 PM Source

@Jrrkein There is a native MZ plugin for achivements from Caspar Gaming. Maybe it will be more compatible with your other plugins.

Achivement MZ Plugin on Caspar Gaming's Website.
Jrrkein

#120 May 8, 2021, 07:13 PM Source

a3xgf said:
@Jrrkein There is a native MZ plugin for achivements from Caspar Gaming. Maybe it will be more compatible with your other plugins.

Achivement MZ Plugin on Caspar Gaming's Website.
I like using casper too, but it's little more than offers more.
Restart

#121 May 8, 2021, 08:20 PM Source

Jrrkein said:
Haven't changed it yet
okay well tell me when you do and we'll see if it works or not. I'm not really focusing on compatibility between different plugins atm.
Jrrkein

#122 May 8, 2021, 08:40 PM Source

Do I have to change every line with the given code?
Restart

#123 May 9, 2021, 12:39 AM Source

Jrrkein said:
Do I have to change every line with the given code?
every line in that plugin yes. Just convert the x,y,width,height into a rectangle as shown