BeamNG.drive (BeamMP) Server Admin Commands and How to Use Them

BeamMP’s stock server has nine console commands: help, list, kick, say, status, settings, lua, clear and exit. Enter them in the BeamMP-Server terminal or a hosting panel’s live console, not in BeamNG.drive’s normal chat. The vanilla server does not provide a built-in ban list, mute system, whitelist, permission groups or in-game administrator role. Those features require a compatible plugin, and their syntax can differ between plugins and hosting providers.

This guide explains every stock command, shows the exact workflow for kicking or warning players, separates temporary runtime changes from persistent configuration, and identifies which moderation commands come from plugins rather than BeamMP itself.

Where do BeamMP server commands run?

Run stock commands in the BeamMP-Server process window or in the live console supplied by your server host. A command entered in BeamNG.drive’s player chat will not be interpreted by the vanilla server. Some plugins add chat commands, but that is an extension and must be installed and configured separately.

Self-hosted server

1. Start the BeamMP server executable on Windows or Linux.
2. Click the server terminal so it has keyboard focus.
3. Type a command and press Enter. The response appears in the same console.

Managed hosting panel

1. Open your provider’s control panel and select the BeamMP instance.
2. Open the page labelled Console, Live Console or an equivalent real-time log view.
3. Send the command through that input, then confirm the result in the log.

If a command is rejected after an update, type help on that server. The command reference updated October 7, 2026 describes the nine built-in commands, but a particular server build or host wrapper can expose a different set.

What are the built-in BeamMP admin commands?

The stock command set is intentionally small. It covers player lookup, kicking, announcements, diagnostics, runtime settings, Lua debugging and clean shutdown, but not persistent moderation policy.

Command	What it does	Important details
help	Lists commands available in the current console.	Use it first after changing server versions or adding a plugin.
list	Shows connected players, names, IDs and car counts.	Run it before a kick so you identify the correct connection.
kick <name> [reason]	Disconnects one player.	Name matching starts at the beginning of the name and ignores case. Quote a name containing spaces.
say <message>	Broadcasts a message to everyone.	Useful for race starts, restarts and maintenance warnings.
status	Displays player, car, guest, synchronization, packet and subsystem information.	Use it when players report lag, failed synchronization or connection trouble.
settings	Reads or changes settings while the server is running.	Enter settings help for the syntax supported by your build. Persistent values belong in ServerConfig.toml.
lua [state id]	Opens the Lua prompt, optionally for a plugin state.	Inside the prompt, :help, :events, :queued and :exit are debugger commands.
clear	Clears the visible console display.	Cosmetic only; it does not clear logs, players or settings.
exit	Shuts the server down cleanly.	Warn players first, especially on a public server.

How do I see who is connected before taking action?

Use list. It returns the player names and IDs currently connected, along with each player’s car count, so you can distinguish similarly named users and spot an unexpected vehicle load.

1. Enter list in the server console.
2. Match the displayed name to the player’s in-game identity. If two names share a beginning, use the longer, more specific name or the available ID information.
3. Copy the exact spelling, including spaces, for a later command.

The list is a point-in-time view. A player can disconnect between the lookup and a moderation command, in which case the command may report no matching connection.

How do I kick a player from a BeamMP server?

Use kick <name> [reason] in the terminal or live console. The documented matcher is case-insensitive and starts with the beginning of a name; put quotation marks around names that contain spaces.

Basic kick

kick Driver42

Kick with a reason

kick Driver42 reckless driving

The reason is sent with the disconnect action, so keep it short and specific. For a spaced name, quote the name portion:

kick "Track Marshal" repeated blocking

Safe operating sequence

1. Run list and verify the target.
2. Send a warning with say if the situation is minor or ambiguous.
3. Run the kick command with a factual reason.
4. Run list again to confirm the connection is gone.

A kick is temporary. Without a moderation plugin, the same player can reconnect immediately if the server is public.

How do I broadcast a warning or race announcement?

Use say <message> to send one server-wide message. It is the stock way to announce a restart, explain a kick, or signal the start of an event.

say Five minutes until scheduled maintenance.

Because the command broadcasts to every connected player, avoid including private moderation details. For a single-player explanation, use your normal staff communication method instead.

How do I diagnose lag and synchronization problems?

Run status. Its output includes player and car information plus guest, synchronization, packet and subsystem details that help separate a server-side problem from an individual connection issue.

1. Ask the affected player when the problem occurs and whether other players see it.
2. Run status and note the current player, car and synchronization data.
3. Compare the result after the player reconnects or after a suspected mod is removed.
4. Check the server log for repeated errors before changing settings.

status is diagnostic output, not a performance benchmark. It does not by itself identify the cause of every frame-rate or network complaint.

How does the settings command work?

settings reads or changes values for the running process. Type settings help to see the exact subcommands accepted by your server version.

settings help

Runtime changes and saved configuration are different:

• Runtime: a value changed through settings affects the current process according to that build’s rules.
• Persistent: values that must survive a restart belong in ServerConfig.toml, followed by a controlled server restart when required.

After changing a runtime value, verify it with the corresponding read form of settings. Do not assume a successful console response means the value was written to disk.

What can I do with the Lua console?

lua opens the server’s Lua prompt; adding a state ID targets a particular plugin state when one is available.

lua

lua 3

Inside that prompt, use the debugger commands below:

• :help lists commands supported by the Lua prompt.
• :events displays available event information.
• :queued shows queued work.
• :exit leaves the Lua prompt and returns to the server console.

Lua access is powerful and plugin-dependent. Treat it as an administrative and debugging interface, not as a substitute for documented moderation commands; an incorrect script can affect a running server.

When should I use clear or exit?

clear only changes the display

Use clear to remove old lines from the visible console when logs become hard to read. It does not erase the server’s log files, disconnect players or undo a setting.

exit stops the server

Use exit for an orderly shutdown. Before sending it, announce the timing with say, allow players to finish a session, and confirm that any needed configuration has been saved.

say Server shutting down in two minutes. Please disconnect safely.

exit

Does vanilla BeamMP support bans, mutes, whitelists or in-game admin roles?

No. The stock server does not include a built-in ban list, mute system, whitelist, permission hierarchy or in-game administrator role. The nine console commands are not a hidden moderation suite; in particular, there is no universal vanilla ban command.

What a moderation plugin can add

A compatible plugin can provide persistent player records, groups and chat-based administration. Cobalt Essentials, for example, documents permission levels, groups, bans, mutes, whitelist controls and chat commands.

Capability	Example documented chat command	Example console form
Kick	/kick <name> [reason]	Plugin-specific; follow its console syntax.
Ban	/ban <name> [reason]	Plugin-specific; follow its console syntax.
Remove a ban	/unban <name>	Plugin-specific; follow its console syntax.
Mute	/mute <name> [reason]	Plugin-specific; follow its console syntax.
Whitelist	/whitelist enable or /whitelist add <name>	Plugin-specific; follow its console syntax.
Assign a group	/setgroup <name> <group>	ce setgroup YourBeamMPName owner
Assign a permission level	/setperm <name> <level>	Use the plugin’s documented console equivalent.

The examples above belong to the plugin documentation, not BeamMP’s core. Install only a release compatible with your server version, place its server-side Lua files in the appropriate Resources server plugin directory, and read its own permission and data-storage instructions.

Why provider-specific role syntax needs caution

Some hosting knowledge bases show a [Roles] section in ServerConfig.toml and list in-game /kick, /ban, /unban and whitelist examples. Treat that syntax as provider- or implementation-specific unless the plugin you installed documents the same behavior. A command working on one hosted instance does not make it a universal BeamMP command.

How do I configure a BeamMP server for administration?

The server’s behavior is determined by more than the console: the Resources folder, environment variables, command-line arguments, ServerConfig.toml and the process working directory all matter. Configuration mistakes in any of these areas can make a command, plugin or mod appear to fail.

Choose a hosting model

Model	Where you administer	Main trade-off
Home server	Local terminal, with router port forwarding when players connect from the internet.	Free to run, but you maintain networking, uptime and security.
VPS	Remote terminal or provider console.	More setup and recurring infrastructure cost, but easier remote access and isolation.
Managed host	Provider’s live console and file manager.	Simpler deployment, while panel behavior and plugin support depend on that provider.

The official setup documentation supports native Windows and Linux servers. It uses port 30814 as the usual port and generates a ServerConfig.toml containing fields such as Port, AuthKey, AllowGuests, LogChat, Private, Name, MaxCars, MaxPlayers, Map and ResourceFolder.

Protect the AuthKey

The AuthKey is required for public server-list access. Treat it like a password: keep it out of screenshots, chat messages and public repositories, and never share it with another administrator unless you are deliberately transferring control through a secure channel.

Understand the Resources folders

The Resources directory is divided into Client and Server subdirectories. Vehicle and map mods belong in Resources/Client; server-side plugins use the server-side plugin folders and Lua files. Incompatible mods can cause connection or gameplay problems, so test a new package privately before deploying it to a public session.

How do vanilla administration and plugin administration differ?

Use the stock console for immediate operational tasks; add a plugin when you need persistent moderation policy or player-facing commands.

Decision point	Vanilla server	Plugin-based administration
Where commands run	Terminal or hosting live console.	Usually console plus in-game chat, depending on the plugin.
Moderation depth	Kick and broadcast only, plus diagnostics and settings.	Can add bans, mutes, whitelist, groups and permissions.
Persistence	Runtime changes through settings; durable configuration in ServerConfig.toml.	Moderation records and roles are stored according to the plugin’s data system.
Operational burden	You maintain a Windows or Linux server, networking and updates.	You also maintain plugin compatibility, permissions and plugin data.
Version dependence	Core syntax changes with BeamMP server releases.	Commands and configuration can change with both the server and the plugin release.

What should I check when a command or plugin does not work?

Work from the least invasive check to the most specific one. Most failures come from using a plugin command on a vanilla server, entering a command in the wrong console, or deploying files in the wrong directory.

• “Unknown command”: run help. If the command is absent, it is not part of the current core command set; check whether a required plugin is installed and loaded.
• The player is not found: run list again, copy the current name, and quote names containing spaces. A disconnect between lookup and action also produces a miss.
• Chat slash command does nothing: confirm that a moderation plugin providing that command is enabled. Vanilla BeamMP does not interpret general /ban or /mute commands.
• Settings revert after restart: move the intended durable value into ServerConfig.toml rather than relying only on a runtime settings change.
• Players cannot connect after a mod change: remove the newest vehicle or map package from Resources/Client, test again, and verify that all clients use compatible content.
• A public server is not listed: verify the AuthKey and its permissions, confirm the configured port and network forwarding, and remember that the server supports IPv4 only.
• Plugin behavior differs from documentation: check the plugin release, server version, load path and provider panel logs. Provider-specific role sections or commands are not guaranteed to match another installation.

What is a reliable day-to-day admin routine?

A short routine prevents most accidental kicks and configuration surprises.

1. Start or restart the server and read the console for load errors.
2. Run help once after an update so you know which commands are actually available.
3. Use list before acting on a player report.
4. Send a clear say announcement before restarts, map changes or scheduled maintenance.
5. Use status when complaints involve synchronization, packets or guests rather than immediately kicking players.
6. Record persistent configuration in ServerConfig.toml and keep the AuthKey private.
7. Back up plugin data before changing permissions, whitelist entries or moderation records.
8. Use exit for planned shutdowns instead of closing the process window abruptly.

Frequently Asked Questions

Can BeamMP servers use IPv6 for player connections?

The official documentation states that the server supports IPv4 only. If players on an IPv6-only network cannot connect, they need an IPv4 path or a network service that provides one.

Can I run a BeamMP server without renting a VPS?

Yes. A home server can be run for free on supported Windows or Linux hardware, although you must handle port forwarding, uptime and security yourself. A VPS is described as easier and more secure for many administrators, but it is not a requirement.

Where should BeamNG vehicle and map mods be installed?

Put client-downloadable vehicle and map content in Resources/Client. Test additions privately because incompatible mods can prevent connections or destabilize a session.

What happens if I expose my BeamMP AuthKey?

The key controls access needed for public server-list use and should be treated as a password. Replace or regenerate it according to your server setup if it has been posted publicly, then update the server configuration and restart it.