It took me a while to get my head around running RMMZ in Ubuntu and debugging plugins. Perhaps because it isn't officially supported! Hopefully this will help anyone who tries something similar: Running RMMZ itself: Install PlayOnLinux In PlayOnLinux, hit the Install button and select the RMMZ installer
It took me a while to get my head around running RMMZ in Ubuntu and debugging plugins. Perhaps because it isn't officially supported! Hopefully this will help anyone who tries something similar:
Running RMMZ itself:
- Install PlayOnLinux
- In PlayOnLinux, hit the Install button and select the RMMZ installer
- Complete the wizard
- Create a shortcut
You should now be able to launch RMMZ like any other application. It will appear in a Wine window. You can create, edit and save games. However, you will not be able to launch them.
To launch and debug we will first configure the WebStorm IDE:
- Install WebStorm (you can get it from the Snap Store)
- Install NW.js (previously known as node-webkit):
- Download the 64-bit SDK from https://nwjs.io/downloads/
- Unzip it to ~/.local/nwjs-sdk-v0.55.0-linux-x64
- Created a symlink from /home/user/.local/bin to ~/.local/nwjs-sdk-v0.55.0-linux-x64/nw
- Open your RMMZ project folder in WebStorm
- Create an "NW.js" configuration as follows:
- NW.js app: project folder (it contains package.json)
- NW.js arguments: None
- Working directory: project folder
- Environment variables: None
- NW.js interpreter: ~/.local/bin/nw
- Also create an "Attach to Node.js/Chrome" configuration as follows:
- Host: localhost
- Port: 34313 (it doesn't actually matter)
- Attach to: "Chrome or Node.js... started with --inspect"
- Reconnect automatically: True
To launch and debug the RMMZ project:
- Launch the NW.js configuration in Debug mode
- Wait for this message to appear in the console:
DevTools listening on ws://127.0.0.1:54321/devtools/browser/527f34ec-746d-4e3f-8f3e-6c2287d157d1
- Click on the ws:// link to start the "Attach" config
- You will be offered a dropdown of HTML files to attach to, pick "index.html"
- Go back to the NW.js tab
- Click "Reload in Browser"
The project will now be reloaded, and you will hit any load-time breakpoints that you have set.
References