BeamMP Config Editor: ServerConfig.toml as a Form (BETA)

Every BeamMP server is controlled by one file, ServerConfig.toml, sitting in the server’s root directory. It is not a large file, but it is still real TOML with sections and quoting rules, and the LoafHosts install script rewrites the whole thing fresh every time you reinstall the server. The BeamMP Config Editor is a BETA feature that lets you edit the settings that matter from a grouped form instead of opening the raw file, with two presets for common setups. This guide covers exactly what the editor touches, how the settings are grouped, what stays locked and why, and when a change actually takes effect.

Note: The BeamMP Config Editor is a BETA feature. It works today, but expect it to keep evolving as we round out coverage.

What the Config Editor Edits

The editor works on a single file: ServerConfig.toml in your server’s root directory. That file has two sections, [General] and [Misc], and the editor exposes most of the keys in both as labelled form fields, each with a short help line describing what it does. Save, and only the fields you changed are written back; the rest of the file, including any manual edits you made directly to keys the editor does not expose, is left alone at save time.

The one thing worth knowing up front: LoafHosts’s install script regenerates ServerConfig.toml from scratch every time the server is reinstalled, not just on first deploy. That behavior comes from BeamMP-Server’s own install process, not from the Config Editor. It means any edits you make, whether through this editor or by hand, persist across normal restarts and stops, but are wiped if you run Reinstall Server. The editor cannot change that; it is simply how the underlying installer works.

Note: The editor reads and writes the real ServerConfig.toml on disk, not a separate copy

Note: Reinstalling the server regenerates ServerConfig.toml from scratch, which resets both the editor’s fields and any manual edits, not just the panel’s own startup variables

Tip: If you have custom edits you care about (a Tags value, a [Misc] tweak), note them down before running Reinstall Server

Opening the Config Editor

Open your BeamMP server in the LoafHosts panel and look in the sidebar under the Game section. You will find a Config Editor entry there; clicking it opens the form in place of your normal server view, with the sidebar and status header still visible. If the server has never been started, ServerConfig.toml will not exist on disk yet, since it is the install script that writes it, so the editor will ask you to start the server once first.

Tip: If the editor reports no settings found, start the server once to generate ServerConfig.toml, then reopen the editor

How the Settings Are Grouped

The form organizes the file’s keys into a small set of groups so you are not scanning one long list:

• Server: identity and housekeeping fields: Server Name, Description, Tags (comma-separated, shown in the BeamMP server browser), Private, Resource Folder, and Chat Logging.
• Gameplay: the two keys that shape a session: Max Players and Max Cars per player, plus Map, the in-game level the server loads.
• Misc: the [Misc] block: Debug logging, and three server-behavior toggles carried over from the file’s own Misc section (Hide Update Notice, Send Crash Reports, and Show Crash Report Message).
• Network: reserved for the port and authentication key. Both are shown for reference but are locked (see below), since they are managed from the Startup tab.

Each field’s help text is written from the meaning of the underlying TOML key, not just its name. For example, the tip on Max Cars explains it is a per-player limit on simultaneously spawned vehicles, and the tip on Private explains that turning it on hides the server from BeamMP’s public server list rather than restricting who can connect with the right IP.

Tip: Tags accepts a comma-separated list like Freeroam,Drift, shown to players browsing the BeamMP server list

Tip: Map takes a literal in-game level path, for example /levels/east_coast_usa/info.json, not a friendly map name

Locked Fields: Port and Authentication Key

Two fields, the server Port and the Authentication Key, are shown locked and cannot be edited from the Config Editor. They live in the file’s [General] section like everything else, but they are managed from the server’s Startup tab instead: Port is tied to the network allocation your server was provisioned with, and the Authentication Key is the secret token you generate at keymaster.beammp.com. Editing either one here would either be rejected or overwritten the next time the panel writes your startup values into the file, so the editor locks them and points you at the Startup tab, which is the correct place to change them.

Note: Port and Authentication Key are locked in the Config Editor; change them from the server’s Startup tab instead

Note: The lock is enforced on save, not just hidden in the UI; the editor will not write those two keys under any circumstances

One-Click Presets

If you would rather not think through individual fields, the editor offers two presets:

• Private invite-only: turns Private on, so the server is hidden from BeamMP’s public server list. Good for a friends-only session where you share the IP directly.
• High population: raises Max Players to 20 and Max Cars to 3, a starting point for a busier public server that wants more players and more cars on track at once.

Applying a preset only changes the specific fields it targets; everything else in your config, including your server name, description, and map, is left exactly as it was. As with any change made here, it takes effect the next time the server (re)reads the file.

Tip: Private invite-only is the safest starting point while you are still testing a new server

Tip: High population is a starting point, not a hard ceiling; you can still fine-tune Max Players or Max Cars individually afterward

Validation

Each field is checked against the type BeamMP actually expects before anything is written. Max Players and Max Cars are whole numbers within a sensible range; Private, Chat Logging, Debug, and the three Misc toggles are written as TOML booleans (true/false); text fields like Server Name, Description, Tags, and Map are saved as quoted strings. If a value fails validation, for example a non-numeric entry in Max Players, the save is rejected with a message and the on-disk file is left untouched.

Note: A bad value is caught before it reaches ServerConfig.toml; the file is only ever written once your input passes validation

When Changes Apply

BeamMP-Server reads ServerConfig.toml at startup, so a saved change is not live until the server (re)reads the file. Every field the Config Editor exposes applies on a restart; none of them require a full reinstall to take effect. Save your changes, then restart the server from the Power controls to bring them in.

Note: Saving only writes the file; restart the server to load the new settings

Tip: Make several edits, save once, then do a single restart to bring them all in together

What’s Not in the Editor Yet

A handful of ServerConfig.toml keys, such as ResourceFolder, are present in the file but not yet exposed as editor fields; the same is true of anything you add to the file by hand outside the fields listed above. Those values are preserved across saves (the editor never touches a key it does not expose), but if you need to change one, use the File Manager to open ServerConfig.toml directly. Since this is a BETA feature, expect the field coverage to grow over time.

Tip: Use the File Manager for any ServerConfig.toml key not yet listed in the form; the Config Editor will not overwrite it

Putting It Together

The BeamMP Config Editor turns ServerConfig.toml into a short, grouped form: identity and housekeeping under Server, the two gameplay dials under Gameplay, the crash-reporting and update-notice toggles under Misc, validated input, and two presets for the most common starting points. Port and the Authentication Key stay locked to the Startup tab, where they belong. Change what you need, save, restart, and your BeamMP server is running with the settings you chose, no raw TOML required.