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

Restart

#81 May 4, 2021, 04:33 AM Source
Have added 30 or so more plugins.

One of the fun things about doing this is people asking about plugins that I wasn't aware of. KMS is a Japanese plugin maker, and he has a cool water map effect, a swirly random encounter, and a minimap, all of which now work in MZ too :)
[embedded media]
LyraVultur

#82 May 4, 2021, 04:50 AM Source

Oh, wow! A working minimap plugin for MZ will be very handy!
weso12

#83 May 4, 2021, 01:07 PM Source

Just FYI I was trying YEP_X_SelectionControl(with the plugins YEP_BattleEngineCore and YEP_TargetCore since Yanfly lists those plugins as mandatory and adding "
<Single or Multiple Select>" to any skill, seems to have this effect

console window is that's helpful

Also from what i can tell skills that are set to target Actors by default, won't no matter what be able to target both with selection control (ones that target Enemies are able to target Actors no problems)
Restart

#84 May 4, 2021, 04:18 PM Source

weso12 said:
Just FYI I was trying YEP_X_SelectionControl(with the plugins YEP_BattleEngineCore and YEP_TargetCore since Yanfly lists those plugins as mandatory and adding "
<Single or Multiple Select>" to any skill, seems to have this effect

View attachment 188323

console window is that's helpful

View attachment 188324

Also from what i can tell skills that are set to target Actors by default, won't no matter what be able to target both with selection control (ones that target Enemies are able to target Actors no problems)
Can you show me the skill? I've tried this guy

And it works as expected (giving you the option to heal either one or all enemies - or if you change the 'scope' to allies, one or all allies).

Do you have any other plugins set up?
(Oh, and did you grab the latest version off github?)
weso12

#85 May 4, 2021, 04:31 PM Source

Restart said:
Can you show me the skill? I've tried this guy
View attachment 188335
And it works as expected (giving you the option to heal either one or all enemies - or if you change the 'scope' to allies, one or all allies).

Do you have any other plugins set up?
(Oh, and did you grab the latest version off github?)
I just got the updated version off github and it worked like a charm, sorry to bug you, I feel like an idiot now.
Restart

#86 May 5, 2021, 08:31 AM Source

weso12 said:
I just got the updated version off github and it worked like a charm, sorry to bug you, I feel like an idiot now.
No problem, you shouldn't stress about it.

Speaking of not stressing about things, I've updated the plugin list again with about a dozen more, and have added a compatibility patch for Olivia's Anti-Player Stress, which is a very useful little plugin for tweaking default settings, and removing annoyances, and is probably familiar to most people on the forums.

Jay_FocusedSoundEffects is also working, which is nice. I love directional sound, and this is a really easy way to add it to your project.

Aside from that, I've decided the list in the OP should also include MV plugins that are reported to work in MZ both with Fossil and without it. They will be tagged with a little diesis symbol (‡). There isn't really a comprehensive list of MV plugins that can work in MZ, and I think this makes it more useful for people who want to know 'can I use this MV thing I found in MZ?'

If the plugin is labelled as being MZ compatible somewhere, obviously it won't be included in the OP (because anyone looking at the plugin will know what it works with), and the list in Fossil_Pre's introductory comments section won't include any ‡ plugins.
hyacinthh

#87 May 5, 2021, 03:46 PM Source

hello!! just joined just to ask this question haha. I use the fossil plugin with the SRD shake text plugin, but all the shaking text appears to layer over all the following textboxes. This may be a problem with the shaking text plugin itself and not the fossil plugin, but I have no way of checking as I don't have rpg maker mv to do a test and rpgmaker mz won't run the plugin without fossil. Here's how it looks when the previous shaking text stacks on top of another.

It'll continue to stack and layer for all textboxes afterwards too. sorry if this is a little too much trouble!!
Onox

#88 May 6, 2021, 02:17 PM Source

I don't know if this is my fault or bad interaction with other plugins but the "SRD_SkillExtender" seems to be having some trouble.
The "extender" function works but the name of the extended skills is not displayed ...

Edit: I tried with just the fossil and skill extender plugins in an empty project and it doesn't work either
.
Restart

#89 May 6, 2021, 05:21 PM Source

hyacinthh said:
hello!! just joined just to ask this question haha. I use the fossil plugin with the SRD shake text plugin, but all the shaking text appears to layer over all the following textboxes. This may be a problem with the shaking text plugin itself and not the fossil plugin, but I have no way of checking as I don't have rpg maker mv to do a test and rpgmaker mz won't run the plugin without fossil. Here's how it looks when the previous shaking text stacks on top of another.
View attachment 188409

It'll continue to stack and layer for all textboxes afterwards too. sorry if this is a little too much trouble!!
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.

Onox said:
I don't know if this is my fault or bad interaction with other plugins but the "SRD_SkillExtender" seems to be having some trouble.
The "extender" function works but the name of the extended skills is not displayed ...

Edit: I tried with just the fossil and skill extender plugins in an empty project and it doesn't work either
.
I'll take a look at it. Plugins that make a custom window usually require one or two pokes so everything shows up in right size.
Restart

#90 May 6, 2021, 08:02 PM Source

Onox said:
I don't know if this is my fault or bad interaction with other plugins but the "SRD_SkillExtender" seems to be having some trouble.
The "extender" function works but the name of the extended skills is not displayed ...

Edit: I tried with just the fossil and skill extender plugins in an empty project and it doesn't work either
.
Try the latest version from github.

Also, I believe I have just gotten yanfly's ATB, CTB, and STB to generally work.

However, I am not super familiar with these systems, and I would appreciate someone who has already used them in a game to check out whether or not they're fully functional before I make it official.

I know CTB's turn order display isn't working yet, I'm sure there are other bugs.
Onox

#91 May 6, 2021, 08:18 PM Source

Restart said:
Try the latest version from github.
It work perfectly !
Restart

#92 May 6, 2021, 11:25 PM Source

Onox said:
It work perfectly !
Great, glad to hear it!

I saw that Moghunter adapted his ATB gauge plugin to track characters in the MZ ATB system. In the spirit of full interoperability, I hooked it into the Yanfly ATB. Fossil will detect if you have both mog's gauge and ATB set up, and do the needful.

Note that only the MZ version of MOG_ATB_Gauge will work, since it's designed to be more flexible. Since the features are identical that shouldn't be an issue (and fossil will yell at you in the console if you grabbed the wrong file)

This also works with Yanfly CTB.
MirageV

#93 May 7, 2021, 04:08 AM Source

It was curious about this, so I tried it with Moghunter's MV Picture Gallery and it actually functions 100% correctly.

...Well, technically. The windows appear on screen like this, which made me snort.

Screenshot

And this is how the same setup appears in MV at the same resolution.

Screenshot

I wonder if it's possible to get the windows sorted out in MZ? I'd super appreciate the effort. :rswt
Restart

#94 May 7, 2021, 04:37 AM Source

MirageV said:
It was curious about this, so I tried it with Moghunter's MV Picture Gallery and it actually functions 100% correctly.

...Well, technically. The windows appear on screen like this, which made me snort.

Screenshot

And this is how the same setup appears in MV at the same resolution.

Screenshot

I wonder if it's possible to get the windows sorted out in MZ? I'd super appreciate the effort. :rswt
I tried it in my test project and it looks like this

I tried resizing the window but it still looks like this

What are your plugin settings? It seems to be working okay for me.

EDIT: Okay, I think I figured it out. It scales based off of the 'UI Area' setting in your System2, not based on 'Screen Width'. I guess that makes sense as a default since you don't want pictures to be onscreen that you can't click on. Try changing that and tell me if it works.
Jrrkein

#95 May 7, 2021, 06:00 PM Source

I'm using this plugin for my project.
MV - HO Achievement System
Seems the UI won't fit with system2 setting as well kinda tight spot not like in this one

This one is clearly in MV, which fits perfectly in MZ it might be tight squeeze
Restart

#96 May 7, 2021, 07:21 PM Source

I'm sorry, what's the issue?

This seems to be resizing fine in MZ as well
Jrrkein

#97 May 8, 2021, 12:22 AM Source

I think the issue doesn't seem fit well with screen resolution on system2
Restart

#98 May 8, 2021, 01:25 AM Source

Seems like either a conflict with another plugin, or your plugin parameters are set wrong.

I'm using the params from the demo project, which determine how big the windows are.
Jrrkein

#99 May 8, 2021, 01:36 AM Source

All the other plugins are Visuasetella, two gavs and fossil. Also I didn't tamper anything with the setting
Restart

#100 May 8, 2021, 02:07 AM Source

can you show me your plugin params? It's possible the demo project is set up differently

alternative you can try turning off the other plugins, it's impossible to predict if VS will break things.

Anyway I pushed a new Fossil_Post tweak that will fix the gauges on the achievement window so they appear and disappear properly, tell me if THAT works anyway.