-
Notifications
You must be signed in to change notification settings - Fork 2
Debug
The mod offers various debug functionalities available when starting the game in debug mode.
To start the game in debug mode use the Worldsmith feature to test the map or add the launch option -debug "<PATH TO YOUR MAP>" in steam.
When starting the game in debug a menu will be added offering some QoL functionality.
To access the pause menu go to Options > Mods > Switch Blocks.
The pause menu the offers 5 options to:
To reload changes made to the settings.
To reload changes made to any drawable.
To reload changes made to any seed file. (seeds_, resets_, deactivates_, durations_)
To create the required file structure for the mod.
To create the blocks.xml with all possible settings for the used block types.
To create templates for drawables in a templates folder.
This file contains information about the loading process of mods and should be looked at first should something go wrong.
You can find this file at the path your Jump King is installed at.
E.g. D:\SteamLibrary\steamapps\common\Jump King\ModLoadLog.txt.
Should an error occur with the mod as well as how it failed will be listed here.
Like the mod load log this is an important file to debug the mod.
Crashes will be listed here should any occur.
Unlike the ModLoadLog this file will not be created new every time and every crash will be listed here.
Unfortunately Worldsmith will also write messages into the crash log should the ending data not be correct, and as of writing this, Worldsmith does not create ending data correctly creating a lot of entries regarding incorrect ending data.
You can find this file at the path your Jump King is installed at.
E.g. D:\SteamLibrary\steamapps\common\Jump King\crashlog.log.