AutoCfg Loader - Mod Cfg File Executor

This is intended to be a requirement for other modders to use, allowing them to execute their mod's .cfg files on game launch (to prevent the game from overriding cfg values on launch), when the player spawns in after loading/starting a game (to prevent level/map params from overriding cfg values), and when the player unpauses the game or skips time/sleeps (to prevent game settings changes from overriding cfg values).

\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

To package your mod to work with this, your .cfg file should be placed in a "Data/ModConfigs/" sub-directory of your mod's main root folder, and that directory should be packed in a .pak archive... For example:

KCD2/Mods/ExampleModFolder/Data/ExampleModArchive.pak/ModConfigs/ExampleModConfig.cfg

└── ExampleModFolder/

└── mod.manifest

└── mod.cfg

└── ExampleModArchive.pak

└── /ModConfigs/

└── ExampleModConfig.cfg

You should also still include a traditional "mod.cfg" file in your mod's root folder, for people that would prefer not to use this in order to use your mod (just be sure to remember to update both for mod updates).

\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\