Admin commands can be typed in to the in-game chat (or sent from the Admin Panel on the Live Timings page) to trigger certain events. In order to access most of the admin commands you must either use the "Admin Password" that you configured on the Server Options page to connect to the server, or use the following command once joined with the same password:
/admin password
Once you have done that you will have full access to all of the admin commands.
Whenever a command is related to a certain driver you can always use either car ID, GUID or name to target that driver, for example if a driver had the name "Billy", was connected to car ID 4 and had the GUID "99999999999999999" I could kick them using any of the following commands:
/kick Billy/kick 4/kick 99999999999999999The only exception to this is the /spectate command.
/admin - Gives the user access to admin commands (e.g. /admin password)/spectator - Gives the user access to spectator commands (e.g. /spectator password)/help - Displays a list of currently available commands, you can also optionally add the name of a command for information about that command, for example /help admin./pm or /direct - Sends a direct message to another driver using car ID, GUID or name! Message must be wrapped in quotes (e.g. /pm Billy "How are you doing today?")/kick - Kick a driver from the server using car ID, GUID or name! (e.g. /kick 3)/force_kick - Forcibly close the server connection to a driver using car ID, GUID or name! (e.g. /force_kick 3)/ban - Kick a driver from the server and add them to the block list using car ID, GUID or name! (e.g. /ban 3)/unban - Remove a driver the block list using GUID (e.g. /unban 12345678987654321)/next_session or /ksns - Move to the next configured session, or back to the first session if loop mode is on/restart_session or /ksrs - Restart the current session/client_list - See a list of clients in the current entry list/ballast - Apply ballast (maximum 5000kg) to a driver from the server using car ID, GUID or name! (e.g. /ballast Kevin 40)/restrictor - Apply an air intake restrictor (maximum 400%) to a driver from the server using car ID, GUID or name! (e.g. /restrictor Brad 40)/next_weather - Move to the next configured weather in the session, if multiple weathers are defined/spectate - Spectate a given driver by their car ID (e.g. /spectate 10), only useful in Solo Qualifying sessions (Visibility Mode set to Solo)/spectate_class - Spectate a given class by their class name (e.g. /spectate_class lmp2), only useful in Class Qualifying sessions (Visibility Mode set to Class)These commands and the related information are only available from ACSM v2.4.0
Extra server information is intended for use by client side applications in order to get extra information from the server that is not usually made available to the client.
/server-extra-info-opt-in - Opt in to extra information from the server, sent via chat messages/server-extra-info-opt-out - Opt out of extra infomation from the serverAvailable from v2.4.0, collision messages are formatted as follows:
"Collision",CarID,DriverGUID,OtherDriverGUID,OtherCarID,EventType,Speed,Position,RelativePosition,TimeStamp,AfterSessionEnd
For example:
Collision,0,44444444444444444,,0,11,40.16,"Vec3F(-196.215378, -4.763421, 25.719995)","Vec3F(1.006236, -0.302321, 1.974535)",2006-01-02 15:04:05,false
EventType is 10 for a collision with another car and 11 for a collision with the environment, OtherCar/Driver data is empty for a collision with the environment.
Penalty messages are only sent if ACSM Custom Penalties are enabled, and then messages for certain systems (for example DRS usage) are only sent if that specific Penalty system is enabled.
Available from v2.4.2.
Sent whenever a driver receives an infraction:
"Infraction",CarID,DriverGUID,InfractionType,NumCuts,NumWarnings,WarningsBeforePenalty
For example:
Infraction,3,55555555555555555,0,1,3,5
These are the possible infraction types for the Infraction message.
| Value | Infraction Type |
|---|---|
| 0 | Cut |
| 1 | Collision With Car |
| 2 | Collision With Environment |
| 3 | Incorrect DRS Usage |
Sent whenever a penalty is applied to a driver:
"Penalty Applied",CarID,DriverGUID,PenaltyType,TriggeredBy,ClearIn,Infraction,Extra
For example:
Penalty Applied,5,99999999999999999,Ballast,admin,5,9,20
The Extra value varies depending on the context of the PenaltyType:
Drive Through: Number of laps to complete the drive throughBallast: Ballast amount in kgRestrictor: Restrictor amount in %Time: Time penalty in millisecondsThis value indicates whether the penalty was triggered by a server admin (in which case their Manager account name will be the value) or by the automated ACSM system (in which case the value will be "Automatic").
These are the possible infraction types for the Penalty Applied message.
| Value | Infraction Type |
|---|---|
| 0 | Cut |
| 1 | Collision with car |
| 2 | Collision with environment |
| 3 | Incorrect DRS usage |
| 4 | Did not use minimum number of tyre compounds |
| 5 | Finished session with unserved penalty |
| 6 | Left pit lane early during driver swap |
| 7 | Did not completed minimum number of driver swaps |
| 8 | Did not start race on best qualifying tyre |
| 9 | Given by admin |
| 10 | Failed to serve penalty |
| 11 | Failed to compete mandatory long pit stops |
| 12 | Left pit lane during mandatory long pit stop penalty window |
Sent whenever a penalty is cleared for a driver. Only Restrictor, Ballast and Drive Through penalties can be cleared, they may be cleared by an admin or cleared automatically when a driver completes the penalty (finished drive through or finished x laps with BoP).
"Penalty Cleared",CarID,DriverGUID,PenaltyType
For example:
Penalty Cleared,2,88888888888888888,Restrictor
Sent when DRS is enabled, on the configured lap.
DRS Enabled
Sent when a driver completes a lap, updating their average lap time as seen by the penalty system.
"Average Lap Time Update",CarID,DriverGUID,AverageLapTime
For example:
Average Lap Time Update,13,23232323232323232,142000
AverageLapTime is expressed in milliseconds.
Please note that any CarID used in Extra Server Information messages is the client side Car ID, not the server side Car ID. For the client their own ID is always 0, and the other IDs are adjusted from the server accordingly. For example when the client is in Server Car ID 2:
| Server Car ID | Client Car ID |
|---|---|
| 0 | 1 |
| 1 | 2 |
| 2 | 0 |
| 3 | 3 |
| 4 | 4 |