Assetto Corsa Server.cfg: Tracks, Sessions and Rules

An Assetto Corsa server.cfg file sets the core rules for a multiplayer server: which track and layout it runs, which cars are available, how sessions progress, and what driving conditions and limits apply. It works alongside other server files, especially entry_list.ini and event-specific configuration, so not every setting a player sees is controlled by server.cfg alone.

What server.cfg controls

Assetto Corsa’s dedicated server reads configuration files in its server configuration folder when it starts. The main server.cfg file describes the event and server behavior; its exact options can vary with the server build and the configuration template supplied with the game. Treat the template installed with your version as the authority for supported keys rather than copying a configuration from an unrelated server.

Most settings are written as key-value pairs under named sections. A typical file uses sections such as [SERVER], [PRACTICE], [QUALIFY], [RACE], and [WEATHER]. Section names organize settings; they are not decorative headings. A misspelled key, misplaced value, or unsupported option may be ignored or cause the server to fail to load the configuration, depending on the setting and build.

The file is not a complete description of every server feature. The server’s entry list can determine which cars and driver slots are used, while other files or hosting tools can manage additional event details. If a server’s displayed behavior does not match a value you changed, check all relevant configuration files and the hosting panel before assuming server.cfg is being read.

Tracks, layouts, and car availability

The track setting identifies the circuit folder the server should load. A layout or configuration value, where the track supports alternate layouts, selects a particular version of that circuit. These are identifiers used by the game, not necessarily the track names as shown in a launcher. Use the exact names present in the installation and verify that every machine or client joining has compatible content.

A configuration can point to a valid track but still fail if the track is missing, its layout name is wrong, or the server and clients do not have compatible content. Custom tracks also need to be installed correctly on the server; changing a text value does not install or distribute the track. For a public event, state the required track and layout clearly so participants can check them before joining.

Car selection is commonly governed through the server’s entry-list setup, rather than by assuming one server.cfg line will fully define the grid. Entries can identify allowed cars and driver slots, and may include team or skin information depending on the setup. Confirm the syntax in the supplied entry-list example. If you want a restricted roster, test with the intended car list instead of relying on the server browser’s description.

Sessions and the event sequence

Sessions determine what drivers do and in what order. A common event sequence is practice, qualifying, and race, but a server can be configured for different combinations. The relevant sections set options such as session duration, while race settings can use a lap count or another supported race-length option. Use the matching setting from the installed template: do not assume a time value and a lap value are interchangeable.

• Practice: gives drivers time on track before the timed or competitive part of the event.
• Qualifying: establishes a qualifying session and, where configured, the starting order for the race.
• Race: defines the main contest, including its configured length and applicable rules.

Check how session transitions are configured and whether the server waits for a scheduled start or advances automatically. A short practice period may be useful for a casual event, but a longer session gives participants time to connect, set up controls, and learn the circuit. Confirm the final sequence from a test run; the in-game session display is more useful than assuming a setting name means what it does in another server version.

Weather and track conditions

Weather settings define conditions such as ambient temperature, road temperature, and the weather type or progression, when those options are supported by the server configuration. Values may be entered in a weather section or in a format described by the template. Read each field’s expected units and allowed values carefully; a number intended as a temperature is not a percentage, and a weather identifier may not be free-form text.

Some setups use multiple weather points or progression to change conditions during an event. In that case, a single displayed weather value may not tell the whole story. Check the full weather configuration and confirm how the server build interprets its entries. Conditions can affect grip and driving feel, so make them part of the event announcement rather than surprising drivers after they connect.

Weather configuration is separate from choosing a track. A valid circuit does not guarantee that every weather option is valid for that server version. Start with a known-good template, change one condition at a time, and verify the result in an actual session.

Server rules, limits, and driving aids

Server.cfg can set practical multiplayer rules such as the server name, password, capacity, voting behavior, and penalties or driving aids, depending on the available options. These controls affect access and event behavior, but they do not replace a human-readable rulebook. Explain expectations such as track limits, contact, rejoining after a spin, and whether assists are allowed in the server description or event instructions.

• Use a password when an event should be limited to invited participants, and share it through an appropriate channel.
• Set capacity to a level the server and event can support, then verify that the entry list provides the intended slots.
• Choose voting and penalty options deliberately; permissive settings can make a casual lobby easier to manage but may not suit a competitive race.
• Check allowed assists and damage or fuel-related options against the event format and the exact keys supported by your template.

A server setting cannot guarantee fair driving. Penalties may respond to game-defined conditions, but they do not judge every incident or settle disputes. For organized racing, publish stewarding and conduct expectations separately and make clear how participants should report problems.

Editing and troubleshooting safely

Before changing the file, make a copy of the working configuration. Edit plain text without changing the file extension, preserve section headers, and avoid adding punctuation or comments unless the format supports them. If you use a hosting control panel, remember that it may generate or overwrite configuration files; make edits in the panel or follow its instructions so your changes persist.

1. Stop the server before editing files that it reads at startup.
2. Use the installed server template to confirm section names, key spelling, value format, and valid choices.
3. Change one group of settings at a time, such as track selection or session length.
4. Save the file, restart the server, and inspect its log for configuration or content-loading errors.
5. Join a test session and verify the track, session sequence, weather, and rules in-game.

If the server does not start, first check for a missing track or layout, a typo, a malformed value, or a mismatch between the configuration and the server build. If a setting appears to have no effect, confirm that you edited the active file and that a hosting panel did not replace it. Avoid treating a community example as universal: templates and supported options can differ.

Frequently Asked Questions

Where is Assetto Corsa server.cfg?
It is part of the dedicated server’s configuration files. Its precise location depends on how the server was installed or hosted. Find the active server directory or use the hosting panel’s file manager, then confirm that the file is the one the running server loads.

Does server.cfg select the cars?
It may define general server behavior, but the entry list is commonly where individual car entries and driver slots are configured. Check both files and the template for your server build.

How do I change the track layout?
Set the track and supported layout identifiers to the exact values used by the installed content. Confirm the layout exists on the server and that participants have compatible track content.

Why did my server.cfg change not work?
The server may be using another file, the edited key may be unsupported or misspelled, or a hosting tool may overwrite your change. Check the startup log, active configuration path, and installed template.

Can I set changing weather for a race?
Some configurations support weather progression or multiple weather entries. The accepted format and behavior depend on the server’s options, so follow its template and test the conditions in a session.

Is server.cfg enough to explain race rules?
No. It configures supported server behavior, but drivers also need clear event instructions for conduct, track limits, incident handling, and other expectations that the file does not fully express.

Related

• AI Cloud vs On-Premises GPUs: Which Costs Less?
• Is CVS Trying to Be More Like Costco and Marshalls?
• Abyss Tier List: How to Rank Characters and Teams