Server Configuration
Windows / Linux
Windows specific
| Default Installation Path |
|---|
| C:\Program Files (x86)\Steam\steamapps\common\Assetto Corsa Competizione\server |
Change the configuration.json, event.json and settings.js under the cfg Folder for your needs. After that you can Doubleclick on the accServer.exe to Start the Server. Keep in mind that you need to make Port Forwarding on your Router to get Players on your Server. Else it's just Locally accessible.
Linux specific (Ubuntu 18.04)
We need Wine because there is no Nativ Binary for Linux.
| sudo apt-get install wine-development |
Copy now all Server Files from your Windows System where you have ACC Installed to the Linux Server. After that you can Start your Server with
| wine ./accServer.exe |
Installation
In the ACC installation under ..:\Steam\steamapps\common\Assetto Corsa Competizione you will find the folder "server".
| Description | |
|---|---|
| cfg | The files for setting up a public or private multiplayer server are located in this folder |
| accServer.exe | Starts a server on your PC or dedicated server |
| ServerAdminHandbook_v7c.pdf | Contains the official documentation for operating an ACC server |
In the further course of this description, you will be shown what additional folders and files are added automatically or manually.
cfg-Folder
So far there are 3 files in this folder: ...\Steam\steamapps\common\Assetto Corsa Competizione\server\cfg\
| Link to Description | |
|---|---|
| assistRules.json | ↓assistRules.json |
| configuration.json | ↓configuration.json |
| event.json | ↓event.json |
| settings.json | ↓settings.json |
In the further course of this description, you will be shown what additional folders and files are added automatically or manually.
current-Folder
If you start accServer.exe now, a folder "current" will be created in "cfg" Folder. This contains your settings from the .json-files as a text file.
If you make a mistake in .json, it will be corrected when the server is started and will be displayed in the text file. This gives you another way to go about troubleshooting.
| Compare them with your settings at: | |
|---|---|
| configuration.txt | ↓configuration.json |
| entrylist.txt | ↓entrylist.json |
| event.txt | ↓event.json |
| eventRules.txt | ↓eventRules.json |
| settings.txt | ↓settings.json |
Configuration
The server is exclusively configured via JSON files in UTF16-LE format. In general, it is a good idea to get used to the JSON syntax, and/or test your configurations with an syntax check on https://jsonformatter.curiousconcept.com/.
To get a clean start, you can just remove the .json files and start the server once, it will autogenerate them with current defaults. Additionally, you can reduce the “configVersion” contained in each file to get new properties generated (this is true for all the configs). Certain “advanced” settings will be hidden when the value is set to it’s default during this process.
The configuration is split into different files, which represent different levels of what you would possibly like to keep or change frequently:
configuration.json
- Here we define the very technical settings that possibly never change and define the server “identity”.
- The most important thing to know is that both ports must be unique on the system, the firewall allows connections and the ports are accessible from the internet.
| File Content | Property | Description |
|---|---|---|
|
{ | ||
| tcpPort | ACC clients will use this port to establish a connection to the server | |
| udpPort | Connected clients will use this Port to stream the car positions and is used for the ping test. In case you never see your server getting a ping value, this indicates that the udpPort is not accessible | |
| registerToLobby |
| |
| maxConnections | The maximum amount of connections a server will accept at a time. If you own the hardware server, you can just set any high number you want. If you rented a 16 or 24 slot server, your Hosting Provider probably has set this here and doesn’t give you write-access to this configuration file. | |
| lanDiscovery | Defines if the server will listen to LAN discovery requests. Can be turned off for dedicated servers. | |
| configVersion | ... |
Attention: Running a server on a private PC is not recommended. It requires opening and forwarding Ports onto your private system, which makes it vulnerable to random and/or malicious internet traffic. Additionally, private ISP bandwidth is often asymmetrically limited in the upload, which can easily lead to a bad server performance and in the result in a bad multiplayer experience for everyone around.
settings.json
The setting defines your personal server settings, which may be changed from time to time, but also define the server.
| File Content | Property | Description |
|---|---|---|
|
{ |
serverName | The server name displayed in the ACC UI pages |
| adminPassword | The password you specify allows a driver or spectator to log in as Server Admin in the chat window ( ENTER key ) of the server. | |
| trackMedalsRequirement | Defines the amount of track medals that a user has to have for the given track
| |
| safetyRatingRequirement | Defines the Safety Rating (SA) that a user must have to join this server
| |
| racecraftRatingRequirement | Defines the Racecraft Rating (RC) that a user must have to join this server
| |
| password | Password required to enter this server. If a password is set, the server is declared →Private Multiplayer. | |
| spectatorPassword | Password to enter the server as spectator. Must be different to “password” if both is set. | |
| maxCarSlots | Defines the amount of car slots the server can occupy; this value is overridden if the pit count of the track is lower, or with 30 for public MP. The gap between maxCarSlots and maxConnections ( in configuration.json ) defines how many spectators or other irregular connections ( ie entry list entries ) can be on the server. | |
| dumpLeaderboards | If set to 1, any session will write down the result leaderboard in a “results” folder ( must be manually created ). | |
| isRaceLocked | If set to 0, the server will allow joining during a race session. Is not useful in →Public Multiplayer, as the user-server matching will ignore ongoing race sessions. | |
| randomizeTrackWhenEmpty | If set to 1, the server will change to a random track when the last drivers leaves ( which causes a reset to FP1 ). The “track” property will only define the default state for the first session. | |
| centralEntryListPath | Can override the default entryList path “cfg/entrylist.json”, so multiple ACC servers on the machine can use the same entrylist ( and custom car files ). Set a full path like “C:/customEntryListSeriesA/”, where the entrylist is stored.
Attention: The path seperators have to be slashes ( / ), backslashes ( \ ) will not work. | |
| allowAutoDQ | If set to 0, the server won’t automatically disqualify drivers, and instead hand out Stop&Go ( 30 Secounds ) penalties. This way a server admin / race director has 3 laps time to review the incident, and either use /dq or /clear based on his judgement. | |
| shortFormationLap |
After a patch there is always the phenomenon that the meaning of the values 0 and 1 are reversed. | |
| dumpEntryList | Will save an entry list at the end of any Qualifying session. This can be a quick way to collect a starting point to build an entry list, and is a way to save the defaultGridPositions which can be used to run a race without Qualifying session and predefined grid. Also see the corresponding admin command. | |
| formationLapType | Toggles the formation lap type that is permanently used on this server:
After a patch there is always the phenomenon that the meaning of the values 0 and 1 are reversed. |
event.json
Defines the race weekend the server runs. This configuration file is meant to be swappable, so you can easily switch between different event templates by renaming/overwriting them.
| File Content | Property | Description |
|---|---|---|
|
{ |
track | The track we run.
Setting a wrong value will also print out the available track keys in the log. With the 1.1 update containing the 2019 season content, each track has a _2019 variant. Using this track will set the BoP and track grip correspondingly. |
| preRaceWaitingTimeSeconds | Preparation time before a race. Cannot be less than 30s. | |
| sessionOverTimeSeconds | Time after that a session is forcibly closing after the timer reached '0:00. Something like 107% of the expected laptime is recommended.
| |
| ambientTemp | Sets the baseline ambient temperature in °C.
| |
| cloudLevel | Sets the baseline cloud level, →Race Weekend Simulation.
| |
| rain | If weather randomness is off, defines the static rain level. With dynamic weather, it increases the rain chance.
Values greater than 0.1 can override the value of cloudLevel. | |
| weatherRandomness | Sets the dynamic weather level:
| |
| postQualySeconds | The time after the last driver is finished ( or the sessionOverTimeSeconds passed ) in Q sessions and the race start. Should not be set to 0, otherwise grid spawning is not secure. | |
| postRaceSeconds | Additional time after the race ended for everyone, before the next race weekend starts. | |
| metaData | A user defined string that will be transferred to the result outputs. | |
| simracerWeatherConditions | Experimental / not supported: if set to 1, this will limit the maximum rain/wetness to roughly 2/3 of the maximum values, translating to something between medium and heavy rain. It may be useful if you feel forced to run very low cloudLevel and weatherRandomness values just to avoid thunderstorm; however high levels (0.4+ clouds combined with 5+ randomness) will still result in quite serious conditions. | |
| isFixedConditionQualification | Experimental / not supported: if set to 1, the server will take the rain, cloud, temperature, rain levels literally and make sure whatever is set up never changes. Daytime transitions still happen visually, but do not affect the temperatures or road wetness. Also rubber/grip is always the same. This is intended to be used for private league qualification servers only. | |
| sessions | A list of session objects, see the next table | |
| Property | Description | |
| hourOfDay | Session starting hour of the day
| |
| dayOfWeekend | Race weekend day / →Race Weekend Simulation:
| |
| timeMultiplier | Rate at which the session time advances in realtime.
| |
| sessionType | Race session type:
| |
| sessionDurationMinutes | Session duration in minutes |
- Remarks:
- At least one non-race session must be set up
- Setting up unreasonable day and hours ( also consider time multipliers ! ) can lead to wrong track and weather behaviour, e.g. avoid jumping from Saturday to Friday
eventRules.json
Defines the pitstop rules. Public MP servers will ignore this json file and use default values.
The basic pitstop features offer a huge array of combinations and different aspects you can set up your non-public races. Not every combination does make sense though, so it’s your responsibility to setup the rules so drivers have a good experience. It should be entirely possible to create a race in the style of a single Sprint series race as well as a 3-24h endurance race with or without driver swaps. Of course this shouldn’t limit you to think about your series and especially race event durations, and possibly add more fairness to balance fuel efficient cars – or allow a certain depth of tactics.
Additional notes regarding stints:
- Stint timer (top left corner in the timing HUD) is reset when the car crosses the pit entry and starts counting down again when crossing the pit exit.
- When serving a penalty, the stint timer will freeze and continue counting down after pit exit without resetting.
- When a player's total remaining driving time is less than his current stint time, the total driving time will override the stint timer (!).
When this happens, the stint timer's background turns red, indicating the final stint of the active driver.
| File Content | Property | Description |
|---|---|---|
|
{ |
qualifyStandingType |
Use 1, averaging Qualy is not yet officially supported. |
| superpoleMaxCar | Not currently listed or described in the Kunos Server Admin manual | |
| pitWindowLengthSec | Defines a pit window at the middle of the race. Obviously covers the Sprint series format.
| |
| driverStintTimeSec | Defines the maximum time a driver can stay out without getting a penalty. Can be used to balance fuel efficient cars in endurance races. The stint time resets in the pitlane, no real stop is required.
| |
| isRefuellingAllowedInRace | Defines if refuelling is allowed during the race pitstops.
| |
| isRefuellingTimeFixed | If set to true, any refuelling will take the same amount of time. If turned off, refuelling will consume time linear to the amount refuelled. Very useful setting to balance fuel efficient cars, especially if combined with other features. | |
| mandatoryPitstopCount | Defines the basic mandatory pit stops. If the value is greater zero, any car that did not execute the mandatory pitstops will be disqualified at the end of the race. The necessary actions can be further configured using the “isMandatoryPitstopXYRequired” properties. A value of zero disables the feature. | |
| maxTotalDrivingTime | Restricts the maximum driving time for a single driver. Is only useful for driver swap situations and allows to enforce a minimum driving time for each driver ( IRL this is used to make sure mixed teams like Pro/Am have a fair distributions of the slower drivers ). -1 disables the feature. | |
| maxDriversCount | In driver swap situations, set this to the maximum number of drivers on a car. The maxTotalDrivingTime property will be scaled down to apply to teams with less drivers. | |
| isMandatoryPitstopRefuellingRequired | Defines if a mandatory pitstop requires refuelling.
| |
| isMandatoryPitstopTyreChangeRequired | Defines if a mandatory pitstop requires changing tyres.
| |
| isMandatoryPitstopSwapDriverRequired | Defines if a mandatory pitstop requires a driver swap. Will only be effective for cars in driver swap situations; even in a mixed field this will be skipped for cars with a team size of 1 driver. | |
| tyreSetCount | Specify the number of permitted tire sets, 1-50 are possible. Not currently listed or described in the Kunos Server Admin manual |
assistRules.json
Can be used to turn off certain assists for any car connected to this server. Beware: disabling assists will effectively remove the effect, but there is no special handling how the assists look like in the menu. Without instructions, users will be surprised and confused – up to a point where they become a risk for other drivers. Whenever you think about disabling something, please be sure this is really necessary and a risk in terms of fairness. It is out of question that the ( quite strong ) driving aids “Stability Control” and “Autosteer” may be candidates for league racing, but just turning off the ideal line will not improve anything for anyone (except that the one driver using it may become less safe and ruins the race of others). Even innocent elements like auto-engine start and pit limiter may just force users to re-map their wheels, and for example lose the ability to use their indicators in lapping traffic – again nobody is winning in this scenario.
For (very) obvious reasons, public MP servers will ignore this json file and allow everything.
| File Content | Property | Description |
|---|---|---|
|
{ | ||
| stabilityControlLevelMax | Set’s the maximum % of SC that can be used. In case a client has a higher SC set than allowed by the server, he will only run what is allowed (25% in this example). Obviously setting this property to 0 removes all SC, including mouse and keyboard users.
The Stability Control is an artificial driving aid that allows the car to act out of the physics boundaries, and highly recommended to overcome input methods like Keyboards, Gamepads and Mouse steering. However, there is a built-in effect that makes the SC performance inferior, so in theory using (and relying) on SC is already more than enough penalty, and the way to improve performance is to practice driving without.
| |
| disableAutosteer | Disables the steering aid that is only available for gamepad controllers. Unlike SC, this works inside the physics and does not allow unrealistic driving behaviour – except that this is a very strong aid with superhuman feeling for grip and high reaction speed. There is a built-in penalty that should balance the driving performance in most cases, and give an incentive to learn not to use the driving aid.
| |
| disableIdealLine |
| |
| disableAutoPitLimiter |
| |
| disableAutoGear |
| |
| disableAutoClutch |
| |
| disableAutoEngineStart |
| |
| disableAutoWiper |
| |
| disableAutoLights |
|
entrylist.json
Using entry lists a server admin can setup special roles that link drivers (by Steam Id) to those configuration entries.
It allows the server to identify persons, and allows to force or allow various aspects. Entry list entries will always bypass Rating Requirements, and will be able to join servers even if they are full (as long as we have pit slots left, and the driver number is smaller than configuration.json/ maxClients).
To start, just add a new file called entrylist.json in the “cfg” folder. Using an entry list does not interfere with the classification of “Public” or “Private” MP, and you can selectively use an entry to e.g. reserve a slot for you in a Public MP server. Serious groups might use slots for their members and run a race with a 90 SA restriction in Public MP to fill up their rows with highly capable “randoms”.
| File Content Example: 1x Driver as Admin / 2 Drivers as Team |
Property | Description |
|---|---|---|
|
{ |
entries | List of entries |
| drivers | List of drivers, see next table. Must at least contain one driver with the SteamId | |
| raceNumber | The preferred race number add.
| |
| forcedCarModel |
| |
| overrideDriverInfo | If set to 1, the driver’s name and category will be overridden by what is setup in the entry list. If set to 0, it’s up to the client joining. | |
| customCar | If set to a filename, the car, team and appearance will be used no matter what the user chose ( Exception: overrideCarModelForCustomCar ). This is useful for leagues and events, where we want consistent car appearance and the chosen car model for the corresponding driver/team. The custom car file has to be located in a “cars” folder next to the entrylist.json ( also works for centralEntryListPath ). Leave blank ( “”, =default ) to let the user chose the car via car selection UI. | |
| overrideCarModelForCustomCar | If customCar is used, this setting will apply the car model configured if the value is set to 1 (which is the default). If set to 0, all values except the carModel are applied, so the user is free to pick a car but while team name and appearance will be applied. | |
| isServerAdmin | If set to 1, that user will be automatically elevated to server admin when he joins. | |
| defaultGridPosition | If set to a value of 1 or greater, this car will obtain this grid position if a race starts without any qualifying session before ( e.g. P -> R ). | |
| ballastkg | Assigns ballast in kg for this car. Will be additive to ballast for the car model ( via bop.json ), and can be overridden by the admin command /ballast. Range is 0 to 100. | |
| restrictor | Assigns restrictor in % for this car. Will be additive to restrictor for the car model ( via bop.json ), and can be overridden by the admin command /restrictor. Range is 0 to 20. | |
| forceEntryList | Will reject drivers that are not in the entry list. Default is 0, which allows the partial definition of entries in a “normal” server configuration. Cannot be used on public servers. | |
| For each entry in “drivers”, we will need at least the SteamId defining the entry. Other possible. values: | ||
| firstName | First name of the driver, if “overrideDriverInfo” is set to 1 | |
| lastName | Last name of the driver, if “overrideDriverInfo” is set to 1 | |
| shortName | Short name of the driver, if “overrideDriverInfo” is set to 1 | |
| driverCategory | Bronze / Silver / Gold / Platinum category, if “overrideDriverInfo” is set to 1. | |
| playerID | Steam64 Id for this client; Add a “S” in the front | |
bop.json
In addition to the admin commands and entry list based ballast and restrictor, you globally define those values for car and track combinations.
To accomplish this, just add a bop.json like this:
| File Content | Property | Description |
|---|---|---|
|
{ |
entries | |
| track | enter a Racetrack here | |
| carModel | enter a CarModel here | |
| ballast | Assigns ballast in kg for this car. Can be overridden by the admin command /ballast.
| |
| restrictor | Assigns restrictor in % for this car. Can be overridden by the admin command /restrictor.
|
Each “entry” can be understood as a line with a composite key of track and car model, and the ballast/restrictor are applied if both math. This way you can apply a small balance to one precise combination, or create your full blown custom BoP for all kinds of seasons, tracks and cars.
Important notes:
- The additional BoP is at the moment adjustable on public servers, but we will look at this closely. If we see bad and overdone efforts that affect the experience of average users, we will limit the additional BoP to private servers
- It is very hard to improve the current BoP, much harder than it may look (especially for 2019, where SRO did a great job). Do not fall for the mistake to use hotlap performance as the reference, and also make sure to start with tiny adjustments.
The values of the bop.json act additive to the entry list, so you can combine a championship penalty with your track/car specific changes. Any admin command (/ballast or /restrictor) will set the corresponding value to whatever you define, and overwrite potential configurations until the car rejoins.
Result Files
Using the “dumpLeaderboards”: 1 option, any session that is finished will write the final standing into a .json file in the “results” folder. Those files are generated with a filename in the pattern of “190806_193009_R.json”, including date, time and session type (P, Q, R).
| File Content |
|---|
|
{ |
In a nutshell, the root object contains information about the session and track, next to a leaderboard representation, a complete list of laps and a complete list of penalties for this session. The properties should be self-explanatory, in case of doubts and questions please do not hesitate to join the official support forum.
Spectator Mode
The necessary server settings: The difference between "maxConnections": 40; ( configuration.json ) and "maxCarSlots": 30; ( settings.json ) defines How many seats are available on the server. In this case, it is 10.
Now only one password has to be assigned. This must be different than what is stated for the accession of the driver. Check also:
- configuration.json / maxConnections
- settings.json / spectatorPassword
- settings.json / maxCarSlots
If someone wants to join a server as a spectator, he must enter the password for the spectator mode.
ID Lists
| 2018 | 2019 |
|---|---|
| barcelona | barcelona_2019 |
| brands_hatch | brands_hatch_2019 |
| kyalami_2019 | |
| laguna_seca_2019 | |
| hungaroring | hungaroring_2019 |
| misano | misano_2019 |
| monza | monza_2019 |
| mount_panorama_2019 | |
| nurburgring | nurburgring_2019 |
| paul_ricard | paul_ricard_2019 |
| silverstone | silverstone_2019 |
| spa | spa_2019 |
| suzuka_2019 | |
| zolder | zolder_2019 |
| zandvoort | zandvoort_2019 |
| Value | Car Model |
|---|---|
| 0 | Porsche 991 GT3 |
| 1 | Mercedes AMG GT3 |
| 2 | Ferrari 488 GT3 |
| 3 | Audi R8 LMS |
| 4 | Lamborghini Huracan GT3 |
| 5 | Mclaren 650s GT3 |
| 6 | Nissan GT R Nismo GT3 2018 |
| 7 | BMW M6 GT3 |
| 8 | Bentley Continental GT3 2018 |
| 9 | Porsche 991.2 GT3 Cup |
| 10 | Nissan GT-R Nismo GT3 2017 |
| 11 | Bentley Continental GT3 2015 |
| 12 | AMR Vantage V12 GT3 |
| 13 | Lamborghini Gallardo R-EX |
| 14 | Jaguar G3 |
| 15 | Lexus RC F GT3 |
| 16 | Lamborghini Huracan GT3 Evo (2019) |
| 17 | Honda NSX GT3 |
| 18 | Lamborghini Huracan SuperTrofeo |
| 19 | Audi R8 LMS Evo (2019) |
| 20 | AMR V8 Vantage (2019) |
| 21 | Honda NSX Evo (2019) |
| 22 | McLaren 720S GT3 (Special) |
| 23 | Porsche 911 II GT3 R (2019) |
| Value | Category |
|---|---|
| 3 | Platinum |
| 2 | Gold |
| 1 | Silver |
| 0 | Bronze |
| Value | Category |
|---|---|
| 0 | Overall |
| 1 | ProAm |
| 2 | Am |
| 3 | Silver |
| 4 | National |
| Value | Session Type |
|---|---|
| 0 | Practice |
| 4 | Qualifying |
| 10 | Race |
Admin Commands
While connected to a server ( both as driver and spectator ), users can elevate to “server admins” if they are aware of the password. That allows them to use a few special commands. Version 1.0 start with a limited set, which is expected to be extended in future versions. To elevate to admin, hit “enter” to use the chat and type /admin adminPw123. A notification will tell you if successful. Additionally, you can setup an “Entry lists” entry for the admin(s) steamids.
| Command | Number | Description |
|---|---|---|
| /next | Skips the current session | |
| /restart | Restarts the current session. Do not use this during the preparation phase | |
| Insert a space between the command and the start number / Kg / % | ||
| /kick | 1 to 998 | Kicks a user from the server, preventing him to join again until the race weekend restarts |
| /ban | 1 to 998 | Bans a user from the server, preventing him to join again until the server restarts |
| /dq | 1 to 998 | Instantly disqualifies the car, teleporting it to the pits with locked controls |
| /clear | 1 to 998 | Removes pending penalties ( e.g. Drivethrough or Stop&Go ) |
| /clear_all | clears all penalties from all cars | |
| /sg10 | 1 to 998 | + 10 seconds stop&go penalty |
| /sg20 | 1 to 998 | + 20 seconds stop&go penalty |
| /sg30 | 1 to 998 | + 30 seconds stop&go penalty |
| /tp5 | 1 to 998 | + 5 seconds penalty time ( reusable ) |
| /tp5c | 1 to 998 | + 5 seconds penalty time + Indication of the reason: collision ( reusable ) |
| /tp15 | 1 to 998 | + 15 seconds penalty time ( reusable ) |
| /tp15c | 1 to 998 | + 15 seconds penalty time + Indication of the reason: collision ( reusable ) |
| /dt | 1 to 998 | Assigns a drivethrough penalty to the given car. As other DTs, it has to be served within 3 laps or the car will become disqualified. In case of a race finish within those 3 laps, the DT will be transformed to a 80s time penalty. |
| /dtc | 1 to 998 | see dt + Indication of the reason: collision ( reusable ) |
| /ballast | 1 to 998 + kg |
Sets the car’s ballast (in kg) to what you defined. This overrides any other ballast this car has been assigned.
|
| /restrictor | 1 to 998 + % |
Sets the car’s restrictor (in %) to what you defined. This overrides any other restrictor this car has been assigned.
|
| /manual entrylist | Manually creates an entry list json file containing the drivers connected in this moment. See also settings.json / dumpEntryList | |
| /debug formation | Prints information about the current cars and their states. Useful information to report bugs during the formation lap | |
| /debug bandwidth | Let’s the server console print the current bandwidth relevant data for both TCP and UDP traffic. Type again to turn it off | |
| /debug qos | Let’s the server console print the current network connection quality data. Type again to turn it off. | |
References
- test your configurations with an Online Syntax Check.
- Server Admin Handbook (PDF) - find in ACC Install under ..:\Steam\steamapps\common\Assetto Corsa Competizione\server
- Server Admin Handbook (Forum) - https://www.assettocorsa.net/forum/index.php?threads/the-server-admin-handbook-thread.59017