Bannerlord AI NPC Mod: Talking Lords and Battle Voice Commands

Calradia is full of lords with opinions and tavern keepers with rumors, yet every conversation runs through the same short menu and a persuasion roll. A Bannerlord AI NPC mod changes that: you speak or type, the lord answers in character, remembers the war you started, and acts on what you agree. Neocortex gives your module the AI characters, Conversation Flows, quizzes and on-device voice commands to build it.

Screenshot: Mount & Blade II: Bannerlord © TaleWorlds Entertainment

What you could build with Neocortex in Bannerlord

Lords and tavern keepers who actually negotiate

Picture a tavern keeper in Pravend who knows which wanderers are drinking upstairs and haggles over the price of a rumor. Or a Khuzait noble who hears your offer to join his army, weighs it against his clan's grudges, and names a counter price.

Your module sends the facts that matter with each message: relations, the kingdom's current wars, the gold in your purse, your last battle. The character replies with text, an emotion tag for the face and tone, and actions your code runs, such as { "name": "JOIN_ARMY", "targetId": "lord_derthert" } or SHARE_RUMOR. The persuasion system stays the referee; the conversation just stops sounding like a menu.

Battlefield voice commands

Bannerlord already has a deep order system. Voice commands put it in your mouth instead of on the function keys. You design a command set with actors ("infantry", "archers", "cavalry", "everyone"), actions ("charge", "hold position", "follow", "advance", "fall back") and objects ("me", "that hill").

Say "cavalry charge" or "archers hold position" and the module receives a clean command it turns into the matching order. "Archers hold, cavalry charge" arrives as two commands. Matching happens on the player's PC, so the order lands while the charge still matters.

A peace negotiation as a Conversation Flow

An envoy scene works well as a Conversation Flow. The emissary steers the talk through checkpoints: greeting, terms stated, tribute agreed, then peace signed or talks collapsed. Each reply carries a flowState keyword, and your module reacts: on PEACE_SIGNED it runs the campaign's own peace action, on TALKS_COLLAPSED the war goes on and the envoy leaves angry.

A heraldry and history quiz

A herald in a town hall can run a quiz on banners, cultures and history: "Which culture fields Fian Champions?" or "Who rules Vlandia?" The quiz engine (Team plan) handles questions, scoring and a leaderboard, and your module pays out renown or a horse to the winner.

How Bannerlord modding works

Bannerlord mods are modules: a folder under Modules with a SubModule.xml and one or more C# assemblies. Your code runs in a submodule class that hooks the game's lifecycle, and because it is plain .NET, it can call a web API with HttpClient like any desktop app.

The community stack most mods build on, all actively maintained in October 2026:

• Harmony (GitHub) patches game methods at runtime, for example to route a conversation through your own code.
• BLSE (GitHub), the Bannerlord Software Extender, is the continuation of BUTRLoader with an extended launcher. It is required for the Xbox PC version and optional on Steam, GOG and Epic.
• ButterLib (GitHub) adds shared developer tools such as hotkeys, logging and save helpers.
• UIExtenderEx (GitHub) lets several mods change the standard UI without clashing, which is how you add a subtitle panel or a chat box.
• MCM (Mod Configuration Menu) gives your mod an in-game settings page, a good home for the player's API key and push-to-talk binding.

TaleWorlds ships the official Modding Kit on Steam with the scene and resource editors, documented at moddocs.bannerlord.com with an API reference. The community Bannerlord modding docs cover a first C# mod and Gauntlet, the XML and ViewModel UI system you use for subtitles. For voice playback, the module plays the returned audio through a .NET audio library you bundle with it.

Mount & Blade: Warband

Warband modules are written with the Python Module System, which compiles your scripts into the text files the engine loads. Many modern modules run on WSE2 (Warband Script Enhancer 2), an engine replacement that adds operations, triggers, performance work and bug fixes.

Module System scripts are not built for web requests or microphone input, so pair the module with a small companion app on the player's PC. The app talks to Neocortex and runs voice commands, then passes replies and matched commands to the module. How the two exchange messages depends on your setup, so check the WSE2 operation list for what your build supports.

Screenshot: Mount & Blade II: Bannerlord © TaleWorlds Entertainment

How Neocortex fits in

• Dialogue. The module reads campaign state, sends it to a Neocortex character through /v3/chat, shows the reply as subtitles in a Gauntlet panel, plays the voice from /v3/audio/generate or /v3/audio/stream, and runs the actions the character returns.
• Conversation Flows. Flows steer story beats such as the peace talks and return checkpoint keywords your module reacts to.
• Quizzes. The quiz engine runs the herald's question-and-answer game through /v3/quiz.
• Voice commands. The Neocortex Voice Commands library on the player's machine turns spoken orders into game actions without a cloud round trip.

Characters are built in a visual node editor with personality, emotion, knowledge, world and voice nodes, so you can feed a lord a text file of his family history and let him draw on it. Up to six characters can share one conversation on Pro and Team plans, which suits a war council in a lord's hall. If you are weighing options, our comparison page lays out how Neocortex differs from other AI character platforms.

Getting started

1. Set up the stack. Install Harmony, ButterLib, UIExtenderEx and MCM, add BLSE if your players use it, and build a basic C# module.
2. Design the cast in the Neocortex dashboard: a lord, a tavern keeper, an envoy flow and a heraldry question set. Test them in the browser first.
3. Design a battle command set for formations and orders, with a few example phrases per action.
4. Connect from the module. Call /v3/chat off the main thread, reuse the sessionId, and map returned actions to campaign code.
5. Keep the API key in a config file or MCM setting the player fills in, never hard-coded in a shared mod.
6. Test in a single-player campaign with push-to-talk before trying always-listening.

Voice Commands is a licensed SDK: contact us for a Voice Commands license.

Mod policy and fair play

Keep the mod to single-player campaigns and custom battles, free and non-commercial, and respect the TaleWorlds EULA and the rules of the site you publish on. Do not use voice or AI features in multiplayer against its rules. Each player uses their own Neocortex API key.

Want the bigger picture on speech control? Read our post on on-device voice commands for game mods, or browse the other game guides, from Skyrim to RimWorld, in our AI NPC and voice command mods index.

Tool versions and links checked October 2026. Modding tools change often; check each project's page for the latest release.

Frequently Asked Questions