Assetto Corsa admin commands
On Assetto Corsa, admin commands are typed in the in-game chat, after signing in with the admin password. On a server from OuiHeberg, this password is generated when the server is created and sits in OuiPanel. This guide shows how to find it, sign in as admin, then kick a driver, change session or add ballast. It assumes you already ordered a server from our Assetto Corsa server hosting plans.
The server must be installed and have started at least once. The guide How to host an Assetto Corsa server explains the Steam sign-in and the first start.
Find the admin password
The admin password is a server variable in OuiPanel. You can copy it or change it.
Open your server in OuiPanel, then Configuration › Server Settings.
In the Environment Variables block, copy the value of the Admin password field.
To change it, enter a new password, confirm with the check mark, then restart the server.
The generated password has 16 characters. A new password must have from 8 to 40. At each start, OuiPanel writes it on the ADMIN_PASSWORD line of cfg/server_cfg.ini. Change it in the variable, not in the file.
Only give this password to your admins. An admin can kick and ban drivers, restart the current session and change the ballast of the cars.
Sign in as admin
Join your server with the game and go out on track, or stay in the pits.
Open the in-game chat.
Type
/adminfollowed by the password, then confirm.
/admin AdminPassword
The server confirms the sign-in in the chat. All commands start with / and are typed in that same chat. The admin sign-in lasts as long as you stay on the server. After reconnecting, type the command again.
The Kunos server has no RCON reachable over the network. The OuiPanel Console is for reading the server log. Type the commands in the in-game chat.
Identify, kick or ban a driver
Commands target a driver by their car number, called the car ID. This number matches the slot occupied in entry_list.ini, from 0 to the last one.
These commands are the ones the community and hosting providers report for the Kunos server, which has no official documentation online. We have not verified them on our servers yet.
| Command | Effect |
|---|---|
/client_list | Shows the list of connected drivers, with their car number |
/kick Nickname | Kicks the driver by name. They can come back right away |
/kick_id 3 | Kicks the driver of car 3. Safer than a name with special characters |
/ban_id 3 | Kicks the driver of car 3 and adds them to blacklist.txt. They can no longer join the server |
The blacklist.txt file, at the server root, holds one Steam ID per line. To lift a ban, remove the driver's line in the File Manager, then restart the server. This file is kept during a reinstall.
The Steam ID is a 17-digit number that starts with 7656119. It appears in the address of the driver's Steam profile, after steamcommunity.com/profiles/, if that profile has no custom address.
Manage sessions and ballast
These commands come from the same list, reported by the community.
| Command | Effect |
|---|---|
/next_session | Ends the current session and moves to the next one, for example from practice to qualifying |
/restart_session | Restarts the current session from the beginning |
/ballast 3 50 | Adds 50 kg of ballast to car 3, until the next server restart |
Sessions follow the order of the [PRACTICE], [QUALIFY] and [RACE] sections of cfg/server_cfg.ini. When the race ends, the server starts over from the beginning, with LOOP_MODE=1, or stops otherwise.
Permanent ballast is set in entry_list.ini, on the BALLAST line of the slot concerned, and the engine restrictor with RESTRICTOR. These values apply when the server starts.
Before restarting a session, warn your drivers in the chat. The server has no announcement command.
Restrict the server to your drivers
Three settings limit who can join. The first is set in the OuiPanel variables, the other two in the files, with the server stopped.
| Setting | Effect |
|---|---|
| Server password | OuiPanel variable. Drivers must enter this password to join. Empty, the server is open |
LOCKED_ENTRY_LIST=1 | In server_cfg.ini. Only drivers whose GUID is in entry_list.ini can join |
GUID=7656119… | In entry_list.ini, [CAR_n] section. Reserves that slot for the driver with that Steam ID |
In the Console, stop the server with Stop.
In the File Manager, open the
cfgfolder, thenserver_cfg.iniorentry_list.ini.Change the value, click Save, then start the server.
These files can also be edited from your computer over SFTP. The guide How to connect via SFTP with FileZilla explains the connection.
To add community cars or tracks, read the guide How to add mods to an Assetto Corsa server.
If a command does not work
| Symptom | Solution |
|---|---|
| No command responds | Sign in first with /admin. After reconnecting to the server, type it again |
| The password is refused | Copy it from the Admin password variable. After a change, restart the server |
| The command was typed in the OuiPanel Console | The server expects its commands in the in-game chat, once signed in as admin |
| The wrong driver is targeted | Use /client_list, then the car number with /kick_id rather than the name |
| A banned driver comes back | Check that their ID is in blacklist.txt. The file is read when the server starts |
| The ballast disappears | /ballast lasts until the restart. For permanent ballast, write it in entry_list.ini |
Need help?
Open a ticket from Tickets › Open a Ticket, or from the Contact support tile at the bottom of your server's page in the client area. You can also ask your question on the OuiHeberg Discord.
Assetto Corsa server hosting from $2.30/mo, up to 24 drivers on official tracks, with SFTP access for your mods, backups and DDoS protection included.
View plans →