Developer Guidance

Information regarding the compiler

RPG Maker Cook Tool Deluxe uses NW.js' JavaScript Source Protection feature. This feature compiles the code into a binary file that only NW.js understands. By default, the Cook Tool will automatically patch the required files (which will make the game work with binary files).

During compilation, nwjc (NW.js' compiler) will process the JavaScript file using the V8 engine (the built-in interpreter for JS). If the compiler encounters an issue, you will see this error message. The error can been seen in the DevTools as well while building the game.

Breaking Changes

• The binary version of the source code will only run on the same version of NW.js (that was used to compile the code) and Operating System that the game was built.
• Plugins that load JS files will need a re-work on any JS load calls. See this page on how to load compiled JS files.
• Useful info on the stack trace is stripped out.
• Attempts to look up the plugin's name via `document.src` breaks, as the code loads the binary with a user defined file extension. This will need to be adjusted so it looks for the correct file.

Diagnosing issues

To diagnose issues with plugins, head to Project settings and enable the option "Create a test build" (found under the Essentials tab). Once it's built, you can run the game normally and open the Dev Tools to diagnose the issue.

Alternatively, you can download the SDK version of NW.js (that matches with the version selected on the Cook Tool) and run nw.exe --nwapp="path-to-the-output" (or nw --nwapp="path-to-the-output" on Linux) to access the DevTools. Make sure that the option to package the game files isn't turned on.