MX Bikes Server Settings Explained

Server identity and access

• name: the server name riders see in the server browser.
• maxclient: the number of rider slots. CBRHosting servers run from 2 up to 42 slots.
• password: a join password for private sessions. Leave it empty for a public server.
• admin_password: lets a rider become admin in game. On CBRHosting you can also list admins by GUID so they get admin automatically when they join.
• max_ping: kicks riders above the ping you set, which keeps races fair for everyone else.

Sessions: practice, qualifying, warmup and race

A race weekend on MX Bikes is a chain of sessions. The config sets how long each one lasts and how the race is measured.

• practice_length and open_practice: how long practice runs and whether riders can practice freely between events.
• qualifypractice_length and prequalify_length: timed qualifying that decides the gate pick.
• warmup_length: the short session right before the gate drops.
• race_length_format, race_minutes, race_laps and race_extralaps: a race can run on time, on laps, or on time plus extra laps.
• raceover_length and restart_delay: how long results stay up and how quickly the next event starts.
• sighting_lap and quick_race: optional sighting lap, or skip straight to racing.

Bikes, rules and realism

• category and allowed_bikes: limit the server to a class such as MX1 or MX2, or to specific bikes.
• realistic and no_aids: turn rider aids off for a sim focused server.
• force_cockpit: force first person view.
• overjump_crash and auto_reset: how strict the server is about crashes and resets.
• limited_tyre_sets: limit tyre choices for series rules.
• chat_disable and polls_disable: switch off chat or rider votes.

Weather, time and track conditions

• conditions, temperature, wind_speed and wind_direction: the weather for the event.
• time: the time of day.
• track_conditions and track_layout: how the dirt starts and which layout of the track is used.
• tracks_shuffle: shuffle the rotation instead of running it in order.

Whitelist, blacklist and bans

The server reads a whitelist and a blacklist file by rider GUID. CBRHosting writes those files for you from the dashboard: ban a rider on one server or across all of your servers, with a reason and a duration, and the ban follows them. Series organisers can whitelist registered riders only.

Skip the config file entirely

Every setting above is a labelled control in the CBRHosting server settings, with a short explanation next to it. Save, and the config is regenerated and the server restarted for you. If you prefer, see the manual dedicated server guide for running it yourself.

Frequently asked questions

Where is the MX Bikes server config file?

When you run the server yourself, the config is a text file passed to mxbikes.exe with the -dedicated and -set params options. On CBRHosting you never touch it, the dashboard writes it for every start.

How many slots can an MX Bikes server have?

CBRHosting servers support from 2 to 42 rider slots, and you can change the slot count at any time from the server settings.

Can I run races on laps instead of time?

Yes. Races can run on time, on a lap count, or on time plus extra laps, set per server.

Get your MX Bikes server online now

Free 24 hour trial with 1 server and 10 slots. No credit card needed.