Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

RPG Maker Cook Tool Deluxe

The one stop shop for deploying RPG Maker MV/MZ games · By AceOfAces

[R6.01 U3 & older builds] Some plugins not working after compiling

A topic by Greyface Games created 45 days ago Views: 70 Replies: 2
Viewing posts 1 to 2
(1 edit)

Some strange behaviour that I noticed when I first picked up the CookTool a few months back, but I got distracted by the Linux/SteamOS compatibility issues.

I've noticed that on Windows & Linux, some plugins do not appear to be working. I'm going to add some specific logging for them into the game, but wondered if there was a known compatibility list or something that the cooktool alters that may be impacting these plugins?

So far as I can tell it is impacting 2 plugins, one is my own, but one is this-
https://ct-bolt.itch.io/rmmz-windowex-plugin

I can't yet tell if the plugins aren't running at all, or if they are running but failing.

The one thing both plugins have in common is that they look for images in set folders (system for this one, characters for my one), so it may be that the plugin is running but not reaching the folder and so sticking with the original image. 

Could there be a path/permissions issue, do you think?
Any thoughts or suggestions would be welcome!

(4 edits)

This is a compatibility issue with a feature of the tool, called JavaScript Source Code Protection. This converts the JS files to files that nwjs understands, thus protecting the source code. Since the tool has to patch the engine to load these files, plugins that try to pull their name dynamically don't work. That feature is a dependency for Deep Level Encryption as well, so it can guard the password.

If you don't want either of these, you can disable both of them in the settings (under Asset Preparation). If you do, I cover this here: https://dragonhousehelpcenter.azurewebsites.net/manuals/rmcooktooldx/devguide. On the WindowEx plugin, I see that it tries to pull its name dynamically, so changing the line  $_$.params = getPluginParameters(); to $_$.params = PluginManager.parameters('CTB_WindowExMZ') . As for yours, I can't say for certain. But you can create a test build (the option is found on Project Settings, under the essentials tab). First, remove the --disable-devtools from the package.json file temporarily. Then create the test build. Once that's done, press F12 to open the dev console.

EDIT: Wrote the wrong line fix here. And re-wrote the dev tools instructions.

Perfect- I'll give that a go; I would guess it's the same issue for my plugin too as I followed a similar method.

I'll test and let you know- but really appreciate the efforts and info!