itch.io

That's odd. Is your anti-virus blocking it?

Hello, 121542650!

Have you extracted all of the files in the zip file? It needs all of the files within it to work properly. 

Ahoy! Quick question about the plugin:

What is the deal with the ImageCache and AudioCache, exactly? Since my game must also reside in the Program Files folder (via an installer) or packaged within a MSIX package (which don't allow writing anything to the game's folder), do I need to include them, or I can just allow the game to create them?

I checked the zip file I uploaded on itch and the Bootstrap is in the files. Could you check the zip file that you downloaded if the Bootstrap folder is missing?

Hello, thatcombatwombat! 

Double check that the Bootstrap folder is present and the Dragonhouse.GameMaster is inside it. 

In recent versions of the tool, the Bootstrap was replaced with a new Dragonhouse.GameMaster, which is a merger of the bootstrap and the Game Master executables.

No problem.

If you mean what files you should include to the steam build, only the game files that are on that folder. Do not include any save files.

Hello, Daisuke Tanaka! 

The protonout folder is the one for uploading to Steam, as it can work with the Steam Deck automatically. 

So... A bit of an update on that side (sort of). I've noticed that the Steam Overlay also didn't work after packing, as the required command line argument wasn't passed to the game's executable. Although I'm not sure if these are correlated, but it's possible that there could be a conflict. 

I am working on adding the required flag automatically for the Steam builds, but until then, you can fix that (if needed) by adding the --in-process-gpu in the executable flags (found under Project Settings -> Compiler and Packer -> Halva Settings). 

Hello, WonderLang!

This error appears if the files in the Binaries folder are missing. Make sure that all files from the Binaries folder are included in the ZIP file.

Hello, Dark_Ansem! 

Asset compression (compressing to Opus, WebP, etc.) is a utility within the tool. The compression options that are in the project settings only affects the compression of the packages. It's not required to use the asset compressor utility.

Hello, GamesOfLove!

It's possible that it's a compatibility issue with Steam Proton. At the moment, I don't have a fix for it, but I am looking into it. A potential solution is to set up the Windows Subsystem for Linux and run the Linux version of the tool, to create a native Linux build.

Hello, Egg!

The cook tool does its job with the project that you give it. If (for example) you use the Cook Tool to work on the exported version of it, it will create a build based on that. There isn't any file duplication unless there was a mixup in the setup.

In addition, if you use newer versions of NW.js in your project (configurable in the project settings) it can add about 400MB to the final build. It's normal that newer versions of it can make the final build bigger. Finally, the included asset compressor (found under the utilities menu) can help in compressing the game's files by using more modern image and audio formats (which are more efficient in compression.

Hello, littlemisssoso! 

At the moment, I am not sure why this happens, as the bootstrap in the Steam Proton files shouldn't take the controller input. It could be a compatibility issue. 

I'm looking into this. 

Found the issue: There was another Windows specific call that wasn't implemented in Proton. Uploading a fix for it as soon as possible.

EDIT: The fix is live now.

Hello!

I've pushed out a slightly experimental version of the Game Master that is compatible with Steam Proton). You'll find it on your downloads page.

It's under Project and utilities -> Utilities -> Metadata Editor. You'll find the Chromium Flags option there.

Hello, littlemisssoso!

1 The failure to close the game properly is (most likely) an issue with the version of nwjs you are using. I'm looking into a solution that ensures that the game closes properly.

2. This should be added automatically by using the built-in Metadata Editor. Simply add it to the Chromium Flags section and click on Save.

A bit of an update: I have a suspicion that the code that checks if the app is packaged into an msix package might be causing crashes on Proton (since it doesn't implement the code that is necessary for it). Although I reccomend building a native Linux build, I'll look into better handling this scenario for the bootstrapper.

For now, yes. I am looking into cross-building (at least, with the assistance of the Windows Subsystem for Linux).

Hello, Software Wulf!

I can't say for sure why the Windows version doesn't work with Proton (as there could be some bits of code where Proton doesn't play well). However, you can use the Linux version of the Cook Tool Deluxe and create a native Linux version of the game (assuming that any dependencies for the game are also compatible with Linux).

If I recall correctly, the SteamOS has a desktop mode, so you could set up the tool on the Deck. Alternatively, using the Windows Subsystem for Linux would also set up a Linux environment so you can use the Linux version).

Hello, Dice!

It is a bug with the plugin, where trying to save (while the folder wasn't created) would cause the save system to break (at least until the settings file was created before saving). I pushed out a fix for the plugin, so it creates the folder properly.

As far as I know, only the Book plugin is affected. 

Ahoy! A bit of an update regarding that issue: the issue turns out to be how the book plugin tries to find it's name. Since it's loaded via nwjs' built in mechanism (since the compiled version of the plugin can't be loaded through normal means), trying to find the name via looking up in the document, it will return null, thus breaking it during launch.

This was certainly a tough bug to figure out. But it was a pattern that I saw in other plugin. Took me a while to notice it here as well. 

The current workaround for this is to hardcode the name.

The plugin is licensed under the MIT license. It's fine for use in commercial games.

The patch is live. It's part of R5.06u6.

Hello, mira.jp!

It seems to be a technical issue, where the creation of the .FileCatalog.sbfc fails. This is an issue for cases where the option to clear the cache after the game closes is turned off. I'm working on a patch to fix this.

Quick update: I found the issue: a race condition prevented the creation of the file catalog. I'm pushing out the hotfix as soon as possible.

Hello, ianov!

A bit of an update: I couldn't replicate the error for the missing file catalog. This could have been a fluke. However, I've done some improvements for Halva, so it may address this. If it still appears, let me know.

Fixed this bit in the updated plugin pack.

Hello, ianov! 

Looking into the issues, they are bugs. I am working on a fix for these and upload them as soon as possible. 

Hello, Kawagoe_Love!

RPG Maker VX Ace and older versions of the engine aren't supported by this tool. Currently, it supports RPG Maker MV and MZ.

Hello, jbariller!

The saves are stored depending on the plugin's settings. As a quick reference:

1. If set to game's location, it will save on the game's folder.
2. If set to the App Data, it will save on the Local App Data folder (under a folder name that is referenced on the package.json file. It reads the "name" variable from there.
3.  If set to User Folder, it will save to the current user's folder (for example, C:\Users\MainUser).

I am aware of this: RPGMaker Data Folder Encrypter by coffeenahc (itch.io)

Hello, Arxxur!

At present, encrypting game data without packaging is not feasible. However, you can encrypt your game files using RPG Maker's export function and then compile the source code, which is an option in the project settings. This method will safeguard your game's assets and code, and there are plugins available to protect the database. Be aware that some plugins might not function correctly after compilation.

A fix for the user agreement file is changing the code a bit, where it should look up the base folder of the game's executable, instead of the base folder. For example, to return the folder for saving that file, it could be like this:

return path.join(path.dirname(base), "UserConfig");

base (in this case) would be the executable (usually found with something like 

var path = require('path');
var base = path.dirname(process.mainModule.filename);

Send me a screenshot, when you are able to.

Hello, reginaldbrown912!

• When you say that it creates a user agreement file, what do you mean, exactly? If it creates a file that tells the game that the user has accepted the terms, you may need to re-locate the file (either saving to the folder that the final build resides or on the user's folder), since it could be deleted with the cache.
• Could you show me the settings that you have applied to the plugin?

Hello!

In regards to that plugin, it will only break if you enable the compilation of the source code. If you have the "Package game files" turned on (and the "Compile source files" turned off) you should be good to go.

Hello!

I'm pushing out a hotfix for it. It will be available soon.

No problem.