Abonner for at downloade
Adonnay's Troop Changer

ATC - Adonnay's Troop Changer


ALSO: If you had the Nexus version installed, make sure you deinstall/remove it before trying to use the Steam version. The game will always load the Nexus version of the mod first!

What does ATC do?
A: ATC in itself does not do anything. It's a framework, a middleware. ATC enables modders to have their troop trees added to the game without the need to create custom cultures or mess with the native game files. It can also merge multiple troop mods into one allowing for a wide variety of troops in your game.


What it does NOT do?
A: ATC does NOT create troops or troop trees of any kind. You have to bring your own troop tree or download one of the many ATC compatible troop trees.


What does make a troop tree ATC compatible?
A: A single configuration file. You can find a sample file in the ATC /Config subfolder.


Is there a way to check if the mod works?
A: Yes. Apart from the ingame message at the start of the game (ATC loaded successfully) you can check the debug log file that is stored in \ProgramData\Mount & Blade Bannerlord II\ATC and called ATC.debug.log.


My game crashes on startup with only ATC active. Why?
A: First of all make sure you have the correct ATC version for your Bannerlord version!
Then have read a couple of reports that people don't seem to have enough rights to write into the \ProgramData\Mount & Blade Bannerlord II\ folder. I have no idea why but make sure you have. You could also try to manually add the folder \ATC if it is not present. Starting the game as administrator can also help.


Where can I find the configuration file?
A: You can find the configuration file called ATC.settings.xml in \ProgramData\Mount & Blade Bannerlord II\ATC. It contains the following options:

• EnableModScan - allows ATC to scan active mods for ATC configuration files (all files named *ATC.modconfig.xml)
  
• EnableCustomTemplates - Let ATC modify the party templates for newly spawned lords on the fly
  
• DebugConfigRead - debug messages when a configuration is called
  
• DebugRecruitSpawn - debug messages when a new volunteer is spawned
  
• DebugAIRecruiting - debug messages when a volunteer is recruited
  
• EliteOnlyInCastleVillages - sets the elite spawn logic to the vanilla logic
  
• EliteSpawnChance - only relevant if EliteOnlyInCastleVillages is set to 'false'
  
• ElitePowerThreshold - only relevant if EliteOnlyInCastleVillages is set to 'false'
  
• EliteSpawnChanceCap - only relevant if EliteOnlyInCastleVillages is set to 'false'
  
• RecruitMaxUpgradeTier - volunteers slowly level up when not recruited, this sets the maximum tier to level up to. (4 = vanilla)
  
• LevelRecruitsUpToTier - immediately level up the recruits to that tier when they spawn (1 = vanilla/no instant level up)
  
• MaxLogSizeInKB - only relevant if you enable any of the debug messages above

• <EnableModScan>true</EnableModScan>
  
• <EnableCustomTemplates>true</EnableCustomTemplates>
  
• <DebugConfigRead>false</DebugConfigRead>
  
• <DebugRecruitSpawn>false</DebugRecruitSpawn>
  
• <DebugAIRecruiting>false</DebugAIRecruiting>
  
• <EliteOnlyInCastleVillages>true</EliteOnlyInCastleVillages>
  
• <EliteSpawnChance>5</EliteSpawnChance>
  
• <ElitePowerThreshold>200</ElitePowerThreshold>
  
• <EliteSpawnChanceCap>20</EliteSpawnChanceCap>
  
• <RecruitMaxUpgradeTier>4</RecruitMaxUpgradeTier>
  
• <LevelRecruitsUpToTier>1</LevelRecruitsUpToTier>
  
• <MaxLogSizeInKB>500</MaxLogSizeInKB>