Mount & Blade: Warband Server Hosting

With SurvivalServers

Hosting your Warband server with us is effortless:

• Click Order Now above
• Enter a Username, Password and Email Address or sign up with Google/Twitch
• Select your slot amount, datacenter, and billing cycle
• Click "Order Now" and your Warband server is provisioned automatically, online in minutes with full control panel access

Without SurvivalServers

Running a Warband dedicated server yourself takes quite a bit more setup:

System Requirements

• Windows. Warband ships a standalone dedicated server executable that runs without the game client
• Around 220MB of disk for the server itself, plus room for whatever modules you install — a big one like Persistent World runs to a gigabyte or more
• About 1GB of memory up to 16 slots and 2GB out to 64. The server is single threaded, so a fast core matters more than a lot of them
• A machine you are willing to leave running whenever your regiment or community wants to play
• One port per server, forwarded on both TCP and UDP. TCP-only is the single most common mistake in community guides
• The dedicated server package. There is no SteamCMD app for it — TaleWorlds distributed it as a standalone download, and that download host is no longer online, so getting a clean copy is the first problem you have to solve

Installation

• Obtain and unpack the dedicated server package. It contains mb_warband_dedicated.exe, the shared resources and the Native module.
• Start it with mb_warband_dedicated.exe -r <script> -m <module>. The -r file is a list of set_* commands ending in start, and -m names a folder under Modules.
• You must launch it from its own folder. The executable resolves the script, the module tree and the log folder against the working directory, so starting it from anywhere else silently gives you a default Native server with none of your settings.
• Write the script by hand. Everything lives in it: set_server_name, set_pass_admin, set_max_players, set_mission, the set_map and add_map rotation, factions, friendly fire, combat speed, voting rules and the log paths.
• Forward the game port on both TCP and UDP — the server binds both on the same number.
• Running more than one server on a box means giving each instance its own port and its own set_server_log_folder and set_server_ban_list_file, or they overwrite each other's logs and bans.
• Modules have to be installed on the server too, matching what your players run. There is no Steam Workshop for Warband, so module folders are copied in by hand on both ends.
• Share your public IP and game port. Players add you under Favorites with <ip>:<port>.

Administration

• There is no RCON and no web admin. You claim admin in game by opening the admin panel and entering the password from set_pass_admin.
• From there you can kick and ban, change the map and mode, and restart the round. That panel is the entire moderation surface.
• Bans are written to a plain text ban list in your log folder, edited by hand.

Why Wait? Use SurvivalServers Instead

• Instant provisioning on enterprise NVMe SSD hardware with DDoS protection across 8 global datacenters
• We host the server build ourselves, so there is no hunting for a package that is no longer distributed
• Your config is rebuilt from our control panel on every start, so nothing can quietly overwrite your settings
• Every server setting is a labelled field in one form — mode and map rotation, rounds and scoring, combat rules, factions, bots, and voting and admin
• Pick your game mode from a dropdown and your map rotation from a list, instead of hand-writing set_map and add_map lines
• Upload Persistent World, cRPG or any other module over FTP or the File Manager and select it by name — no launch flags to edit
• Automated restarts, scheduled backups, and full FTP and File Manager access on day one
• No package hunting, no port forwarding, no firewall rules, no Windows updates to babysit