Bannerlord cheats: console commands and mods explained

Bannerlord cheats: what players actually mean, and what developers can learn from them

Mount & Blade II: Bannerlord has lived through years of Early Access, a full release, and a long tail of community module work, so the phrase “bannerlord cheats” pulls in three very different audiences. Some players want a quick console command to add gold, heal troops, or skip a siege. Some players want a trainer, a save editor, or an in-game cheat menu because they would rather test a campaign than grind through one. A smaller but more interesting group wants to understand how bannerlord cheats work under the hood, because TaleWorlds exposes a developer console and a full C# module system that modders use to build entire gameplay overhauls. This article focuses on that third group, while still being useful to the first two. If you have ever typed a command into Bannerlord’s developer console, installed a module from Nexus, or wondered why some “cheats” survive in the base game while others only exist in mods, the rest of the page is written for you.

Before going further, a few caveats. Using console commands or external trainers in Bannerlord disables achievements on most platforms, and multiplayer rules are stricter than single-player rules. None of the techniques below are guaranteed to be present in any given build, and TaleWorlds can change or remove debug commands between patches. Treat the descriptions as a map of the system, not a fixed script.

What counts as a “cheat” in Bannerlord

Bannerlord is unusually generous with debug exposure compared to most single-player RPGs, which is why the bannerlord cheats ecosystem is so wide. The categories players usually mean when they search for bannerlord cheats are:

Developer console commands: typed into the in-game console, which is the same surface TaleWorlds developers use internally for testing.
Debug build flags: command-line arguments that change how the game loads, useful for performance testing and module development.
Module mods: C# assemblies and XML data loaded by the Module System, often hosted on the Steam Workshop or Nexus Mods.
Save editors and external trainers: third-party tools that read or write campaign save files or attach to the game process.

Each category interacts with the game’s anti-cheat, achievement, and stability guarantees differently. Module mods, for example, are an officially supported extension point, while a save editor is a community tool that has to reverse-engineer file formats. Understanding which category you are using is more important than memorizing specific commands.

Opening the Bannerlord developer console

The most common entry point for bannerlord cheats is the in-game developer console. It is not advertised on the main menu, but it is a real subsystem, not a rumor. To open it, launch Bannerlord and on the main menu press Alt + ` (tilde) on most Western keyboard layouts, or Alt + ½ on some European layouts. The console appears as a thin bar at the bottom of the screen and accepts text commands. The exact key combination has changed during the Early Access cycle, so if it does not work, check the bindings file for your layout in the install directory.

Once open, the console behaves like a standard developer REPL. You type a command, press Enter, and the game executes it on the main thread. Errors print to the same bar, and most commands are case-insensitive. Console access is the foundation that the rest of bannerlord cheats sit on, because many of them are just thin wrappers around the same internal methods.

What the console is actually doing

Internally, the console is a debug layer over the engine’s scripting and gameplay assemblies. When you type a command, Bannerlord resolves it against a registered command table and routes the call to a method decorated for debug use. That is why a command might exist in one patch and vanish in the next: it is not a feature marketed to players, it is a debug surface that happens to be accessible. For developers, this is the most useful framing: bannerlord cheats are the same commands the QA team uses to set up repeatable tests.

Bannerlord cheats that work in single-player campaigns

Single-player is where console-based bannerlord cheats are most reliable, because the only enforcement layer is the achievement system. The following list covers the most widely reported commands. None of them are official, all of them are subject to change, and you should test them in a throwaway save before trusting them in a long campaign.

campaign.add_gold_to_hero [amount]: adds the listed amount of gold to your main hero. Useful for testing economy balance without grinding.
campaign.add_renown_to_clan [amount]: grants clan renown, which influences voting weight in kingdom politics.
campaign.add_influence [amount]: adds influence, the soft currency used for kingdom decisions, fief policies, and clan parties.
campaign.add_skill_xp_to_hero [skill] [amount]: grants XP to a named skill. The skill identifier has to match the internal enum, not the localized display name.
campaign.add_troops_to_hero_party [troop_id] [count]: spawns a stack of a troop into the player’s party. The troop ID comes from the culture’s troop XML.
campaign.kill_hero [hero_name]: removes an NPC hero. Useful for stress-testing how the campaign reacts to a missing lord.
campaign.set_main_hero_age [age]: changes the main hero’s age, which affects skill gain rates and marriage eligibility.

The pattern is consistent. Each command targets a campaign entity, takes one or two parameters, and writes directly to the campaign state. From a developer perspective, this is the cleanest category of bannerlord cheats because it does not require touching save files or external tools.

How to find the right parameter values

Most console commands accept string identifiers, not magic numbers. The identifiers live in the game’s data files, primarily under ModuleData in the install directory. For example, troop IDs are defined in culture-specific XML files such as empire_troops.xml, and skill IDs are defined in skills.xml. If a command silently fails, the most common reason is a typo in the identifier or a missing localization entry for your language. A useful debugging habit is to enable the in-game logger and watch for “could not resolve” messages when a command runs.

Battle and AI debugging commands

Campaign cheats are only half of the picture. Bannerlord also exposes a set of battle and AI debug commands that are interesting from a development standpoint because they let you isolate specific systems without rewriting a scenario. Common examples include:

config.dump_ai_state: writes the current AI state machine to the log, useful for understanding why a formation is stalling.
config.slow_motion_battle [0/1]: toggles slow-motion mode during a battle, helpful for capturing motion data or analyzing morale swings.
config.enable_formation_debug: draws formation markers on screen and prints tick-level updates to the log.
config.set_ai_aggressiveness [0-10]: shifts the AI’s tendency to charge, hold, or skirmish, which is useful for balancing custom troops.

These commands are not framed as bannerlord cheats in the marketing sense, but they are the commands a designer would use to validate a new troop or a new formation rule. If you are working on a balance mod, learning this set saves hours of manual playtesting.

Debug build flags and command-line arguments

Beyond the in-game console, Bannerlord also accepts a list of command-line arguments and engine configuration flags. These are entered on the game’s launch options in Steam, in a desktop shortcut, or in a development launcher. They are the second pillar of bannerlord cheats and the one most modders care about. Examples include:

-debug: forces the game to start with the developer console and the full debug overlay enabled.
-benchmark: runs the built-in scene benchmark instead of the main menu, useful for measuring performance changes between patches.
-modular: tells the engine to load modules from a custom path, which is how module developers point the game at their source tree.
-noIntro: skips the intro videos, which is a small time saver when iterating on a build.
-skipToBattle: jumps straight into a configured battle scene, often used by AI testers.

Command-line arguments are how you can reproduce a specific state on demand. For example, a tester who wants to validate a siege AI patch might launch the game with a combination of -debug, a custom module path, and a save file flag that drops the player at a known siege setup. That reproducibility is the same property professional QA uses, and it is the reason these flags are part of any serious bannerlord cheats workflow. Readers who want more background on Charles Banner, Baron Banner can use the Charles Banner Baron Banner while reviewing this point.

Where configuration actually lives

Many of the values these flags touch are also exposed in the engine_config.txt and game_config.txt files in the install directory. Those files are plain text and can be edited, which is technically a form of bannerlord cheats in its own right. Changing the campaign difficulty, the AI behavior weight, or the trade penalty values through config is slower than a console command but more durable, because the values survive across patches unless TaleWorlds renames the keys.

Module mods: the supported “cheat” layer

Module mods deserve their own section because they are the only category of bannerlord cheats that TaleWorlds actively supports. The Module System is a C# and XML framework that lets external code load into the game as a separate assembly, with its own data, its own UI hooks, and its own campaign behavior. Bannerlord loads modules at startup based on the contents of the Modules folder and the SubModule.xml declaration.

From a player’s perspective, a module is just something you tick on the launcher. From a developer’s perspective, a module is a full extension point. Common cheat-flavored modules include:

Recruit-troop-anywhere modules that remove the culture and roster restrictions on party composition.
Auto-resolve tuning modules that adjust the casualty model used in simulated battles.
Marriage and age modules that lift the restrictions on player marriages and heirs.
Economy rebalance modules that change town prosperity, tax yield, and caravan profit.
Developer overlays that draw debug text on top of the campaign map.

What makes modules interesting is the asymmetry between what they can change and what the console can change. The console can write values; modules can change the rules. A console command can add gold, but only a module can change the price curve that determines how much gold a caravan pays. That is why many bannerlord cheats you find online are actually small modules rather than console commands.

Anatomy of a simple cheat module

Even a tiny module illustrates the architecture. A module folder contains a SubModule.xml file that declares metadata, a C# project that compiles to a DLL, and a bin folder where Bannerlord loads the compiled output. The SubModule class overrides lifecycle hooks such as OnSubModuleLoad and OnGameInitializationFinished, which let the module patch behavior when the campaign starts. A cheat module typically patches a behavior, such as the price model, by injecting a Harmony-style postfix or by overriding a campaign behavior class. The compiled DLL ends up in bin, the XML data ends up in ModuleData, and the launcher picks the module up on next start.

If you have ever wondered why some bannerlord cheats are 5 MB and others are 50 MB, the size difference usually comes down to whether the author replaced a few data files or rebuilt a whole gameplay subsystem in C#.

Save editors and external trainers

Outside the official surfaces, the bannerlord cheats ecosystem includes tools that operate on the save file itself. Bannerlord saves are compressed archives of XML and binary data, and several community tools can unpack them, edit known fields, and repack the result. Editors in this category typically expose hero stats, party composition, inventory, and skill XP, because those are the fields players most often want to adjust.

External trainers attach to the running game process and write to memory addresses that match known debug symbols. They are convenient but fragile: any patch that changes the memory layout of a class can break a trainer overnight. From a developer standpoint, save editors are interesting because they are essentially an unofficial public schema for the campaign state. If a field appears in a save editor, you can be confident it is serialized to disk; if it does not, it is probably held in transient memory only.

Both categories share a risk profile. They can corrupt saves, they can introduce state that the campaign engine does not expect, and they can interact badly with modules. The safest practice is the same as with any bannerlord cheats: keep a clean backup of the save before editing, and validate the result in a short play session before trusting the edited save.

How bannerlord cheats interact with achievements and multiplayer

Bannerlord’s enforcement layers are not uniform. The achievement system flags any save that has been touched by a known cheat signal, and the flag sticks to the save, not the player. The multiplayer mode uses a server-authoritative model, so the category of bannerlord cheats that exists in single-player does not transfer; you cannot open the developer console in an official multiplayer match, and you cannot load most modules there. The server validates state and rejects clients that try to send out-of-range values, which is why the cheating scene in Bannerlord multiplayer is much smaller than in comparable open-world RPGs.

For developers, the lesson is structural. The campaign is mostly client-authoritative for single-player state, which is why a console command works at all, while the multiplayer layer is server-authoritative, which is why a console command does not. That difference is the same architecture choice you would make for a single-player RPG versus a competitive online mode, and Bannerlord is a useful case study in how the boundary is enforced through code rather than through policy.

Trade-offs: when bannerlord cheats help, and when they break your playthrough

Cheats in Bannerlord are not just a quality-of-life feature. They are a workflow. The honest trade-off is between speed of testing and depth of experience. The following table summarizes the most common use cases and their trade-offs. For an independent view of lord banner kc, the lord banner kc adds source-specific context to this discussion.

Use case	Best tool	What you gain	What you risk
Test a new troop mod in combat	Battle debug flags + `campaign.add_troops_to_hero_party`	Skip recruitment grind, isolate troop behavior	Miss economy effects that only show at scale
Reproduce a siege AI bug	Debug build flags + save editor	Deterministic setup for screenshots or logs	Save can desync from cloud if you back it up mid-siege
Replay the campaign with a new module loaded	Module mod with a save-edit prelude	Cleaner state for the new rules to apply	Some modules assume a fresh campaign
Skip early-game economy for a roleplay run	Console `campaign.add_gold_to_hero`	Faster entry into mid-game	Removes the pressure the rest of the system assumes
Validate a balance change across many saves	Config-file edits and `-benchmark`	Repeatable measurements	Edits can be overwritten by patches
Stream or record a curated moment	Slow-motion battle flag + debug formation overlay	Better camera and explanation value	Visuals look artificial in long clips

Read the table as a decision aid rather than a recommendation. If your goal is to test systems, bannerlord cheats are a force multiplier. If your goal is to enjoy a long campaign, leaning on them too early tends to flatten the difficulty curve the game was tuned around.

How to build a small bannerlord cheats workflow as a developer

If you are a developer working on a Bannerlord mod, a content pack, or a related project, the practical workflow looks like this. The steps are ordered, because each one depends on the previous one being stable.

Set up a clean source tree. Clone the module SDK and the mod you are working on into separate folders, and keep the SDK pinned to a known good version.
Wire a debug launcher. Add a Steam launch option that points Bannerlord at your module folder, enables -debug, and disables intro videos.
Pick a small repeatable test. Define one campaign state, one battle scenario, or one quest trigger that you can return to in under five minutes.
Write a console macro for the test. Use the console to drive your character into the test state, and store the commands in a text file so you can paste them back in.
Log everything. Enable verbose logging for the systems you are touching, and keep a copy of the log per run.
Diff saves, not screens. Save before and after the change, then diff the unpacked save XML. That is where the most useful signal lives.
Revert and rerun. If a change is not in a clean revertible state, do not trust the result. Bannerlord’s state can hide regressions for many in-game hours.

This loop is the same loop you would use in any other Unity or Unreal project that exposes a developer console. The Bannerlord-specific part is the module layering, which is where most of the time goes. Once the loop is stable, bannerlord cheats stop feeling like cheating and start feeling like the QA toolchain they actually are.

A short field guide to identifiers you will need

Most console commands fail not because the command is wrong but because the identifier is. The identifiers below are the ones you will use most often, drawn from the publicly distributed module data.

Entity	Identifier source	Example	Common mistake
Troop	Culture XML in `ModuleData`	`imperial_legionary`	Using the display name instead of the string ID
Skill	`skills.xml`	`OneHanded`, `Tactics`	Localizing the skill name before lookup
Item	`ItemModifiers` XML	`iron_sword_t3`	Confusing item ID with item modifier ID
Hero	Spawn data XML	`main_hero`, `lord_empire_1`	Typing the hero’s given name instead of the system name
Settlement	Settlement XML	`town_empire_1`	Using the player-visible settlement name
Faction	Factions XML	`empire`, `aserai`	Mixing culture and faction keys

When a console command fails silently, the most productive next step is to open the relevant XML and confirm the string you typed actually exists. The data files are forgiving, but the console is not.

Common failure modes when using bannerlord cheats

Most of the time, when a bannerlord cheats workflow does not work, the cause is one of a small set of predictable issues. The list below is short on purpose. These are the failures worth memorizing.

Wrong input layer. The console is open, but the game is reading keystrokes from the battle UI. Click the campaign map first, then retype.
Stale module cache. A module update is on disk, but Bannerlord is still loading the cached compiled output. Clear the bin folder and restart.
Out-of-range value. Some commands clamp the input. Adding ten million gold might be silently capped to a much smaller number.
Achievement flag on a save. Once a save has been flagged for cheat use, that flag usually sticks, and a new save is the only way to clear it.
Patch drift. A command worked last month and does not work today. This is the most common cause and the one to check first after a Bannerlord update.

Each of these has a known mitigation, which is why experienced modders keep a small cheat checklist pinned next to their launcher. If you are new to bannerlord cheats, build that checklist early; it pays for itself the first time a patch breaks your setup.

Ethics, terms of service, and the unofficial nature of bannerlord cheats

It is worth being explicit about the boundary. Single-player campaign cheats, console commands, debug flags, and most module mods are tolerated because they do not affect other players and they tend to extend, rather than break, the game’s lifespan. Multiplayer cheats, memory trainers that affect other players’ clients, and commercial resale of modded content sit in a different category and can fall foul of the terms you agreed to when you installed the game.

A practical rule of thumb: if your bannerlord cheats use is something you would do in a private sandbox, you are in the safe zone. If it is something that changes the experience for another player who did not opt in, you are not. That is the line the developers draw, and the line most mod communities draw as well.

Where bannerlord cheats intersect with mod development

The most useful framing for this whole topic is that bannerlord cheats and mod development are the same activity seen from different angles. A player types campaign.add_gold_to_hero and gets more gold. A developer reads the source of that command, sees the underlying method, and realizes they can hook a Harmony postfix to it so a module modifies the value automatically. The console is the surface, the module is the engine, and the cheat is the visible result.

For studios or learners who want to use Bannerlord as a case study, the cleanest way to enter is to take an existing bannerlord cheats workflow, trace it back to the engine code that supports it, and then write a small module that exposes the same surface through a UI button instead of a console line. That single exercise covers a surprising amount of gameplay engineering: input handling, state serialization, mod lifecycle, and player-facing UX. It is also a more honest answer to the question “what are bannerlord cheats” than any list of commands, because it shows that the cheats are not a back door. They are the front door that the game leaves open for builders.

Closing notes for developers and curious players

Bannerlord cheats will keep evolving as long as the Module System does, because the same surface that lets modders add a new troop tree also lets a player add gold. The list of working commands is less important than the model: a console that exposes campaign state, a config layer that exposes engine state, and a module layer that exposes behavior. Once you can read the model, the individual commands stop mattering, and you can answer most questions on your own by looking at the data files and the assembly list.

If you are a player, treat bannerlord cheats as a tool with a clear purpose: testing a campaign, recovering from a bug, or exploring a system you would not otherwise see. If you are a developer, treat them as a window into a system that was designed to be extended, even when the marketing page does not say so. Either way, the work is more interesting when you know what the command is actually doing, and that is the framing this article is built around.

Frequently asked questions

Are bannerlord cheats allowed by the developers?

Bannerlord does not ban single-player cheats, and the developer console is a real subsystem. What the game does is flag any save that has been touched by a cheat signal, which disables achievements on that save. Multiplayer is enforced more strictly and does not accept most cheat categories. As long as you stay in single-player, you are operating in the space the developers left open, but you should still check the latest terms of service for any change.

How do I open the developer console in Bannerlord?

On most keyboard layouts, press Alt + ` (tilde) on the main menu or in the campaign. Some European layouts use Alt + ½ instead. If neither works, open the engine configuration file and check the bound key. The console behaves like a standard REPL: type a command, press Enter, and read the result in the same bar.

Do bannerlord cheats work in multiplayer?

No, the multiplayer mode is server-authoritative and does not expose the developer console. The server validates the state it receives from each client, so most single-player cheats do not transfer. External trainers and memory editors that try to interfere with other players’ clients are treated more seriously than single-player cheats and can lead to bans or to broken matches.

Will using bannerlord cheats corrupt my save?

Cheats can corrupt saves if you write invalid values, edit the wrong field, or apply a cheat mid-event. The simplest mitigation is to back up the save before any cheat run, and to avoid running console commands during sieges, battles, or quest transitions, where the campaign state is most fragile. Module mods that change the rules are usually safer than save editors because the changes happen at load time, not mid-session.

Why did my favorite bannerlord cheats stop working after a patch?

Console commands, config keys, and even module hooks can change between patches because the underlying method names and data structures can be renamed or removed. After a Bannerlord update, the first thing to check is the patch notes, and the second is the mod page where you got the cheat from. If a command has been renamed, the old syntax silently fails rather than throwing a useful error.

Can I use bannerlord cheats on a console version of the game?

Console versions of Bannerlord are a different product and do not expose the developer console. Trainer and save-editor tools that target the PC version do not work on consoles, and the closed platform makes it harder to load modules. If you are on console, the only supported ways to change the experience are the official difficulty settings, the accessibility options, and any official updates TaleWorlds ships for that platform.

Are bannerlord cheats the same as mods?

They overlap but they are not the same. Cheats are usually short actions that change a value, like adding gold or unlocking a perk. Mods are usually sustained projects that change a system, like a reworked economy or a new troop tree. The interesting part is that many mods include a built-in “cheat” mode, and many cheats are stripped-down versions of a mod author’s full module. The two communities share most of the same toolchain.

Where can I learn more about the technical side of bannerlord cheats?

For a deeper look at how developer consoles and debug layers are designed in general, the Charles Banner, Baron Banner entry on Wikipedia is a useful reference for the history of named consoles in software. For a practical look at how legal and procedural boundaries are drawn around debug systems, the lord banner kc profile at Keating Chambers is a useful case study on how professional service work treats borderline developer tooling. Beyond those references, the Bannerlord modding Discord, the Nexus modding wiki, and the official TaleWorlds module documentation are the most reliable technical resources.

Bannerlord cheats: a developer-side look at console commands and mods