Assetto Corsa administration commands depend on the software running your dedicated server. A stock Kunos server supports a compact set for authentication, session changes, player lists, kicking, banning and ballast. AssettoServer adds reason fields, pit commands, SteamID64 targeting, whitelist management, player inspection, weather and time controls, and temporary runtime configuration. First run /help in server chat and identify the installed implementation and version; AssettoServer’s documented command page is marked version 0.0.54, while a host may run another release.
This guide lists the stock commands, the additional AssettoServer syntax, safe moderation workflows, panel-console differences, persistence rules and fixes for common failures.
Which Assetto Corsa server implementation do you have?
Check the server software before copying a command. The original Kunos dedicated server and AssettoServer do not expose exactly the same commands, and a command added by AssettoServer will be rejected by an untouched Kunos installation.
- Stock Kunos dedicated server: the built-in set covers
/help, admin authentication, session control, player listing, kick, ban by car ID and ballast. - AssettoServer: includes the stock-style session commands plus moderation reasons,
/pit,/whois, whitelist and SteamID64 support, restrictor and ballast control, headlights, time, weather and selected live configuration.
Run /help after connecting as an administrator. It is the most reliable way to see what the running build accepts. Documentation labelled AssettoServer version 0.0.54 is a version marker, not a guarantee that every host is on that release.
What are the stock Kunos admin commands?
On the original Kunos server, enter these commands in the in-game server chat. The leading slash is part of the chat syntax.
| Command | What it does | Usage and cautions |
|---|---|---|
/help |
Displays commands available on that server. | Use it first when unsure which implementation or version is active. |
/admin <password> |
Authenticates you as an administrator. | Use the admin password configured for the server. Never post it in public chat. |
/next_session |
Ends the current session and advances the weekend. | Drivers lose the remainder of the current session, so announce it first. |
/restart_session |
Restarts the current session. | Useful after a false start or setup mistake; it interrupts everyone currently driving. |
/client_list |
Lists connected players and their car IDs. | Run it before ID-based moderation. |
/kick <player name> |
Removes a connected player. | Names containing spaces or unusual characters can be difficult to address reliably. |
/kick_id <car id> |
Removes the driver occupying a specific car slot. | The official example is /kick_id 2. |
/ban_id <car id> |
Removes the driver and adds the driver to the server blacklist. | Use the current car ID from /client_list; IDs can change when players reconnect. |
/ballast <car id> <kg> |
Adds ballast to a car. | The official example is /ballast 2 100, adding 100 kg to car ID 2. |
Stock Kunos administration requires the server’s admin password to be set (often exposed as ADMIN_PASSWORD in the server configuration). Some hosting setups also allow a player to join using that configured admin password; follow the authentication method documented by your host rather than assuming it is enabled everywhere.
How do I become an administrator in game?
Authenticate before attempting moderation or session control. A failed command usually means authentication, syntax, or implementation is wrong.
- Join the server with the account that should administer it.
- Open the server chat and enter
/admin YOUR_ADMIN_PASSWORD, replacing the placeholder with the configured password. - Run
/helpor a harmless command such as/client_listto confirm access. - If the server rejects the command, verify that the password is set in the server configuration and that you are using in-game chat rather than a provider console. Check the panel’s administrator permissions if the panel has its own access control.
Do not paste the password into a public announcement, screenshot or shared chat log. Change it if it has been exposed.
How do I kick, ban or send a player to the pits?
Use the least disruptive action that solves the problem. A kick is reversible, a ban is intended to prevent re-entry, and /pit is a non-punitive way to reset a driver on AssettoServer.
Find a reliable target
On stock Kunos, run /client_list and note the player’s car ID. AssettoServer accepts a car ID, SteamID64 or name for its documented player commands. A car ID or SteamID64 is safer than a name when the name contains spaces, punctuation or duplicate text.
Remove a driver temporarily
Stock syntax is /kick <player name> or /kick_id <car id>. AssettoServer supports /kick <id> [reason] and /kick_id <id> [reason]. For example, /kick_id 3 ignoring blue flags removes car 3 and displays the reason where that build supports reason messages.
Apply a ban
Stock Kunos provides /ban_id <car id>. AssettoServer documents /ban <id> [reason] and /ban_id <id> [reason]. A ban is stronger than a kick and is meant to block re-entry. Persistence depends on the server implementation: a hosted AssettoServer setup may write a blacklist.txt, while another build or provider can use a different file or mechanism. Do not assume one host’s file path applies to every installation.
Send a driver to the pits without banning
AssettoServer’s /pit <id> sends the selected driver to the pits. It is appropriate for a recovery or safety intervention when you do not want to disconnect the player.
Record a reason
When the installed implementation supports the optional reason argument, include a short factual explanation. It helps the affected driver and other administrators understand the action and avoids disputes over an unexplained ban.
How do I advance or restart an Assetto Corsa session?
Use /next_session to force the next session in the configured weekend, or /restart_session to reload the current session. Both stock Kunos and AssettoServer document these commands.
- Announce the change with a server message or voice communication so drivers can save setups and understand why the session will end.
- Authenticate with
/admin <password>if you have not already done so. - Enter
/next_sessionto move from practice to qualifying, qualifying to race, or to the next configured stage. - Enter
/restart_sessionwhen you need to repeat the current stage after a false start, configuration error or test.
AssettoServer also documents /say <message> for a server-wide announcement. If your build does not list /say in /help, use the host panel’s message feature or normal administrator communication instead.
What extra player controls does AssettoServer provide?
These commands are documented for AssettoServer and may not exist on stock Kunos servers. Use the exact syntax shown by the release you installed.
| Command | Purpose | Important details |
|---|---|---|
/kick <id> <reason>/kick_id <id> <reason> |
Kick a player with an optional reason. | The identifier can be a car ID, SteamID64 or name according to the implementation. |
/ban <id> <reason>/ban_id <id> <reason> |
Ban and remove a player. | Use an unambiguous ID and understand where your build stores the blacklist. |
/pit <id> |
Send a player to the pits. | Useful as a non-disconnect intervention. |
/whois <id> |
Display player information. | The documented implementation can show address and profile data; treat it as administrator-only information. |
/whitelist <steamid64> |
Add a Steam account to the whitelist. | Copy the complete 64-bit Steam ID; a display name is not a substitute. |
/restrict <id> <restrictor> <ballast> |
Apply an engine restrictor and ballast. | The documented restrictor range is 0–400. Confirm the unit and desired balance before applying it in a live race. |
/forcelights <on|off> <id> |
Force how a player’s headlights appear to others. | Use on or off exactly as shown. |
How do I change server time and weather while it is running?
AssettoServer can change time and weather at runtime when the relevant configuration and Custom Shaders Patch (CSP) features are available.
Set the server clock
Use /settime <HH:mm>, such as /settime 13:45. Enter a 24-hour time with a two-digit hour and minute.
Select a configured weather entry
Use /setweather <weatherId> to select a weather entry from server_cfg.ini. The value must correspond to an entry your server already defines; the command does not create a new weather definition.
List and apply CSP weather
Run /cspweather to list available CSP weather types. Then use /setcspweather <weatherType> <transitionDuration> to change the WeatherFX type and specify the transition duration. This requires the relevant CSP setting to be enabled on the clients and server. A client without the required CSP support may not display the same result.
What does the AssettoServer /set command change?
/set <key> <value> changes selected configuration values without stopping the server. Keys from server_cfg.ini use the Server. prefix; keys from extra_cfg.yml use Extra..
| Example | Effect |
|---|---|
/set Server.Name Start 123 |
Changes the server name to “Start 123” for the running instance. |
/set Extra.AiParams.MinAiSafetyDistanceMeters 100 |
Sets the documented AI minimum safety distance value to 100. |
/set Extra.AiParams.SplineHeightOffsetMeters 0.2 |
Sets the documented AI spline height offset to 0.2 metres. |
The official warning is: “Only use this for testing! All changes made with this command will be lost after a server restart.” Not every configuration key is runtime-editable. Use /set to test a value, then edit the appropriate configuration file and restart through your normal server procedure if the change should survive a restart.
Why does a command work in chat but not in my hosting panel?
In-game chat normally includes the leading slash, while a provider’s panel console may expect the command without it. The exact rule belongs to the panel, not to Assetto Corsa universally.
| Interface | Typical form | Example |
|---|---|---|
| In-game server chat | Slash-prefixed command | /next_session or /kick_id 3 ignoring blue flags |
| Hosting-panel console | Often omits the slash | next_session or kick 3 ignoring blue flags |
Some panels let an administrator issue commands while nobody is connected. If a panel rejects a slash-prefixed command, remove the slash and check its console help. If it rejects the no-slash form, use the panel’s documented syntax. In either interface, run /help in game chat to verify what the server itself exposes.
How should I use admin commands safely?
- Identify the implementation and version. Read the server startup information or panel description, then run
/help. Do not assume an AssettoServer command exists on stock Kunos. - Authenticate privately. Use
/admin <password>and protect the password. Check panel permissions if the console uses a separate administrator list. - Identify the target precisely. On stock servers, use
/client_listand the car ID. On AssettoServer, prefer a car ID or SteamID64 when names are ambiguous. - Choose the smallest intervention. Use
/pitfor a reset,/kickfor a reversible removal, and/banonly when a persistent block is justified. - Give context. Add a concise reason to AssettoServer kick or ban commands when supported.
- Warn before session changes. Announce
/next_session,/restart_sessionor disruptive weather changes so drivers are not surprised. - Persist deliberate configuration changes. Treat
/setas a live test. Write permanent values to the correct file and restart normally.
What should I check when a command fails?
- “Unknown command”: run
/help. You may be on stock Kunos, using syntax from another AssettoServer release, or missing a required module. - “Not authorized” or no response: authenticate again with
/admin <password>, verify the configured admin password, and confirm that your panel account has console rights. - The wrong player is affected: refresh
/client_list. Car IDs can change after a reconnect; use the current ID or a SteamID64. - A name with spaces fails: use
/kick_id,/ban_idor another supported numeric identifier instead of the name. - The command works in chat but not in the panel: test the panel’s no-slash form and read its console-specific help.
- A live configuration change disappears: that is expected for
/set. Editserver_cfg.iniorextra_cfg.ymlas appropriate and restart. - Weather looks different to some drivers: verify CSP/WeatherFX support and that the requested weather type exists in the server configuration.
- A ban does not persist: inspect the blacklist mechanism used by your specific build or host. A path documented for one hosted installation is not universal.
Which commands should I use for common situations?
| Situation | Recommended action | Command |
|---|---|---|
| A driver is disrupting the race once. | Kick with a reason. | AssettoServer: /kick_id <car id> disruption; stock: /kick_id <car id> |
| A repeat offender must be blocked. | Ban using an unambiguous identifier. | AssettoServer: /ban_id <id> repeat deliberate contact; stock: /ban_id <car id> |
| A driver is stuck or needs a non-punitive reset. | Send the driver to the pits. | AssettoServer: /pit <id> |
| The grid started incorrectly. | Restart the current session. | /restart_session |
| The event schedule must move on. | Advance to the next session. | /next_session |
| You need to test an AI or server value. | Change it temporarily, then edit the file if it should persist. | /set <key> <value> |
Frequently Asked Questions
Can I use AssettoServer commands on the original Kunos dedicated server?
No. Commands such as /pit, /whois, /settime and /set are AssettoServer features. On a stock server, rely on the commands shown by /help and do not treat a host’s AssettoServer documentation as a stock-server specification.
Where can I find a player’s SteamID64 for the whitelist?
Use the identifier information exposed by your server or administration panel and copy the complete 64-bit Steam ID. Do not substitute a display name, car number or shortened account identifier when using /whitelist.
Does restarting the server erase a kick?
A kick only removes the current connection, so the driver can normally join again. A ban is intended to block re-entry, but whether it survives a restart depends on the blacklist storage used by that particular server installation.
Can drivers see the result of an admin command?
Session changes and many moderation actions are visible through the resulting disconnect, pit move or session transition. AssettoServer’s optional reason text provides additional context for kick and ban actions; avoid exposing passwords or private information in public messages.