Create a mod in the game under options, then modify the mod directory which will override default settings. For each type of override, find the existing vanilla version under the "Default" directory and use it as an example for the corresponding folder in your mod directory.

You can also upload the mod to steam workshop via the in-game mod options. Please test your mod in the game to make sure it's working before uploading it.

You can make new world presets in "world_presets" of your mod directory following the examples in the existing default/world_presets. You must use ordered-prompts.txt to specify the order in which you want to present your presets to the user. The presets will be appended to the vanilla presets; there is no overriding logic in this case.

Be sure to specify survival_bars if applicable. If survival_bars is specified, each comma-delineated string must correspond to a survival bar ID inside survival_bars of either the mod or default directory.

You must use ordered-survival-bars.txt to specify the order the user would see your survival bars in the new game selection as well as within the game itself. You can then add your own survival bar txt file with the desired parameters. You can also override existing survival bars by specifying an existing ID, but this behavior is not tested. At this time, health is not treated as a survival bar, and contains separate logic which cannot be modded.

Configs for survival bars: Most options you can specify for survival bars in the txt file are self-explanatory if referring to those in the Default directory. check_for_decrease_event and check_for_increase_event must correspond to an existing folder gpt_calibration_results. per_turn_change can be CONSTANT_REGEN, CONSTANT_DRAIN, or CONSTANT_DRAIN_LENIENT. check_for_consumable, if specified, must also correspond to a folder in gpt_calibration_results, and will be used to check whether a consumable can heal this survival bar type. check_for_consumable_prio influences the order in which a consumable is checked for survival bars. For example, if "granola bar" would've healed both "HUNGER" and "ENERGY" survival bars, the winning candidate is the one with lower priority number.

• Under the "Default" directory, find the relevant event check you want to modify under gpt_calibration_input.
  
• Under the "AI" directory, use gpt_testing.exe to figure out a good prompt for event checks. To use gpt_testing.exe, you must use a command line utility such as CMD, and call it with the format "gpt_testing.exe [model_name]" for example gpt_testing.exe KoboldAI/GPT-Neo-1.3B-Adventure. Fire up the exe and modify "input.txt". If "topScores" line is present, the output will be in logprob form. Delete that line if you want free-form text generation instead. disallowedTokens uses the separator "<|SEP|>". repetitionPenalty defaults to 1. Please note if increasing repetition penalty, some non-GPT-Neo models are much more sensitive than GPT-Neo models.
  
• In the mod directory's gpt_calibration_input, you must make a "version.txt" file with a number such as 1. Increase the version number when you update the mod which triggers the user's calibration to run if they use a non-standard model.
  
• For each event check you want to override, make a folder with the same name, with your example txt files for calibration. A file beginning with "yes" is treated as a positive example and beginning with "no" is treated as a negative example. Then you must run my_gpt_calibration.exe for a select number of commonly used models, by running gpt_calibration_caller.bat. You should then see the results in gpt_calibration_results. Please note the goose ai calibration endpoint is going through my server and is rate-limited to 30 calls per day to avoid racking up costs.

Under the "Default" directory, find the prompts you want to override, and copy the modified versions into your mod directory's "Prompts" directory. Use gpt_testing.exe to quickly test whether a prompt has the desired effect before testing it in the game.

Variables to replace are encased in the dollar sign bracket notation, e.g. ${example_variable}. These flags will tell the program to replace these strings with the corresponding actual strings from the game/story.

In general, capitalized variable names are reusable throughout all of the prompts, whereas lowercase variable names are specific to that prompt.