Bannerlord Dedicated Server Troubleshooting

Common Bannerlord Server Issues

1. Server Does Not Appear in Server Browser

• Cause: Server token expired (TaleWorlds tokens expire every 90 days), or start_game was not dispatched.
• Resolution:
  1. Generate a new server token in the Bannerlord PC client.
  2. Update AUTH_TOKEN in DustBowl Warden Startup Parameters.
  3. Confirm start_game_and_mission is executed in the console.

2. Map Load Crash on Match Start

• Cause: Mismatch between GameType and the selected map in default.txt.
• Resolution: Confirm your starting map is designed for the active game mode (e.g., only siege maps with GameType Siege).

3. Out of Memory Crash (Exit Code 137)

• Cause: Container exceeded allocated RAM quota during high-player siege battles.
• Resolution: Increase container RAM limit in DustBowl Warden to at least 8 to 12 GB.

4. Connection Timeouts or Port Conflicts

• Cause: Primary game port 7210 (UDP/TCP) or Steam query port 27015 is blocked by firewall rules or conflicting allocations.
• Resolution: Verify assigned ports in the Warden Network tab, and confirm the containerized Wine prefix initialized without socket binding failures.

5. Persistent Engine Crashes or Corrupt Module State

• Cause: Incompatible custom module assemblies or corrupted binary states.
• Resolution: Open the Snapshots tab in DustBowl Warden, select your latest known-good snapshot, and click Restore to revert container state cleanly.

Useful Interactive Tools

• Test connection parameters with the Direct Connect URL Generator.
• Verify remote administrative ports with the RCON Command & Configuration Helper.