Skip to main content

On Sale: GamesAssetsToolsTabletopComics
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

2 issues

A topic by reginaldbrown912 created Apr 03, 2024 Views: 105 Replies: 3
Viewing posts 1 to 2

One issue is I use an  user agreement plugin, that needs to create a license file to show acceptance of the  agreement, and  when this is active, it cannot create that file, and the second issue I have is even with the save game handler when deployed it does  not allow the saving/loading of games.  It works perfectly during game test but after deployment not so much. I wonder if I am just missing something, any insight would be appreciated. 

Developer (1 edit)

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?

Yes it creates a file in the root of the project to show its been accepted. It seems like new files cant be created to the root of the project. I left  the  save plugin parameters at defaults where it creates a save file in the user data folder in the root project.  I am at work but i can send a screenshot when I get home tonight.

Developer (1 edit)

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.