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

Oddball

#284 Sep 15, 2021, 01:28 AM Source

Will this effect MZ plugins?
Icenick

#285 Sep 18, 2021, 03:16 PM Source

Error
Uncaught TypeError: this._clearUpperCanvas is not a function

Trying to use YF_Core, YF_BattleEngine, and YF_CTB

What did I do wrong?
hsumi

#286 Sep 18, 2021, 04:08 PM Source

Restart said:
I know I already got one minimap plugin to work, but now we have the one made by @SilverDash available in MZ as well.

It has an optional fog of war, and can be toggled on and off (or given as an item). I have most of the plugins in his master demo working, but haven't figured out the itemlog. Still, if you want the cool window-slide-in effect that he put in his core engine (you can see one sliding in from offscreen at the top left!), the event randomization, or the dash stamina system, you've got those as options in MZ now.
I know this is old, but I'm having a problem where loading SE_Minimap causes an 'Undefined' error when I test the project. I have all of the associated requirements enabled (SE_Core, SE_Keys, Mapshot), and the game loads fine with just these enabled, but enabling the minimap plugin just results in an error when hitting the test play button.
Krystek_My

#287 Sep 18, 2021, 05:21 PM Source

Icenick said:
Error
Uncaught TypeError: this._clearUpperCanvas is not a function

Trying to use YF_Core, YF_BattleEngine, and YF_CTB

What did I do wrong?
YEP_EngineCore is not supported.
Not every plugin can be, some like this one are proabbly unportable
evertonera

#288 Sep 19, 2021, 05:22 AM Source

Amazing plugin. I have been trying it out, and most of my MV plugins.
Except I get a really strange bug: my battler sprites won't appear in combat. Anyone else getting this weird bug? It's simple as that: I activate FOSSIL plugin, none of the battlers show up on the screen. Deactivating it fixes this issue.
Icenick

#289 Sep 20, 2021, 12:22 PM Source

Krystek_My said:
YEP_EngineCore is not supported.
Not every plugin can be, some like this one are proabbly unportable
Yeah but CTB says its supported and so is battle engine. Do you run it without the core?
fizzly

#290 Sep 20, 2021, 12:29 PM Source

busbuzz said:
I got referenceerror require not defined with this plugin as i was trying to deploy to web. I looked for plugins that had the function require in it, and found fossil, then removed fossil and the game worked, :(
Have the same problem, looks like it's incompatible with web browsers/android deplyment. Sadly.
Beregon

#291 Sep 22, 2021, 04:20 AM Source

Great plugin! Any chance it will support web deployment in the future?
Rex Tenebris

#292 Sep 23, 2021, 09:19 PM Source

Hello @Restart YEP_X_MapQuestWindow is showing like this, could you fix it please? :(

Quest objectives doesn't show at all, neither the squares. It should look like this (from MV):

Also, by some reason only due using YEP_QuestJournal this window is always opened on start:
Krystek_My

#293 Sep 24, 2021, 12:56 PM Source

Icenick said:
Yeah but CTB says its supported and so is battle engine. Do you run it without the core?
Yes. The Core engine is very complex plugin and would require going into its code.
Use Battle Core and CTB without it.
Icenick

#294 Sep 24, 2021, 02:34 PM Source

Krystek_My said:
Yes. The Core engine is very complex plugin and would require going into its code.
Use Battle Core and CTB without it.
I tried it and it doesn't work in any event.
DarkSearinox92

#295 Sep 28, 2021, 03:08 PM Source

I don't understand if the project continues to be supported or not ... I don't see any new posts about updates, just an endless list of people reporting problems.

Last update of the main post is Jun 16, 2021...
Halcyon Days

#296 Sep 28, 2021, 03:53 PM Source

I'm sorry if it's a dumb question, but I tried to get FOSSIL and downloaded the raw version of the plugin, but how I can add it in my project?
FiercestPixel

#297 Oct 4, 2021, 04:44 AM Source

Has anyone had any luck with porting ChronoEngine? I've been getting this error...
myarichuk

#298 Oct 12, 2021, 03:41 PM Source

Did some digging regarding Yanfly Core Engine compatibility with FOSSIL, perhaps the following will be useful to someone.

It seems like there is an issue with how Core Engine handles and scales battlebacks - FOSSIL has that is supposed to emulate RMMV way of drawing battlebacks because it has changed in RMMZ.

The code line highlighted in the link throws (https://github.com/FossilMZ/fossil-MV-MZ/blob/main/FOSSIL.js#L2808) because Sprite_Battleback.prototype.battleback1Name is undefined for some reason (and the code cannot call "apply" method of undefined object)
Unfortunately, I am too much of a noob in Javascript and too new to RpgMaker to figure out the reason so far.

I wonder what was the version of Core Scripts that the current version of FOSSIL was tested with, because it seems like something has changed in the Core Scripts and broke FOSSIL.

Note : In the test project I used only FOSSIL and Yanfly Core Engine plugins and Core scripts v1.3.3
SirCumferance

#299 Oct 13, 2021, 11:06 PM Source

*taps mic
Thanks for this, truly
magnumwhisper

#300 Oct 15, 2021, 03:40 AM Source

Has anyone had success with deploying their game to mobile/web well using the Fossil plugin? For whatever reason my game does not work when I deploy it for mobile/web when using the fossil plugin.

Thanks in advance!
DarkSearinox92

#301 Oct 19, 2021, 09:50 AM Source

@Restart Is it dead the project?

Guys, what about create a big project just like Community Light? I think that this project deserve better attention and more collaboration.
myarichuk

#302 Oct 19, 2021, 11:35 AM Source

I agree, FOSSIL is an excellent project, MV has accumulated TONS of useful plugins and it would be a shame to lose them just because the RM core scripts were refactored and updated.

Also, I think it is too early to judge this project dead, the last meaningful commit to the project was 3 month ago.
If it is indeed dead, the community can indeed pick this up, FOSSIL license permits it (https://tldrlegal.com/license/creative-commons-attribution-4.0-international-(cc-by-4))

I for one would happily participate in such an effort if it takes place, though unfortunately I am too much of a noob in RM core scripts to even think of leading such effort.

That said, guys, do you think it is possible to get from Kadokawa an official list of changes (refactorings) between RMMV and RMMZ core scripts? This would definitely make life easier for whoever maintains FOSSIL project
DarkSearinox92

#303 Oct 19, 2021, 11:56 AM Source

myarichuk said:
I agree, FOSSIL is an excellent project, MV has accumulated TONS of useful plugins and it would be a shame to lose them just because the RM core scripts were refactored and updated.

Also, I think it is too early to judge this project dead, the last meaningful commit to the project was 3 month ago.
If it is indeed dead, the community can indeed pick this up, FOSSIL license permits it (https://tldrlegal.com/license/creative-commons-attribution-4.0-international-(cc-by-4))

I for one would happily participate in such an effort if it takes place, though unfortunately I am too much of a noob in RM core scripts to even think of leading such effort.

That said, guys, do you think it is possible to get from Kadokawa an official list of changes (refactorings) between RMMV and RMMZ core scripts? This would definitely make life easier for whoever maintains FOSSIL project

Well, 4 month without any news it's a bit worrying xD There are only problem posts and, although Restart said that this started as an open project, no one skilled is really participating in its improvement. It's a shame....