Motor Town Admin Commands and Web API Guide
Admin control on a Motor Town: Behind The Wheel dedicated server works differently from most survival games: instead of a long list of chat commands, Motor Town gives admins an in-game admin menu, a police role system, and (the part almost nobody documents) a full HTTP Web API on the server for kicks, bans, announcements, roles, and live server data. This guide covers all three.
Making a player an admin
Admins are defined in the server's DedicatedServerConfig.json under the Admins list. Each entry pairs a UniqueNetId with a Nickname. For Steam players the UniqueNetId is the SteamID64 (look yours up at steamid.io). Add the player, restart the server, and when they rejoin they have access to the in-game admin tools. The bAllowAdminToRemoveAdmin setting controls whether admins can demote each other (off by default).
On a Survival Servers instance this is a panel field: put the SteamID64s in Admin Steam IDs in the Server Config tool and restart.
The official ReadMe also documents a discovery trick for non-Steam ids: open the server from your game client, add the admin in-game, then read the generated entry out of GameUserSettings.ini under %LOCALAPPDATA%\MotorTown\Saved\Config\Windows.
The police role
Motor Town has a dedicated police role for RP servers. PoliceRolePlayers in the config lists the players (same UniqueNetId + Nickname shape as Admins), and bAllowPoliceVehicleByPlayerRole controls whether police vehicles are restricted to that role: set it true and only rostered officers can drive them; leave it false and anyone can.
The Web API: the server's real command console
The dedicated server can expose an HTTP API with everything a community admin needs, without anyone being in the game. Enable it in DedicatedServerConfig.json:
- bEnableHostWebAPIServer: true
- HostWebAPIServerPassword: a strong password; it authenticates every call
- HostWebAPIServerPort: default 8080
- HostWebAPIDisabledCommands: optional list of endpoints to switch off
Every call passes the password as a parameter and returns a JSON envelope with data, message, and succeeded fields. Example:
curl "http://127.0.0.1:8080/player/count?password=yourpassword"
Security note: the password travels as a plain query parameter, so do not open the API port to the internet. Query it from the server machine itself (or a trusted network) and keep the port firewalled.
Endpoint reference
| Endpoint | Method | What it does |
|---|---|---|
| /chat | POST | Send a server-wide announcement, or a chat message with type=message and an optional color (hex like FF00FF) |
| /player/count | GET | Current player count |
| /player/list | GET | Every online player with name, unique_id, world location, and current vehicle |
| /player/kick | POST | Kick by unique_id (from /player/list) |
| /player/ban | POST | Ban by unique_id, optional hours (permanent if omitted) and reason |
| /player/unban | POST | Lift a ban by unique_id |
| /player/banlist | GET | Current ban list |
| /player/role/list | GET | List admin or police roster (role=admin or role=police) |
| /player/role/add | POST | Grant admin or police to a unique_id |
| /player/role/remove | POST | Revoke admin or police from a unique_id |
| /delivery/sites | GET | Live delivery and cargo state across the island's job sites |
| /housing/list | GET | Housing plots with owner and rental expiry |
| /version | GET | The server's game version, handy for checking client/server version match |
Doing all of this without curl
On Survival Servers instances the control panel's admin tools are built on this same Web API: kick, ban and unban, announcements, and the admin and police rosters are buttons and fields in the panel, with the API kept safely on the loopback interface. The dedicated server setup guide covers getting a server running in the first place, and the mods guide covers the vehicle-mod side of admin life.