4. Mod Configuration

Understanding the config.cpp

• Inside your Workbench Source Directory\Test Mod\Scripts directory, you should find a config.cpp. Open it.
• testmod_scripts refers to the classname? of this unpacked mod folder. I believe this is used if someone were to require your mod in the CfgPatches.testmod_scripts.requiredAddons array of their mod's config.cpp.
• CfgMods.testmod should really just be the name of your mod. I don't 100% know the purpose of this.
• CfgMods.dir should really just be the name of your mod. I don't 100% know the purpose of this.
• CfgMods.dependencies should be the game script modules you depend on. The possible values here should be :

1. Core
2. GameLib
3. Game
4. World
5. Mission

• CfgMods.defs should point to the relative paths inside the eventual packed pbo of the script modules. If you require more or less script modules, you have to change the values here aswell as in CfgMods.dependencies. What is crucial here is the 'Test Mod/Scripts' prefix infront of the script module directories. This refers to the PBO prefix. You can see this prefix by opening the $PREFIX$ file in the Test Mod/Scripts directory.