CfgLoader - KCD2 Cfg Mod Manager

Python-tool for managing .cfg files for various (supported) mods. Includes control over the order in which .cfg files are loaded. It also provides instructions for manually managing cfg files (for those who cannot use the application). Note: This is not a "mod". It is an application/tool that supports the use of multiple .cfg files with a custom boot order and ensures that all commands associated with .cfg files in the 'Mods' folder are executed correctly (games typically use the 'mod.cfg' file in the 'Mods' folder in the 'Mods' folder). What is a Python-based application that controls the order of loading a game / downloading multiple .cfg files. The .cfg file provides a new way to package mods (it also loads files located in the game's root directory). For more information on this, see the Mod Developer's Instructions section below. Steps for mod users Download the supported mod (the page should clearly indicate that it is supported). If the file 'autoexec.cfg' is not present in the game's installation folder, create the file 'autoexec.cfg' or download an additional file 'Autoexec Prereq'. Add the following command to the file (do not include quotation marks): "exec CfgLoader.cfg", save and close the file. Run the included application "KCD2 CFG Manager.py" (make sure Python is installed). Select the game installation folder (if you have checked out the mod to the game folder, it should automatically become the default folder) and set the installation order. Then click the Update CfgLoader File button and wait for the Success message to appear. Close the application when you are finished. You will need to run this app again when you install a new linked mod. After installation, it is recommended that you create a desktop shortcut to your application. The application is not available. Can I install a linked mod without an application? If Python is unavailable for some reason, you can manually create and manage the file 'CfgLoader.cfg'. Alternatively, you can control it directly using the file 'autoexec.cfg' (same procedure, only another file). Simply create this file, open it in Notepad (or any other text editor) and add a command to run the .cfg file packaged as a "supported" mod: exec config-filename.cfg exec config-filename2.cfg exec config-filename3.cfg To add such an exec command, locate the .cfg file name and add a string to the 'CfgLoader.cfg' file for that file. The game runs from top to bottom, so the last running file will overwrite all values common to previously downloaded files. instructions for mod developers (creating "supported" mods): Pack a .cfg file and unpack it into the main installation folder of the game or, if you decide to pack it into the 'Mods' folder (recommended), read on. Otherwise everything is ready: To package mods in the 'Mods' folder, it must contain the file 'mod.manifest' (as usual) and the folder 'Data'. Place the .cfg file in the 'data' folder and package the .cfg as .pak. Do not call the .cfg file 'mod.cfg', 'autoexec.cfg', 'user.cfg', or 'system.cfg'. The application will ignore .cfg files with these names. You can publish your mod and let users know that it is "supported" by adding 'CfgLoader' to the mod name, filename, and file description. See my Soft Shadows and Vividus Lux mods (in the 'Mods' folder) as examples of properly supported mods (supported versions can be found in the 'Updates' file on both pages).