AI INFLUENCE TUTORIALS

Get the mod from:

• Discord for all news: Discord
• Steam Workshop: Steam Link
• Nexus: Nexus Link

• Harmony
• ButterLib
• UIExtenderEx
• Mod Configuration Menu (MCM)

Bannerlord 1.3.9 - 1.3.13

https://player2.game/

Local server starts automatically at: http://localhost:4315/

MCM → AIInfluence → Settings:

• AI Backend: Player2
• URL: http://localhost:4315/
• API Key: leave empty ✅

MCM → AI Backend → Select provider → Enter API URL and Key if required

Tip: Better AI models = smarter characters

Go to platform.deepseek.com and create an account.

Add funds to your API account for usage.

Navigate to API Keys section and create a new API key.

In Bannerlord's MCM → AI Influence settings:

1. Select DeepSeek as AI backend
2. Enter your API key
3. Configure URL if required

• ✅ Correct Bannerlord version? (1.2.12 or 1.3.1)
• ✅ Dependencies installed? (Harmony, ButterLib, UIExtenderEx, MCM)
• ✅ Load order correct? (Dependencies ABOVE AIInfluence)
• ✅ Running without conflicting dialogue/diplomacy mods?
• ✅ Try new campaign

Check AI backend settings in MCM:

• ✔ AI Backend selected? (Player2, OpenRouter, etc.)
• ✔ URL correct? (e.g., http://localhost:4315/)
• ✔ Internet ON? (if using cloud AI)
• ✔ API Key entered correctly? (if required)

✅ Tip: Press "Test Connection" button in MCM!

• ⚠️ Too many initialized AI characters!
• MCM → Performance: Reduce AI character count (recommended: Around 100 active NPCs)
• ✅ Disable heavy mods that rewrite diplomacy or economy
• ✅ Restart Player2 / AI backend after long sessions

• ✅ Better management of situations with NPCs
• ✅ Clarify NPC misunderstandings
• ✅ Provide deeper immersion through extended replies
• ✅ Increase chances of persuading NPCs

Consider these factors before interacting:

• a) What do you want from the NPC?
• b) What is the NPC's status (merchant, lord, noble, etc.)?
• c) What approach matches your character?
• d) What environmental details are worth describing?

Situation: You want information from Korin, a merchant in Balgard.

Your Character: Wandering merchant/mercenary who served a Western Empire lord.

When NPCs don't believe your words, use asterisk actions to provide context:

Configure in MCM settings:

1. Set maximum characters to highest value
2. Set minimum response to at least 150 characters

• Use extended descriptions: "I walk slowly, the setting sun on horizon slowly reflects on my shining armor as I walk towards my soldiers"
• Express emotions: "I just slowly pass by, not even considering his presence, my eyes are little wet from crying"
• Act like a real person would!

This tutorial explains how to enable conversations with multiple NPCs simultaneously, a feature not natively supported by the mod but possible through custom configurations.

Works with every version of Bannerlord/Warsails. It explores AI possibilities and prompt engineering techniques.

Go to MCM settings in-game:

1. Set maximum AI response to 1000 characters
2. Set minimum AI response to 300 characters

Add the following rule to your world.txt file:

Gather NPCs in the same place (ideal for meetings). When speaking to the main NPC (settlement owner/meeting organizer), end your statement with:

⚠️ Important: Always name each NPC involved to maintain consistency.

Generating larger responses to complicated prompts can use more tokens from Player2. Report any bugs encountered while using the dual-conversation rule.

ChatSync is a submod for AI Influence that synchronizes conversations between selected NPCs. Once synced, characters share the same conversation context, making them aware of what has already been said and eliminating the need to repeat dialogue. This creates a true multi-NPC conversation experience instead of isolated one-on-one interactions.

Download: ChatSync on Nexus Mods

• Select multiple NPCs to sync conversations
• AutoSync mode to keep dialogue context shared
• NPC search for quick selection
• Easy in-game UI with intuitive hotkeys
• Ideal for companions, advisors, rulers, and role-play focused gameplay
• Universal path detection for all installation types

Hotkeys:

• F8 – Open/close ChatSync menu
• F9 – Toggle AutoSync ON/OFF instantly
• F10 - Show Diagnostics
• F11 - Manual Path Setup (if automatic detection fails)

1. Download ChatSync from Nexus Mods
2. Place the ChatSync folder in your Bannerlord Modules folder
3. Ensure it loads after AI Influence in your load order
4. Launch game and use F8 to open the ChatSync menu

ChatSync automatically searches for AI Influence in ALL possible locations:

• Steam Workshop installations (all drives and library folders)
• Different mod managers (Vortex, ModOrganizer2, manual installs)
• Custom installation paths on any drive (C:, D:, E:, etc.)
• Standard Bannerlord directories
• Windows user folders (Documents, AppData)

If you encounter "NPC not found" issues:

1. Press F10 to see diagnostics
2. Check if AI Influence mod is found
3. Press F11 to manually set the path if needed
4. Enter the full path to your AI Influence save_data folder

Player2's TTS system generates natural-sounding AI voices for every NPC in Bannerlord, replacing limited single-line voice acting with fully voiced dynamic conversations.

1. Step 1: Open Player2 and ensure the top-right corner slider is ON
2. Step 2: In Bannerlord → Mod Options → AI Influence → Scroll to Player2 Settings
3. Step 3: TTS is now enabled

AI does something undesirable (e.g., Raganvad spamming war declarations on his own faction).

Have a save from before the problematic events. If not, proceed cautiously.

Navigate to mod installation folder (Nexus manual download recommended):

Use the JSON editing tutorial to find the specific character file.

Look for these sections in the JSON file:

• "ConversationHistory"
• "LastDynamicResponse"
• "LastAIResponseJson"

Delete problematic sections from ConversationHistory. Leave it formatted with their last reply.

Copy the last line from ConversationHistory (without quotation marks or character name) and paste into "LastDynamicResponse" inside quotation marks.

Repeat for "LastAIResponseJSON" - paste in correct spot inside quotes.

Save the JSON file and reload your previous save game.

• "AIGeneratedBackstory" - NPC's AI-generated history
• "AIGeneratedPersonality" - NPC's personality traits
• NPC quirks and additional information

1. Open AI Influence folder
2. Use search bar to find specific NPC (e.g., "Baroness Kalatylda (lord_4_6)")
3. Multiple JSON files may appear (from different saves)
4. Open the newest file with Notepad

• ✅ NPC Quirks
• ✅ Personality
• ✅ Backstory
• ✅ Last Dynamic Response

Quick Method:

1. Recruit wanderer from inn using vanilla features
2. Initialize them via AI (even with minimal input)
3. Save game and exit Bannerlord
4. Search for companion's JSON file
5. Edit desired characteristics
6. Boot game and talk to companion referencing your edits

• • AI creates and reacts to world events
• • AI leaders make public statements
• • AI can declare war or propose peace
• • AI can form or break alliances

Statements affect relationships between kingdoms.

If you are a KING/QUEEN:

• • Make diplomatic statements through your governor
• • Declare war publicly
• • Offer or reject peace
• • Form or break alliances

Statements appear in BLUE on the campaign map 🌐

AI will evaluate your actions — not just accept them.

Only NPCs you have talked to are fully driven by AI. Others do not know recent events until first interaction.

Too many initialized AI NPCs will cause lag or freezes. Recommended active limit: around 100 NPCs.

The system is still being rewritten — bugs and unexpected behavior are possible. Developer actively updates based on community feedback.

NPCs in AIInfluence can perform various actions: travel across the map, follow the player, attack enemies, besiege settlements, etc.

Multi-tasking actions: An NPC can perform multiple actions in sequence in one chain. For example, a player can ask an NPC to "visit city A, then city B, attack bandits and return" - and the NPC will complete all these tasks sequentially. Actions are combined with commas, creating a chain of tasks.

The actionrules.txt file allows you to add additional instructions for the AI that will be automatically added to the prompt in the "ADDITIONAL RULES FOR ACTIONS" section. This helps adjust AI behavior if it incorrectly uses actions or does something differently than you need.

2.1. Movement & Basic Actions

• follow_player - NPC follows the player, accompanies them
• go_to_settlement - NPC travels to the specified settlement (city, castle, village)
• return_to_player - NPC returns to the player after completing a task
• attack_party - NPC attacks the specified party (bandits, deserters, enemies)
• patrol_settlement - NPC patrols around the specified settlement
• wait_near_settlement - NPC waits near a settlement without entering it
• siege_settlement - NPC besieges the specified city or castle
• raid_village - NPC raids the specified enemy village
• create_party - NPC creates their own party (leaves the player's party)

2.10. Multi-tasking actions (chains)

What it does: NPC can perform multiple actions in sequence in one chain

Examples of chains:

NPCs can combine actions with commas, creating a sequence of tasks that will be completed one after another.

• attack - NPC decides to attack the player
• surrender - NPC surrenders to the player
• accept_surrender - NPC accepts the player's surrender as a prisoner
• release - NPC releases the player peacefully (does not attack)
• propose_marriage - NPC proposes marriage to the player
• accept_marriage - NPC accepts the player's marriage proposal
• reject_marriage - NPC rejects a marriage proposal
• intimate - Intimate interaction with NPCs

• money_transfer - Money transfer between NPC and player

Important: Used only when the NPC AGREES to transfer money, not for offers or refusals.

• workshop_action (sell) - NPC sells their workshop to the player

Important: Used only after final price agreement, not during negotiations.

Available only to kingdom rulers and vassals in certain situations:

• declare_war - Declaration of war on another kingdom
• propose_peace / accept_peace / reject_peace - Peace proposal, acceptance or rejection
• propose_alliance / accept_alliance / reject_alliance / break_alliance - Alliance operations
• propose_trade_agreement / accept_trade_agreement / reject_trade_agreement / end_trade_agreement - Trade agreements
• demand_territory / transfer_territory - Demand or transfer of territory
• demand_tribute / accept_tribute / reject_tribute - Tribute operations
• demand_reparations / accept_reparations / reject_reparations - Reparations operations

• hire_mercenary - Hiring the player as a mercenary
• dismiss_mercenary - Dismissal of the player from mercenaries
• offer_vassalage - Offer to the player to become a vassal
• dismiss_vassal - Release of the player from vassalage
• join_player_clan - NPC joins the player's clan as a companion
• join_player_kingdom - NPC's clan joins the player's kingdom
• hire_mercenary_clan - NPC's clan accepts the player's offer to hire them as mercenaries
• kick_from_clan - NPC accepts the player's decision to dismiss them from the clan
• dismiss_npc_mercenary - NPC's clan accepts the player's decision to dismiss them from mercenaries
• release_npc_vassal - NPC's clan accepts the player's decision to release them from vassalage

Creating the file:

1. Find the AIInfluence mod folder (usually in `Modules/AIInfluence/`)
2. Create a text file named `actionrules.txt` in the root of the mod folder
3. Add your rules to this file (in English)

Rule format:

Rules are written in English in free form. They will be automatically added to the "ADDITIONAL RULES FOR ACTIONS" section of the AI prompt.

Rules should be written as instructions for the AI, explaining:

• When to use or NOT use certain actions
• What checks to perform before using actions
• How to consider NPC personality when making decisions
• Additional restrictions or conditions

Rule writing style:

• Use imperative form ("NPC should...", "Always verify...", "Never use...")
• Be specific and clear
• Specify specific actions and conditions
• Can reference NPC personality ("Consider personality when...")
• Can add example situations

Rules for information verification:

Rules for considering NPC personality:

Rules for preventing errors:

The actionrules.txt file is a powerful tool for configuring AI behavior when using actions. By adding custom rules, you can:

• Fix problems with incorrect action usage
• Add additional checks and restrictions
• Improve consideration of NPC personality when making decisions
• Customize AI behavior to your preferences

What: Calradia world description for the AI.

Why: The AI reads it on every dialogue for context.

How to edit:

• Add your lore in the section "Additional Information About Calradia:"
• Use `{Character}` and `{Player}` instead of specific names
• Write in English
• Save → the file will be hot‑reloaded automatically

What: Secret knowledge that NPCs may know.

Format:

How it works:

1. On first interaction, a 0–100 roll is made
2. If ≤ `knowledgeChance` → the NPC learns the secret
3. The secret is added to the prompt: `"Secrets: ... (access: high)"`
4. The AI decides whether to reveal it (depends on trust)

Fields:

• `id` — unique name
• `description` — full text (passed into the AI prompt)
• `knowledgeChance` — 0–100 chance that the NPC learns it on first contact
• `applicableNPCs` — types: `all`, `lords`, `companions`, `faction_leaders`, `village_notables`, `merchants`
• `accessLevel` — `low`, `medium`, `high` (shown in the prompt)
• `tags` — for organization (does not affect logic)

What: Public, non‑secret information.

Format:

Fields:

• `usageChance` — 0–100 chance (works like knowledgeChance)
• `applicableNPCs` — types: `all`, `lords`, `companions`, `faction_leaders`, `village_notables`, `merchants`
• `category` — `world` (persistent), `event` (temporary), `personal` (personal)

Differences from secrets:

• Field: `usageChance` vs `knowledgeChance`
• Classification: `category` vs `accessLevel`
• In the prompt: "General Info: ..." vs "Secrets: ... (access: high)"

What: Romantic traditions per culture.

Format:

Affects: Flirt style and relationship requirements.

Main fields:

You can also see service fields:

• `KnownSecretsUserEdited` / `KnownInfoUserEdited` — flags that knowledge was edited by the user (if `true`, the system will no longer change these arrays)
• `DynamicEvents` / `LastEventAnalysisMessageIndex` — which dynamic events the NPC knows and which messages were already sent for analysis
• `AIGeneratedPersonality` / `AIGeneratedBackstory` — auto‑generated personality and backstory description
• Romance fields (`RomanceLevel`, `LastRomanceInteractionDays`, `IsRomanceEligible`) and battle fields (`SettlementCombatInfo`) — managed only by the system

After changing `KnownSecrets` or `KnownInfo`:

The `UserEdited: true` flag → the system will not touch this field.

Resetting flags: MCM → NPC Management → Reset User‑Edited Knowledge

What: Active world events.

Important fields:

• `type` — `military`, `political`, `economic`, `social`, `mysterious`
• `importance` — 1–10 (how important)
• `kingdoms_involved` — array of kingdom `string_id`
• `allows_diplomatic_response` — whether rulers can make statements
• `expiration_campaign_days` — when it expires

Additionally, events have:

• `id` — unique event identifier (string, NPCs store knowledge about it in `DynamicEvents`)
• `player_involved` — whether the player participated
• `spread_speed` — how fast it spreads

NPC link: The list of NPCs who know about an event is stored in each `NPC (id).json` in the `DynamicEvents` array. `DynamicEventsManager` automatically updates these fields and removes expired events from NPCs.

What: Kingdom rulers' statements.

Structure:

Storage: Last 15 statements over 50 in‑game days.

Editing: Not needed (automatic system).

All files below are in `save_data/[CAMPAIGN_ID]/` and are managed automatically by the diplomacy system.

• `diplomatic_events.json` — active diplomatic events linked to dynamic events (`DynamicEvents`)
• `pending_player_statements.json` — deferred player statements to be published later
• `trade_agreements.json` — current trade agreements between kingdoms
• `territory_transfers.json` — history of fief transfers between kingdoms
• `tributes.json` — tribute payment agreements
• `reparations.json` — reparations data (history and open claims)

`logs/mod_log.txt` — main log

• Mod initialization
• Config loading
• AI prompts and responses
• API errors

Check when: NPC does not respond, Secrets are not loaded, In‑game errors occur

`logs/diplomacy.txt` — diplomacy

• Diplomacy system initialization
• Creation of diplomatic situations and statements
• Analysis of diplomatic events (full prompts and AI responses)
• Executing actions (wars, peace, alliances, relation changes)
• Diplomacy system errors and warnings

`logs/dynamicEvents.log` — dynamic events

• Event generation (including full prompt and AI response with detailed debugging on)
• Event propagation to NPCs (who learned what and why)
• Deletion of expired events and cleanup of NPC knowledge

JSON files

• ✅ Always validate JSON (jsonlint.com)
• ✅ Make backups before editing
• ✅ Do not delete required fields
• ❌ Do not edit `dynamic_events.json` and `diplomatic_statements.json` unless necessary

Secrets vs Info

• `world_secrets.json` → field `knowledgeChance`
• `world_info.json` → field `usageChance`
• DO NOT CONFUSE THEM! Otherwise the value will be treated as 0.

Hot Reload

These files are hot‑reloaded automatically:

• ✅ `world.txt`
• ✅ `world_secrets.json`
• ✅ `world_info.json`
• ✅ `cultural_traditions.json`

NPC files are reloaded on the next interaction.

Edit Flags

If you edit `KnownSecrets` or `KnownInfo`:

• The `UserEdited` flag automatically becomes `true`
• The system will no longer touch these fields
• Reset: MCM → Reset User‑Edited Knowledge

Adding new content

1. Come up with an idea (secret, event, quest)
2. Add it to JSON (`world_secrets.json` or `world_info.json`)
3. Save the file → hot‑reload
4. Create new NPCs or reset existing ones
5. Start a dialogue → the AI will know about the new content

Testing secrets

1. Add a secret with `knowledgeChance: 100`
2. Create a new NPC or reset an existing one
3. Start a dialogue
4. Check the log: `[NPC] Name learned secret: ...`
5. Ask the NPC about the secret directly

Debugging events

1. Enable detailed logging (MCM)
2. Create an event (Force Generate Event)
3. Check `logs/dynamicEvents.log`
4. See who received the event and why