Mount & Blade II: Bannerlord sells itself on emergent chaos. One bad cavalry charge can snowball into a lost kingdom, and one unlucky headshot can end a 40-hour campaign. Console commands sit right at the intersection of that chaos and control, giving players the power to bend Bannerlord’s brutal sandbox without fully breaking it.
Used correctly, the developer console is a tool for experimentation, recovery, and testing. Used recklessly, it’s a fast track to a hollow campaign where nothing feels earned. Understanding what console commands are and aren’t is the difference between smart sandbox mastery and accidentally nuking your own save.
What the Bannerlord Console Actually Is
Bannerlord’s console is a developer-facing debug tool that Taleworlds ships with the game, not a hidden cheat menu or mod-exclusive feature. It allows players to execute text-based commands that directly interact with campaign systems like gold, troops, skills, items, and world state.
This isn’t Skyrim’s god-mode playground. Most commands are granular, literal, and system-facing. You’re telling the engine to do something specific, not flipping a universal “win” switch.
What Console Commands Are Good For
The console shines in single-player sandbox experimentation. Testing a late-game build, skipping early grind, or simulating endgame army compositions are all valid uses. Modders and theorycrafters rely on commands to stress-test balance, AI behavior, and perk interactions without replaying the same opening hours.
They’re also a safety net. Corrupt quests, bugged companions, broken clan states, or lost items can sometimes be fixed with a single command instead of abandoning a campaign. In a game this systemic, recovery tools matter.
What Console Commands Are Not
They are not a substitute for understanding Bannerlord’s mechanics. Giving yourself max skills won’t teach you timing, spacing, or how Bannerlord’s hitboxes punish bad positioning. Spawning elite troops won’t fix poor battlefield command or bad terrain reads.
They also don’t turn Bannerlord into an MMO-style cheat fest. There’s no multiplayer access, no PvP advantage, and no way to bypass core AI logic without mods. If you’re expecting instant invincibility with zero consequences, you’ll be disappointed.
Myths That Refuse to Die
One common myth is that using the console permanently breaks the game. In reality, most commands are safe when used deliberately. Problems usually come from stacking extreme changes, like maxing every stat, spawning thousands of troops, or altering world states mid-quest.
Another myth is that console use disables achievements outright. Bannerlord’s achievement behavior can vary by platform and version, but the real risk is destabilizing the campaign, not instant punishment for experimentation.
When Cheating Makes Sense
Cheating makes sense when the game stops respecting your time. Rebuilding after a bugged siege, testing perk synergies before committing a new character, or jumping straight into late-game wars are all reasonable scenarios.
It also makes sense for learning. Seeing how high-level perks scale, how troop tiers perform in mass battles, or how the economy reacts to sudden wealth teaches you systems faster than raw playtime alone.
When Cheating Ruins the Experience
Bannerlord’s magic lives in tension. If you erase risk too early, battles lose their bite and progression collapses. Giving yourself infinite gold or max stats at level one often kills motivation within hours.
The sandbox works best when cheats are used surgically. One fix, one test, one adjustment. Anything more and you’re not playing Bannerlord anymore, you’re just spectating its systems.
Enabling the Developer Console
Before any command works, the developer console must be enabled. On PC, this is done by editing the engine_config.txt file in the Bannerlord documents folder and setting cheat_mode to 1. Once enabled, the console opens in-game with Alt + ` (tilde), where commands can be typed and executed in real time.
This step alone filters casual curiosity from intentional use. If you’re willing to toggle cheat mode manually, you’re probably using the console for a reason, not just impulse power.
Risks You Should Understand First
Save corruption is rare but possible, especially when altering world states during active quests or wars. Balance disruption is guaranteed if you overuse stat, money, or troop commands. Some campaigns simply stop feeling meaningful once progression is bypassed.
The console doesn’t judge you, but Bannerlord’s systems will react. Knowing when to intervene, and when to let the sandbox punish you, is the real skill ceiling of console command mastery.
How to Enable the Developer Console in Mount & Blade II: Bannerlord (Vanilla & Modded Setups)
Everything about console commands starts here. If cheat mode isn’t properly enabled, Bannerlord will simply ignore every command you type, no matter how correct it is. Whether you’re fixing a broken campaign or stress-testing builds, this setup step is non-negotiable.
Vanilla Method: Editing engine_config.txt
For unmodded Bannerlord, enabling the developer console is a manual toggle buried in the config files. Navigate to Documents\Mount and Blade II Bannerlord\Configs and open engine_config.txt with Notepad or any text editor.
Find the line that reads cheat_mode = 0 and change it to cheat_mode = 1. Save the file, launch the game, and load into a campaign. The console opens with Alt + ` (tilde), letting you enter commands live without restarting or reloading.
Modded Method: Developer Console Mods
If you’re running a heavily modded setup, editing config files isn’t always ideal. Some mods overwrite configs on launch, while others disable cheat mode entirely to avoid conflicts.
Popular mods like Developer Console, Detailed Character Creation, or full overhaul frameworks often include built-in console toggles. These usually appear as an in-game menu option or a hotkey, and they’re safer when running large mod lists because they respect mod load order and dependencies.
Verifying the Console Is Working
Once enabled, open the console and type help. If the console responds with a command list instead of doing nothing, cheat mode is active. If the console opens but rejects commands, cheat mode is still disabled or being overridden by a mod.
This is the point where many players think Bannerlord is bugged. In reality, the game is extremely strict about cheat permissions, especially in modded environments.
Core Console Commands You’ll Actually Use
The console is vast, but only a small subset of commands are genuinely useful in real campaigns. These are the tools that fix problems, enable testing, or skip dead time without dismantling the sandbox.
Money and Economy Control
campaign.add_gold_to_hero X is the cleanest way to stabilize a broken economy. Use it to recover from bugged tribute payments, bankrupt clans, or caravans that never paid out.
Avoid spamming massive sums early. Bannerlord’s economy reacts aggressively to sudden wealth, inflating wages, prices, and AI behavior in ways that can quietly ruin long-term balance.
Items and Gear Testing
campaign.give_item_to_main_party [item_id] lets you test weapons, armor, and mounts without praying to RNG. This is invaluable for comparing DPS, swing speed, armor values, and handling before committing perks or crafting paths.
Use this when theorycrafting builds or testing modded items. Avoid handing yourself full legendary kits unless you’re explicitly testing endgame scaling.
Troops and Party Control
campaign.add_troops [troop_id] X is ideal for rebuilding after wiped parties or testing army compositions. It’s also useful for benchmarking how different troop tiers perform in large-scale battles.
Skipping troop progression entirely removes one of Bannerlord’s strongest feedback loops. Use this command to restore parity, not to permanently bypass recruitment and training.
Skills, Perks, and Character Progression
campaign.add_skill_xp_to_hero [skill] X allows precise control over leveling. This is essential when testing perk interactions, leadership breakpoints, or late-game scaling without grinding tournaments or looters for hours.
Maxing every skill flattens the RPG layer fast. Target specific skills tied to the build or system you’re evaluating to keep progression meaningful.
Map Control and Campaign Fixes
campaign.teleport_main_party_to_settlement [settlement_id] is a lifesaver for stuck quests, unreachable objectives, or broken sieges. It’s also useful for jumping straight into wars or testing faction behavior in different regions.
Teleporting mid-war or during active quests can desync events. Use it deliberately, then let the campaign breathe before issuing more commands.
Common Risks and Hidden Limitations
While Bannerlord doesn’t aggressively punish console use, consequences still exist. Achievements are disabled when cheat mode is active, even if you only use the console once.
Save corruption is uncommon but real, especially when altering factions, quests, or world states mid-event. Balance damage is guaranteed if commands replace progression instead of supporting it.
The developer console is a scalpel, not a god mode. When used to correct errors, test systems, or reclaim lost time, it deepens your understanding of Bannerlord’s sandbox instead of hollowing it out.
Essential Quality-of-Life Console Commands (Money, XP, Renown, Influence, and Skills)
Once you understand that the developer console is a precision tool, these quality-of-life commands become indispensable. They’re designed to remove busywork, repair broken progression, or fast-forward systems you’ve already mastered. Used correctly, they keep Bannerlord’s sandbox intact while respecting your time.
Before any of these commands work, cheat mode must be enabled. In your Bannerlord config file, set cheat_mode = 1, then restart the game. Open the console in-game with Alt + ~ (or Alt + ` depending on keyboard layout).
Money and Economic Control
campaign.add_gold_to_hero X is the most commonly used command for a reason. It instantly fixes bankrupt campaigns caused by failed caravans, bugged workshops, or mid-war spirals where upkeep outpaces income.
Use gold to stabilize an economy, not erase it. Dropping millions trivializes trade routes, kingdom decisions, and ransom mechanics, flattening Bannerlord’s otherwise strong economic simulation.
For testing, gold is essential when evaluating workshop balance, caravan ROI, or late-game clan expenses. Inject just enough currency to reach the system you’re analyzing, then let the economy run naturally.
Experience and Level Progression
campaign.add_xp_to_hero X accelerates character leveling without touching individual skills. This is useful when you want perk unlocks or attribute points without grinding battles or smithing loops.
XP injection can skew pacing if overused. Bannerlord’s attribute and focus point economy is tuned around time investment, so dumping levels early can create awkward power spikes.
For controlled testing, pair XP gains with limited focus allocation. This keeps your build readable and avoids turning your character into a stat blob.
Renown and Clan Scaling
campaign.add_renown_to_clan X directly affects clan tier progression. This command is invaluable if a campaign stalls due to broken quests, missing tournaments, or wars that end too quickly to generate renown.
Clan tier gates everything from party size to kingdom eligibility. Adjusting renown lets you test vassal mechanics, mercenary contracts, and army leadership without replaying early-game loops.
Jumping multiple tiers at once can destabilize pacing. Promotions trigger new obligations and enemy aggro, so step renown up gradually to keep the campaign reactive instead of chaotic.
Influence and Kingdom Power
campaign.add_influence X is strictly for kingdom play, and it shines when internal politics break down. Influence fuels army cohesion, policy votes, and settlement decisions, all of which can deadlock in long wars.
This command is especially useful for testing policy synergies or AI voting behavior. Influence starvation can mask whether a system is flawed or just under-resourced.
Avoid infinite influence. Removing political pressure turns kingdom management into a menu-clicker and strips weight from diplomacy and internal conflict.
Skills and Perk Testing
campaign.add_skill_xp_to_hero [skill] X is the gold standard for build experimentation. It allows surgical control over perks, letting you test combat breakpoints, governor bonuses, or party-wide effects without weeks of in-game time.
This is essential for mod users validating perk trees or rebalanced skill curves. It also helps isolate whether a perk is underperforming due to numbers, scaling, or AI behavior.
Never max every skill unless you’re debugging. Bannerlord’s RPG depth comes from trade-offs, and removing them erases meaningful decision-making faster than any other command.
When to Use These Commands and When to Stop
Quality-of-life commands work best as course correction, not permanent crutches. They’re ideal for repairing broken saves, skipping content you’ve already beaten, or stress-testing mechanics at scale.
The moment you start solving every problem with the console, Bannerlord’s emergent storytelling collapses. Use these tools to protect your campaign, not replace it.
Items, Troops, and Party Control Commands – Testing Builds and Army Compositions
Once skills and influence are under control, the next logical step is direct manipulation of gear, units, and party structure. This is where Bannerlord’s sandbox turns into a testing lab, letting you isolate DPS curves, troop AI behavior, and morale scaling without grinding battles for hours.
These commands are most powerful when used with intent. You’re not just spawning toys, you’re validating whether a build, formation, or modded unit actually performs under live campaign conditions.
Item Commands – Gear Testing Without RNG
campaign.add_item [item_id] X is the backbone of equipment testing. It bypasses loot tables entirely, letting you slot specific weapons, armor tiers, or trade goods straight into your inventory.
This is critical for testing weapon balance and perk interactions. You can compare swing speed versus armor penetration, verify if perks apply correctly, or check whether a modded item breaks progression by spiking stats too early.
Avoid dumping full endgame kits at level one unless you’re debugging. Bannerlord’s combat relies heavily on relative power, and overgearing trivializes hitbox spacing, stamina pressure, and risk-reward loops.
Troop Spawning – Controlled Army Composition
campaign.add_troop [troop_id] X lets you build armies with surgical precision. Instead of recruiting whatever villages offer, you can test exact ratios like shield infantry screens, archer backlines, or cavalry shock units.
This command is invaluable for formation testing. You can stress-test how AI handles mixed-unit tactics, see where pathing breaks during sieges, or evaluate whether elite troops justify their wage-to-performance ratio.
Be cautious with mass spawns. Overloading parties with high-tier units can spike wages, morale loss, and food consumption, which may cascade into desertion or negative economy feedback loops.
Party Size and Roster Control
campaign.set_party_size_limit X removes artificial ceilings when testing large-scale battles. This is especially useful for modded campaigns or late-game scenarios where army mechanics don’t scale cleanly.
Pair this with troop spawning to simulate endgame armies without conquering half the map. It allows you to evaluate cohesion loss, reinforcement timing, and whether your PC can handle large engagements without stuttering.
Remember that party size ties into leadership perks and morale math. Inflating limits too far can hide balance issues that only appear under legitimate constraints.
Upgrading, Healing, and Maintaining Troops
campaign.heal_party instantly restores wounded units, which is perfect for repeated testing cycles. You can rerun the same battle multiple times to isolate RNG variance instead of attrition effects.
campaign.add_gold X indirectly supports army testing by removing economic pressure. High-tier troops are expensive, and gold starvation can skew results by forcing premature downsizing.
Do not treat infinite gold as neutral. Removing upkeep pressure changes how Bannerlord’s campaign systems push player decisions, especially around garrisons and mercenary contracts.
When Army Control Breaks the Campaign
Direct troop and item manipulation carries real risk. Spawning invalid items, deprecated troop IDs, or modded units mid-save can corrupt inventories or crash battle scenes.
Achievements are typically disabled once cheats are active, and balance erosion happens faster than expected. When every army is perfectly optimized, morale, terrain, and leadership perks lose relevance.
Use these commands like a designer, not a god. The goal is to test systems under controlled conditions, then return to organic play once the data you need is clear.
Campaign & Map Manipulation Commands (Teleporting, Factions, Settlements, and Time Control)
Once you start manipulating armies directly, the next logical step is bending the campaign map itself. Bannerlord’s strategic layer is where faction AI, economy, and warfare intersect, and console commands let you stress-test those systems without waiting 300 in-game days.
This is where things get powerful fast. Map control commands can invalidate logistics, diplomacy, and even war pacing, so treat them as diagnostic tools rather than quality-of-life shortcuts.
Teleporting Across the Campaign Map
campaign.teleport_to_settlement SettlementName instantly moves your party to a specific town, castle, or village. This is invaluable when testing siege defenses, regional economies, or faction reactions without riding across Calradia for ten minutes.
For more granular control, campaign.teleport_to_party PartyName lets you jump directly to lords, caravans, or armies. It’s ideal for observing AI behavior mid-campaign, especially when tracking why an army stalled, starved, or split unexpectedly.
Teleporting ignores travel time, terrain penalties, and ambush logic. That means you’re skipping fatigue, food drain, and map-based threat evaluation, all of which normally shape Bannerlord’s campaign flow.
Faction Control and Allegiance Manipulation
campaign.join_faction FactionName forces your clan into a kingdom without persuasion checks or reputation gates. This is perfect for testing late-game policies, ruler perks, or vassal cohesion without grinding influence.
If you want to go further, campaign.change_faction_of_party PartyName FactionName allows you to forcibly realign lords. This command is brutal but revealing, especially when analyzing how sudden power shifts affect war declarations and army composition.
Be cautious here. Bannerlord’s diplomacy AI assumes gradual faction change, and hard swaps can destabilize wars, cause stuck armies, or break influence calculations.
Settlement Ownership and World State Editing
campaign.change_owner_of_settlement SettlementName ClanName lets you rewrite the political map instantly. This is one of the best tools for testing rebellion mechanics, loyalty decay, and garrison sustainability under different rulers.
You can simulate edge cases like newly conquered towns with mismatched culture, zero loyalty, or hostile neighbors. It’s also useful for modders tuning tax output, militia growth, or governor perk interactions.
Settlement transfers bypass sieges, influence costs, and war logic. Expect strange behavior if you reshuffle too aggressively, including orphaned garrisons or AI factions declaring wars that no longer make strategic sense.
Time Control and Campaign Acceleration
campaign.set_time_speed X increases or decreases how fast days pass on the campaign map. This is essential when testing long-term systems like prosperity growth, clan aging, or policy snowballing.
Cranking time speed helps identify delayed bugs, such as perks that trigger incorrectly or economies that spiral after several in-game years. It’s also a clean way to observe whether your build scales or collapses over time.
Extreme values can break event pacing. Quests may fail instantly, pregnancies can resolve oddly, and AI decision-making may desync from the campaign clock.
Freezing and Forcing the World
campaign.pause_time effectively freezes the campaign while keeping the UI responsive. This is useful for inspecting army paths, trade routes, and faction borders without the world shifting underneath you.
Pairing paused time with teleport commands lets you stage scenarios with surgical precision. You can position armies, adjust ownership, then unpause to watch the simulation unfold.
Remember that Bannerlord was never designed for constant time freezing. Overuse can desync AI routines, especially during active wars or sieges.
Why Map Manipulation Is the Fastest Way to Break Balance
Map-level cheats bypass the friction that defines Bannerlord’s sandbox. Distance, time, and political cost are the core checks on player power, and removing them flattens the campaign into a sandbox with no resistance.
This is excellent for testing builds, mods, and AI behavior. It is terrible for preserving meaningful progression or emergent storytelling.
Use campaign manipulation when you need answers, not advantages. Once you understand how the systems react, roll back to a clean save and let Calradia fight back on its own terms.
Combat, Character, and Skill Cheats – Leveling, Attributes, Perks, and God Mode Explained
Once you stop bending the map, the next logical step is bending the player. Combat and character cheats operate at the most granular level of Bannerlord’s design, directly interacting with hit calculations, skill XP curves, perk gates, and survivability rules.
This is where testing builds becomes fast instead of tedious. It’s also where you can quietly obliterate progression if you’re not disciplined about what you change and when.
Enabling the Developer Console in Bannerlord
Before any of these commands work, the developer console must be enabled. In the Bannerlord launcher, go to Mods, make sure Sandbox, StoryMode, and CustomBattle are active, then enable the Developer Console mod if you’re using one.
If you’re running native Bannerlord without mods, open Documents/Mount and Blade II Bannerlord/Configs/engine_config.txt and change cheat_mode = 0 to cheat_mode = 1. Save the file, launch the game, then press Alt + ~ to open the console.
Cheat mode disables achievements for that save. Treat any campaign using these commands as a testing environment, not a long-term progression file.
Instant Leveling and Skill XP Control
The core command for character growth is campaign.add_skill_xp [SkillName] [Amount]. This injects raw XP directly into a skill, bypassing stamina, learning limits, and combat participation.
For example, campaign.add_skill_xp OneHanded 100000 will skyrocket One-Handed and instantly reveal whether your perk path actually delivers the DPS or survivability you expect. This is invaluable when comparing weapon trees or validating modded perks.
Dumping massive XP too early can soft-lock perk choices if you overshoot thresholds without planning. Always pause and select perks before stacking more XP, or you risk building a character with impressive numbers but broken synergies.
Attributes, Focus Points, and Level Control
Use campaign.add_attribute_points [Amount] to increase raw attributes like Vigor, Control, or Endurance. This directly affects learning rates, not just stat caps, so it has long-term ripple effects on progression.
campaign.add_focus_points [Amount] unlocks skill scaling without grinding. This is the cleanest way to simulate a late-game character without inflating levels unrealistically.
If you want brute-force progression, campaign.add_levels [Amount] works, but it’s the messiest option. Levels dump points in bulk and can distort perk pacing, making it harder to isolate why a build feels overpowered or underwhelming.
Perks, Builds, and Why Respec Testing Matters
Bannerlord does not natively support full perk respecs, which makes console testing essential. By injecting XP and levels selectively, you can recreate specific perk breakpoints and test interactions under real combat conditions.
This is especially important for perks affecting hit chance, damage modifiers, morale damage, or party-wide bonuses. Some perks look strong on paper but barely move the needle due to hidden multipliers or AI behavior.
When testing, isolate variables. Change one perk path, fight the same battle type, and watch kill speed, stamina drain, and survivability. That’s how you separate placebo perks from meta-defining ones.
God Mode and Combat Invulnerability
campaign.toggle_god_mode flips full player invulnerability. You take no damage, your horse becomes unkillable, and most combat checks simply fail to register against you.
This is not about power fantasy. God mode is for studying AI behavior, attack patterns, aggro switching, and formation collapse without constant reloads.
God mode breaks immersion instantly and can mask poor positioning or timing. Turn it off once you understand the mechanics you’re testing, or you’ll train bad habits that collapse the moment real damage returns.
Healing, Knockouts, and Battlefield Control
campaign.heal_player instantly restores HP and clears injuries. This is useful for repeated duel testing or prolonged siege experiments where attrition would normally end the run.
You can also combine healing with troop spawn commands to stress-test engagements. Watching how fast enemies break, rout, or reorganize under pressure reveals more about Bannerlord’s morale system than raw stats ever will.
Repeated healing mid-fight can desync combat flow. Bannerlord expects downtime between engagements, and ignoring that can produce odd AI hesitation or delayed reactions.
Risks: Save Integrity, Balance Collapse, and False Positives
Character-level cheats are less visible than map manipulation, but they’re just as dangerous. Over-leveling can cause companions or AI lords to scale unpredictably, especially in long campaigns.
Some perks and skills are evaluated on level-up or battle end. Injecting XP mid-loop can cause perks to misfire or not register until the next combat instance.
Always keep a clean backup save. Treat combat and character cheats as lab tools, not permanent upgrades, and Calradia will remain a system you understand instead of one you accidentally break.
Advanced & Lesser-Known Developer Commands for Modders and Power Users
Everything discussed so far assumes you’re already treating Bannerlord like a living system, not a power trip. This is where the developer console stops being a cheat menu and starts functioning like a diagnostic toolkit for campaign logic, AI behavior, and mod validation.
Before touching any of these commands, you need the console enabled. In Documents/Mount and Blade II Bannerlord/Configs/engine_config.txt, set cheat_mode = 1. Boot the game, load a campaign, and open the console with Alt + ~. If the console doesn’t respond, the setting didn’t save correctly.
Economy, Gold Injection, and Market Stress Testing
campaign.add_gold_to_hero X injects raw denars directly into your character. This is best used for testing late-game economy loops like caravan ROI, workshop profitability, and army upkeep scaling.
Dumping massive gold early can destabilize town prosperity and trade prices. Bannerlord’s economy reacts to player spending, so inflating your wallet can cause artificial shortages or surpluses that never occur in a clean run.
Use gold injection in isolated tests. Buy, observe, reload, and repeat rather than letting the economy permanently adapt to an impossible player profile.
Item Spawning and Gear Validation
campaign.add_item [item_id] X allows you to spawn exact weapons, armor, or horses. This is essential for comparing crafted weapons, validating modded gear stats, or testing how armor weight affects stamina drain and movement.
Item IDs must be exact. If the item doesn’t exist or belongs to an unloaded module, the command silently fails. This is a common pitfall when testing mods with custom equipment.
Avoid equipping experimental items on companions you plan to keep. Bad data can persist in inventories and follow you across saves.
Troop Spawning and Formation Experiments
campaign.add_troops [troop_id] X adds units directly to your party. This is the fastest way to test unit performance, formation behavior, and morale breakpoints without grinding recruitment.
This command is invaluable for comparing similar units like Vlandian Sergeants versus Imperial Legionaries under identical conditions. Same terrain, same formation, same commander perks.
Overusing troop injection can confuse campaign balance. Lords evaluate your strength numerically, not tactically, so inflated parties can cause AI to avoid or dogpile you unnaturally.
Skill, Perk, and XP Manipulation
campaign.add_skill_xp_to_hero [skill] X lets you surgically level skills without triggering unrelated perks. This is the cleanest way to test perk interactions, especially ones tied to movement, morale, or party-wide buffs.
Some perks only activate after combat resolution or rest ticks. If something feels broken, it may simply not have refreshed yet. Enter a minor fight or pass time to force recalculation.
Avoid maxing every skill at once. Bannerlord’s progression systems assume specialization, and breaking that assumption can produce misleading results.
Map Control, Teleportation, and AI Observation
campaign.teleport_to_settlement [name] instantly moves your party across Calradia. This is ideal for observing faction wars, siege behavior, or regional economy differences without burning in-game weeks.
Teleporting skips travel-based events like ambushes, morale decay, and food consumption. If you’re testing logistics or attrition, this command invalidates the results.
Use teleportation to observe, not participate. Watching AI fight AI reveals far more about Bannerlord’s balance than jumping in with a god-tier character.
Hidden Cheats, Campaign Overrides, and Debug Risks
Some commands don’t announce their effects clearly. campaign.set_player_age, campaign.change_main_party_size_limit, and relationship overrides can permanently alter save data in ways that aren’t visible until much later.
Developer commands disable achievements outright. If Steam achievements matter to you, treat any cheat-enabled save as a sandbox-only file.
When modding, always assume the console is lying by omission. If something behaves strangely, it’s usually because multiple systems recalculated at once. Backups aren’t optional at this level; they’re part of the workflow.
Used correctly, these commands let you dissect Bannerlord down to its bones. Used carelessly, they turn Calradia into noise. The difference isn’t restraint, it’s intent.
Risks, Limitations, and Best Practices – Save Safety, Balance Impact, and Achievements
By this point, it should be clear that Bannerlord’s developer console is a scalpel, not a hammer. It gives you direct access to systems the game normally gates behind hours of RNG, attrition, and long-term decision-making. That power comes with consequences, especially once saves, balance, and progression systems start overlapping.
Understanding those limits is what separates productive testing from a campaign that quietly implodes 30 hours later.
Save Safety – Why Backups Are Non-Negotiable
Bannerlord saves are not sandboxed against console abuse. Many commands permanently rewrite values that the game never expects to change mid-campaign, such as age, party limits, clan tier math, or relationship thresholds. The save will load fine, but downstream systems may behave erratically weeks later.
Always duplicate your save before testing anything structural. Treat console experimentation like mod development: isolate it, label it clearly, and never assume you can “undo” a command cleanly.
If a command doesn’t immediately show visible effects, don’t spam it. Some systems recalculate on daily ticks, combat resolution, or settlement entry, and stacking changes can corrupt the logic rather than speed it up.
Balance Impact – When Testing Becomes Misinformation
Cheats fundamentally distort Bannerlord’s core feedback loops. Infinite gold erases economic pressure, instant skill XP bypasses perk trade-offs, and troop spawning ignores morale, cohesion, and recruitment friction. The result is data that feels useful but isn’t representative of real play.
This is especially dangerous when evaluating perks, weapons, or army compositions. A build that dominates with maxed skills and perfect gear may collapse under normal stamina, morale, and AI targeting conditions.
The best practice is constraint-based testing. Change one variable at a time, observe behavior, then reset or reload. Bannerlord’s combat and campaign layers are deeply interconnected, and breaking too many assumptions at once produces noise, not insight.
Achievements – What You Lose the Moment You Enable Cheats
Once the developer console is enabled, achievements are disabled for that save. This isn’t a soft warning or a toggle you can reverse later. The game flags the file permanently, even if you never enter another command.
If achievement hunting matters to you, keep a clean, console-free campaign separate from your testing sandbox. Mixing the two is the fastest way to burn a long-term run without realizing it until the endgame.
Mods don’t always trigger the same lockout, but console commands always do. When in doubt, assume achievements are gone and plan accordingly.
Best Practices – How Veterans Use the Console Without Breaking the Game
Use the console with intent, not convenience. Teleport to observe AI wars, don’t win them. Inject skill XP to test perk math, not to skip progression entirely. Spawn items to validate loadouts, then earn them properly if you plan to keep playing.
Document what you change. Even a simple note like “party size modified” can save hours of troubleshooting later when morale, wages, or food consumption start acting strange.
Most importantly, respect Bannerlord’s pacing. The game is designed around friction, downtime, and imperfect information. The console should clarify systems, not erase them.
Used wisely, console commands turn Mount & Blade II: Bannerlord into one of the most dissectible sandbox RPGs ever made. Used recklessly, they hollow out the very tension that makes Calradia worth conquering. The difference isn’t whether you cheat—it’s whether you’re learning something when you do.