The complete, honest guide to running your own MX Bikes multiplayer server. We'll walk through the manual setup first. Then we'll show you how to skip all of it.
Option A: The Manual Way
7 steps between you and a working MX Bikes server. Buckle up.
Step 1: Get a Machine to Host On
You need a Windows machine that can stay on 24/7. System requirements are modest: 2GB RAM and a dual-core CPU, which your toaster probably has at this point. The real issue is the internet connection. You need a static IP or dynamic DNS, and decent upload speed. A cloud VPS works but costs $10-30/mo just for the machine.
Step 2: Download the Server Files
Head to mx-bikes.com/downloads and grab the full game installation. There's no standalone server download. The game executable (mxbikes.exe) IS the server when you launch it with the -dedicated flag. So yes, you're installing the entire game just to run a server.
Step 3: Configure server.ini
Create a .ini file with sections like [connection], [event], [weather], [race], and [hardcore]. Set server name, max players, track, session lengths, weather, and more. Launch with: mxbikes.exe -dedicated 54210 -set params server.ini. Most settings are cryptic numbers with barely any official documentation.
Step 4: Port Forwarding
MX Bikes needs UDP port 54210 for game traffic, 54220 for live timing, and 54230 for remote admin. Log into your router's admin panel, find port forwarding, and forward these to your machine's static local IP. Every router has a different UI, some ISPs use CGNAT which makes it impossible, and if you get it wrong the server silently doesn't show up.
Step 5: Install Tracks and Mods
Download .pkz track files from MXB-Mods and place them in the mods/tracks/ folder. Bikes go in mods/bikes/. Some tracks have separate server versions. Use the wrong one and your server either crashes or silently loads a completely different track with no error message.
Step 6: Player Management
Player management is done through text files and console commands prefixed with '!'. To ban someone you need their GUID from the server console output. No web panel, no app, nothing. Someone wrecking at 2am? Remote into your machine and manually edit a text file.
Step 7: Keep It Running (Forever)
Servers crash a lot, especially with custom tracks. Windows will restart for updates at 3am. You need auto-restart scripts. Game updates require re-downloading files manually every time. There's zero built-in crash recovery. Server goes down at midnight? It stays down until you wake up.
Option B: Use CBRHosting
CBRHosting is a dedicated hosting platform built specifically for MX Bikes. Instead of managing servers manually, you get a fully managed experience with features designed for the MX Bikes community.
Instant Deploy
Create a server in seconds. Pick a name, select a region (Europe or USA), and your server is live. No SteamCMD, no config files, no port forwarding.
Track Library
Access 663+ tracks directly from the dashboard. Search, preview, and install tracks with one click. No manual file management, no version mismatches.
Live Lap Timing
Automatic lap timing and session recording on every server. Personal bests, session history, and rider statistics without any additional setup.
Full Server Management
Start, stop, and configure your server from a web dashboard. Automated messages, ban management, server settings. All without touching a config file.
Racing Series System
Run multi-round championships with automatic server configuration, session flows, rider registration, live results, and standings. A complete race management platform for $9.99/month.