Skip to content
Mamba Host Docs

Assetto Corsa Competizione Setup

Assetto Corsa Competizione (ACC) demands stable CPU frequency, fast NVMe storage for replays, and robust networking for dynamic weather endurance events. Mamba Host delivers all three via Dell PowerEdge R630 hardware (dual Intel E5-2680v4, 128 GB RAM) plus tooling for entry lists, BoP, and driver swaps.

Before You Begin

Section titled “Before You Begin”
  • Download the latest server_cfg.json, event.json, and entrylist.json templates.
  • Determine whether you’re running Sprint, Endurance, GT4, or mixed-class racing.
  • Gather custom liveries and ensure they follow ACC’s checksum requirements.
  • Decide on weather presets, time acceleration, and mandatory pit-stop rules.

Plan Selection

Section titled “Plan Selection”

Specs are stored in src/games/game-server-products.ts. Use this guide:

Event TypeRecommended PlanGrid Size
Private practice / ≤12 carsStarterSolo practice or coaching
Community races (16–24 cars)ProWeekly leagues, public servers
Endurance (24–32 cars + driver swaps)PremiumLong events with dynamic weather

Upgrade when CPU latency spikes during rain/night transitions or when replays consume >80% of allocated storage.

Provision the Server

Section titled “Provision the Server”
  1. Go to https://panel.mambahost.com → Create Server → Assetto Corsa Competizione.
  2. Choose plan, region, and deploy (≈2 minutes).
  3. Grab SFTP credentials and default JSON configs from /cfg.
  4. Enable automated backups before uploading custom entry lists.

Configure Championship Settings

Section titled “Configure Championship Settings”
  • Edit server_cfg.json to set trackMedalsRequirement, safetyRatingRequirement, and maxClients.
  • Define sessions inside event.json (practice/quali/race, time multiplier, weather, cloud level, random factor).
  • Populate entrylist.json with teams, car models, race numbers, and ballast values. Include multiple drivers for endurance swaps.
  • Set BoP adjustments, ballast, and restrictors per car as needed.

Weather & Time Control

Section titled “Weather & Time Control”
  • Use time multipliers for accelerated day/night cycles; e.g., timeMultiplier: 6 for 4-hour events.
  • Combine static and dynamic weather: set cloudLevel, rain, weatherRandomness.
  • Schedule restarts between events to archive race results and replays.

Operations Checklist

Section titled “Operations Checklist”
  • Run a short shakedown before official sessions to ensure everyone has the required liveries.
  • Stream via Broadcast mode or third-party overlays; ACC supports remote broadcast clients.
  • Use the built-in results export to track championship points.
  • For endurance leagues, script driver swap reminders via Discord bots hitting the panel API/webhooks.
  • Publish BoP adjustments and steward rulings after each race so teams can review changes.
  • Version-control server_cfg.json, event.json, and entrylist.json in git for rapid rollback if rulesets break mid-season.
  • Archive replay files (.json + .tmp) to object storage—they are invaluable for protests.

Troubleshooting

Section titled “Troubleshooting”
  • Clients rejected for checksum mismatch: ensure custom liveries are deployed to /Customs and that entrylist.json references the correct folder names.
  • Weather not changing: confirm isFixedConditionQualified/isFixedConditionRace flags are false when you want randomness.
  • Driver swaps failing: all drivers must be assigned to the entry and present on the server; verify forcedCarModel matches their game garage.
  • Ping spikes during rain: reduce grid size or upgrade to Premium; dynamic weather plus headlights increases CPU usage.
Section titled “Helpful Links”