Skip to content

Savegame

Jan Sandström edited this page Sep 5, 2021 · 1 revision

A savegame is generated when the player chooses the save option from the pause menu. This exits the game and when the game is resumed, the savegame is consumed, giving no second chances on failure, enforcing permadeath.

The settings file is not generated by the application but is read if it is manually created.

Path Description
$HOME/.solarus/tunics/save.dat Savegame file
$HOME/.solarus/tunics/tunics.dat Development settings file

On windows this translates to [system_drive]/users/[user_name]/.solarus/tunics.

In the development settings file you may override certain application defaults:

Setting Default Description
skip_cinematics false Skips intro and cutscenes
debug_cheat false Enables a cheat that will let you see which block or pot that hides a switch
debug_filename "wdebug.txt" Output file for zentropy.debug() ("-" means stdout)
debug_walking_speed 88 Hero walking speed in pixels/second
debug_flying false Enable flying mode
debug_validate false Enable validation execution mode
debug_starting_location "rooms/intro_1" Set custom starting location
quest_seed os.time() Pseudorandom seed used for a new game
quest_tier 1 Starting tier for a new game (integer or item name in quotation marks)
quest_sword_ability 1 Hero sword ability
tier_tileset pseudorandom choice from available tilesets Dungeon tileset
tier_keys 3 Number of keys in a dungeon
tier_fairies 1 Number of fairy rooms in a dungeon
tier_culdesacs 3 Number of cul-de-sacs in a dungeon
Clone this wiki locally