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

FireHawk ADK is not defined

A topic by Crimson_Zero created 22 days ago Views: 96 Replies: 7
Viewing posts 1 to 4
(3 edits)

Hello, I just picked up the RPG Maker Cook Tool Deluxe and am having issues getting it to work with RPG Maker MZ 1.9.1.  I feel I must be missing something obvious.

Putting FSDK_CookToolAddOn.js at the top of the plugin list puts out the error: FireHawk ADK is not defined.   This also happens after creating a test build.

Putting FDSK_AdvSaveHandler on gives a 'cannot read property 'filename' of undefined.  Regardless of which 3 preferred locations I pick in the plugin settings.

While the fullscreen plugin causes no errors, it also doesn't seem to do anything regardless of what I set the plugin settings to.

If I create a build with no plugins, the test build will run.  But otherwise most plugins will cause it to be stuck in an endless loop.

Hello, Crimzon_Zero!

  • For the AdvSaveHandler, there was a bug where it tried to find the main executable's location but throw that error instead. I'm uploading a patch as we speak.
  • For FSDK_CookToolAddOn, could you please provide me with the output of the dev console, so I can see where is it triggered?
  • As for the fullscreen plugin, do you use something like Visustella Options Core? If you do, there might be a conflict.

In regards to plugins not working after building: the most likely culprit is that some plugins are trying to find their config by checking their name (rather than using a hardcoded one). If they use something like document.src, then they try to get their name dynamically.

(1 edit)

Same issue for "FirehawkADK is not defined", here is the screenshot:
Solution:
In CookTool..
The correct line is:
var FirehawkADK = FirehawkADK || {};

And for FullScreenPlus, I had to rename the variable isHandled to isHandled2... maybe another script was using it has a global variable.

Yeah. The isHandheld is decalred by CookToolAddOn, thus causing the error. I've updated that plugin again to fix the error.

(4 edits)

For FSDK_CookToolAddOn, it's as Carotopia showed in the picture above.

I'm not using any Visustella plugins with this project.

I am mainly using the Hendrix Action Combat Plugins, which the plugin author has stated that he's used Cook tools Deluxe with in the past without any issues.  Edit: As long as plugin compression was disabled.  Is that still an option with this version?

 
This is the error I get when enabling most of the plugins I use.  In this specific example it is just DotMoveSystem enabled.

Interestingly, if I disable Halva compression, I get an additional error along with the one below:
Uncaught SyntaxError: Unexpected token '<'   index.html:1

(1 edit)

Digging a bit on the plugins that I could get my hands on, DotMovementSystem is one of (or the only) culprit, as it tries to pull its name dynamically (Source Code Protection has to patch MZ so it can load the bainry files that nwjs can read). It's fixable by changing the line 298:

const DotMoveSystemPluginName = document.currentScript ? decodeURIComponent(document.currentScript.src.match(/^.*\/(.+)\.js$/)[1]) : "DotMoveSystem";

To this:

const DotMoveSystemPluginName = "DotMoveSystem";

Might send a message to the dev of DotMovementSystem to let them know about it.

If you see similar issues with what you saw in that plugin, check if there any plugins that use document.currentScript (or similar) and simply change the line to hardcode the name.

As for Uncaught SyntaxError: Unexpected token '<': I can't say for certain what causes that on MZ. It doesn't crash MZ games (I tested with both barebones and more plugin heavy projects) and there's no crash or stuck in a loop. Most likely, there's a slight error in patching the html file so it can load the binary version of main.js. Other than that, it's a fluke of an error.

EDIT: If you mean the Source Code Protection on your edit: Yes. It's still an option. Since R6, it's enabled by default when the option to encrypt the assets is turned on. So, you'd need to disable that option first.

(4 edits)

Oh wow!

You definitely go above and beyond what I was expecting!  Thanks!

Disabling the source code protection allowed most of the plugins to work with no issues.  There's only one that's making a nuisance (TRP Particles) and I can probably find a replacement for it if I can't get it to work.  Or even just forgo it altogether.

I may do as you suggested and go through the code and see if there's anything like document.currentScript (or similar) in the other plugins so it can be fixed for asset protection as you did with DotMoveSystem at a later date, but for now I'm just happy to have it working!

Regarding, FSDK_CookToolAddOn.  You snuck a new (B)ug into the first line of the plugin file you released today (Version 1.4.3-release.20251023) though it's easy to fix :)

Fixed the typo.