Skip to content

Assetto Corsa Competizione Setup

Host your Assetto Corsa Competizione server for GT3/GT4 racing with dynamic weather, endurance events, and driver swap support. This guide covers setup, championship configuration, and league operations.


PlanBest ForDriver Capacity
StarterPrivate practice, solo or coaching sessions~10 drivers
ProWeekly leagues, community races, public servers~20 drivers
PremiumEndurance events, driver swaps, dynamic weather~30 drivers

  1. Create your server

    Go to panel.mambahost.comCreate ServerAssetto Corsa Competizione

  2. Select your plan and deploy

    Choose your plan and region — deployment completes in about 2 minutes

  3. Download your config files

    Get SFTP credentials and default JSON configs from /cfg

  4. Enable backups

    Configure auto-backups before uploading custom entry lists

  5. Configure and start

    Edit your championship settings and launch the server


FilePurpose
server_cfg.jsonServer name, requirements, max clients
event.jsonSessions, weather, time multiplier
entrylist.jsonTeams, cars, drivers, ballast
  1. Edit server_cfg.json — set trackMedalsRequirement, safetyRatingRequirement, and maxClients

  2. Define sessions in event.json — practice, qualifying, race, weather conditions

  3. Populate entrylist.json — teams, car models, race numbers, ballast values

  4. Configure BoP adjustments — ballast and restrictors per car as needed

  5. Include multiple drivers for endurance swap events


  • Short practice, qualifying, and race sessions
  • Single-driver entries
  • Standard weather conditions
  • Extended sessions with driver swaps
  • Time multipliers for day/night cycles (e.g., timeMultiplier: 6 for 4-hour events)
  • Dynamic weather with rain transitions
  • GT3, GT4, and Porsche Cup combined
  • Separate BoP configurations per class
  • Custom entry lists for each class

// event.json weather example
{
"cloudLevel": 0.3,
"rain": 0.2,
"weatherRandomness": 3,
"ambientTemp": 22,
"trackTemp": 30
}
SettingDescription
cloudLevel0.0 (clear) to 1.0 (overcast)
rain0.0 (dry) to 1.0 (heavy rain)
weatherRandomness0-7, higher = more variation
timeMultiplierAccelerates day/night cycle

TaskRecommendation
Run shakedown sessionsVerify liveries before official races
Version control configsStore JSON files in git for rollback
Archive replay filesEssential for protests and highlights
Publish BoP adjustmentsShare steward rulings after each race
Script driver swap remindersUse Discord bots for endurance events
  1. Use Broadcast mode or third-party overlays for streaming

  2. Export results via the built-in results system for championship tracking

  3. Archive replays (.json + .tmp files) to object storage

  4. Schedule restarts between events to archive data and clear memory


  1. Create liveries in ACC’s livery editor

  2. Deploy to /Customs folder via SFTP

  3. Reference in entrylist.json with correct folder names

  4. Run a shakedown to verify all drivers have required liveries


RecommendationWhy
Reduce grid size during rainDynamic weather increases CPU load
Schedule restarts between sessionsArchives data and clears memory
Use static weather for large gridsMore stable performance
Test weather transitions offlineCatch issues before race day

ProblemSolution
Checksum mismatchEnsure custom liveries are deployed to /Customs with correct folder names
Weather not changingConfirm isFixedConditionQualified/isFixedConditionRace are false
Driver swaps failingAll drivers must be assigned to entry and present on server
Ping spikes during rainReduce grid size or upgrade to Premium
Entry list errorsVerify forcedCarModel matches driver’s game garage