Skip to content
Mamba Host Docs

Assetto Corsa Setup

Assetto Corsa servers on Mamba Host are tuned for Content Manager (CM), Custom Shaders Patch, and large mod libraries. Backed by Dell PowerEdge R630 hardware (dual Intel E5-2680v4, 128 GB RAM, NVMe storage), you get fast session transitions, reliable tick rates, and unlimited mod storage.

Before You Begin

Section titled “Before You Begin”
  • Collect car/track mods, CSP configs, and entry lists you intend to run.
  • Decide on server type: public track day, drift lobby, time attack, or structured league.
  • Prepare server_cfg.ini, entry_list.ini, and weather/presets (Sol, Pure).
  • If you run multiple layouts, create a plan for rotation so resources are uploaded once.

Plan Selection

Section titled “Plan Selection”

Plan specs live in src/games/game-server-products.ts. Use this guidance:

Use CaseRecommended PlanNotes
Private testing / ≤12 driversStarterGreat for setup sessions, touge runs
Public lobbies / drift servers (16–24 drivers)ProExtra CPU headroom for heavy smoke & CSP effects
Leagues / events (24–32 drivers)PremiumHandles large grids, live timing, and safety cars

Upgrade when CPU exceeds 75% during races, or when uploads push storage above 80%.

Provision the Server

Section titled “Provision the Server”
  1. Visit https://panel.mambahost.com → Create Server → Assetto Corsa.
  2. Choose region and plan, then deploy (≈2 minutes).
  3. Download the autogenerated cfg files from /server.
  4. Configure backups before importing large mod packs.

Upload Mods & Configs

Section titled “Upload Mods & Configs”
  • Upload tracks to /content/tracks/<track_name> and cars to /content/cars/<car_name>.
  • Place server_cfg.ini and entry_list.ini in /cfg.
  • Use SFTP for large mod collections; keep folder names consistent with Content Manager.
  • Restart the server after uploading to rebuild the checksum list.

Content Manager Workflow

Section titled “Content Manager Workflow”
  • In CM, go to Server → New Server and point it at your Mamba Host instance via FTP.
  • Use CM to edit sessions (practice/quali/race), ballast, penalties, and weather.
  • Export directly to the server via FTP or download the pack and upload manually.

Drift & Touge Tips

Section titled “Drift & Touge Tips”
  • Enable loop_mode=1 for infinite sessions.
  • Increase CLIENT_SEND_INTERVAL_HZ if you want smoother proximity for tandem runs.
  • Limit grid size based on track width to prevent spawn collisions.
  • Use scripts from Modded Assetto Corsa Traffic Servers Guide to populate AI traffic on open roads.

League Operations

Section titled “League Operations”
  • Automate race weekends with CM presets that include practice, quali, race, and reverse-grid formats.
  • Use live timing tools (simresults, Rivals overlay) hosted externally and connect via HTTP.
  • Schedule restarts and backups between sessions to preserve results.
  • Version control server_cfg.ini/entry_list.ini to roll back after rule tweaks.
  • Store steward decisions and penalty logs in Discord or spreadsheets for transparency.

Live Operations & Maintenance

Section titled “Live Operations & Maintenance”
  • Publish weekly schedules and rotate layouts via CM presets.
  • Keep CSP/Sol versions consistent between server and community; announce required versions in Discord.
  • Snapshot mods before major championship rounds so you can reissue the exact build if disputes occur.
  • Automate safety car deployments or restart votes by integrating CM’s HTTP API with Discord bots.

Troubleshooting

Section titled “Troubleshooting”
  • Checksum mismatch: ensure every driver has identical car/track versions; delete data.acd overrides when not needed.
  • CSP conflicts: align server CSP version with client recommendations; disable unsupported features for public lobbies.
  • Mods not visible: confirm folder names match exactly and that server_cfg.ini references the right layout string.
  • Performance drops with smoke/weather: reduce max clients or move to Pro/Premium so physics threads stay ahead.
Section titled “Helpful Links”