This guide covers admin setup, player management, server console commands, map rotation management, game mode switching, modding support, and troubleshooting for your Mount & Blade II: Bannerlord dedicated server. For initial server setup, game mode configuration, map selection, faction settings, and connection instructions, see Mount and Blade II Bannerlord Server Setup Guide.

1. Admin Setup

Setting the Admin Password

The admin password is set via the ADMIN_PASSWORD startup variable in GPanel, or in the config file using the AdminPassword command:

AdminPassword YourAdminPassword

This password is required for both the web admin interface and in-game admin access.

Accessing the Web Admin Panel

Bannerlord includes a built-in web admin panel powered by the DedicatedCustomServerHelper module.

1. Find your server's IP address and port in GPanel's Network tab.
2. Open a web browser and navigate to:

   http://<your-server-ip>:<port>

   The web panel runs on the same port as the game server (default UDP 7210). Check your GPanel Network tab for the exact port.

3. Enter your admin password when prompted.

In-Game Admin Access

1. Join your server as a normal player.
2. Open the game console with Alt + ~ (tilde key).
3. Type Help to see available commands.
4. You may need to authenticate with the admin password through the in-game admin menu if prompted.

2. Server Console Commands

The following commands can be used in the server console (GPanel console) or the web admin panel. Type Help or list in the console to see all available commands.

Server Management Commands

3. Player Management

Kicking Players

To remove a player from the server:

• Web Admin: Navigate to the Players section in the web admin panel, find the player, and click Kick.
• Chat command: Open the in-game chat and type:

  !kick <playername>

Kicked players can rejoin immediately unless you also ban them or set a server password.

Banning Players

To permanently prevent a player from joining:

• Web Admin: Use the ban option in the Players section of the web admin panel.
• Chat command: Open the in-game chat and type:

  !ban <playername>

Bans persist across server restarts.

Unbanning Players

To remove a ban and allow a player to rejoin:

!unban <playername>

Muting Players

To prevent a player from using the in-game chat:

• Use the mute option in the web admin panel.
• Muted players can still play but cannot send chat messages.

4. Map Rotation Management

Changing the Current Map

To change the map during gameplay, use the web admin panel or modify the config file and restart the server. Maps must match the current game mode.

Editing the Map Rotation

The map rotation is defined in your game mode config file. To change it:

1. Stop the server from GPanel.
2. Open the config file (e.g., Modules/Native/siege_config.txt).
3. Modify the add_map_to_automated_battle_pool lines to add or remove maps.
4. Ensure enable_automated_battle_switching is present if you want automatic rotation.
5. Save and restart the server.

Single Map Mode

To run a single map without rotation, include only one add_map_to_automated_battle_pool line and omit enable_automated_battle_switching. The same map will replay each round.

5. Game Mode Switching

Changing the game mode requires updating both the GameType setting and the map pool, since maps are mode-specific.

1. Stop the server from GPanel.
2. Open the config file and change the GameType line:

   GameType Siege

3. Replace the add_map_to_automated_battle_pool lines with maps compatible with the new mode. See the Setup Guide for map lists.
4. Save the file and start the server.

6. Modding Support

Bannerlord supports custom modules (mods) on dedicated servers. Mods can add new maps, game modes, weapons, troop types, and gameplay mechanics.

Installing Mods

1. Stop the server from GPanel.
2. Connect to your server via SFTP. See How to Upload Files via SFTP for instructions.
3. Navigate to the Modules/ directory.
4. Upload the mod folder into Modules/. Each mod should be in its own directory with a SubModule.xml file.
5. Update the server's startup command or batch file to include the mod in the modules list. The _MODULES_ parameter in the startup configuration must reference all active modules:

   Native*Multiplayer*DedicatedCustomServerHelper*YourModName

   Modules are separated by asterisks (*). The load order matters -- place dependent mods after their prerequisites.

6. Start the server.

Steam Workshop Mods

Bannerlord supports Steam Workshop for mod distribution. To install Workshop mods on a dedicated server:

1. Subscribe to the mod on Steam Workshop from a regular Bannerlord installation.
2. Locate the downloaded mod folder in your local Bannerlord installation's Modules/ directory.
3. Upload the mod folder to your dedicated server's Modules/ directory via SFTP.
4. Add the module name to the startup modules list.

DedicatedCustomServerHelper Module

This built-in module provides the web admin panel. It must always be included in the modules list. If you encounter version mismatch errors after a game update:

1. Stop the server.
2. Navigate to Modules/DedicatedCustomServerHelper/.
3. Open SubModule.xml.
4. Update the Version value to match the current game version.
5. Update any DependedModule version values accordingly.
6. Save and restart the server.

7. Troubleshooting

Server Crashes on Startup

• Check the console output for error messages. Common causes include:
  • Missing or expired authentication token -- contact support if you see token errors.
  • Invalid AdminPassword configuration -- ensure the AdminPassword line exists and has a value.
  • Malformed config file syntax -- each command must be on its own line with no trailing characters.
  • Module version mismatch after a game update -- update SubModule.xml version numbers.
• Try removing all custom mods and running with only the default modules (Native*Multiplayer*DedicatedCustomServerHelper).
• Delete the config file and let the server regenerate defaults to rule out config issues.

Players Cannot Connect

• Verify the server is running in GPanel.
• Confirm the player is using the correct IP and port from the GPanel Network tab.
• Check that the game password is correct (case-sensitive).
• Ensure the player has the same game version and mods installed.
• If using mods, verify the player has the exact same module versions.
• Check the console for "player rejected" messages which may indicate the specific reason.

Server Not Appearing in Browser

• Confirm the server has fully started and the console shows it is accepting connections.
• Check that the config file includes start_game or start_game_and_mission -- without this, the server will not register with the master server list.
• The server browser may take several minutes to update. Try direct connect while waiting.
• If the authentication token is expired, the server may start but not appear in the browser. Contact support for token renewal.

Mod Conflicts

• If the server crashes after adding a mod, remove it and test again to confirm it is the cause.
• Check that the mod's SubModule.xml lists correct dependencies and the load order in your modules list is correct.
• Verify the mod is compatible with the current version of Bannerlord. Mods from older versions may cause crashes.
• Some mods conflict with each other. Check the mod documentation and community forums for known incompatibilities.
• Clear the server's shader cache and temp files if you experience graphical issues or loading errors after mod changes.

Player Desync

• Desync occurs when a player's game state diverges from the server. Symptoms include players appearing to teleport, hits not registering, or rubber-banding.
• The most common cause is high latency. Encourage affected players to check their internet connection.
• Mods that modify gameplay mechanics (movement speed, physics, weapon stats) are more likely to cause desync.
• If desync is widespread, try reducing MaxNumberOfPlayers or switching to a lighter game mode (Duel or Skirmish instead of Siege).
• Restarting the server can resolve persistent desync issues.

Authentication Token Issues

• Bannerlord requires a valid authentication token to run a dedicated server. Tokens expire after approximately 3 months.
• If you see token-related errors in the console, the token likely needs renewal.
• Open a support ticket to have your server's authentication token refreshed.

8. Log Files

Bannerlord server logs are useful for diagnosing crashes, connection issues, and player activity.

• Log files are stored in the server's log directory, typically accessible through GPanel's Files tab or via SFTP.
• Check log files for detailed error messages when the console output alone is not sufficient.
• Include relevant log excerpts when opening a support ticket for faster resolution.

Related Articles

• Mount and Blade II Bannerlord Server Setup Guide
• How to Find Your Server IP and Port
• How to Upload Files via SFTP
• Server Startup Guide

Need Help?

If you run into issues with your Bannerlord server that are not covered here, open a support ticket and include your server IP, the game mode you are running, any mods installed, and relevant error messages from the GPanel console or log files.