Skip to content

Assetto Corsa Setup

Host your Assetto Corsa server with Content Manager integration, Custom Shaders Patch (CSP) support, and unlimited mod storage. This guide covers setup, drift/touge configurations, and league operations.


PlanBest ForDriver Capacity
StarterPrivate testing, setup sessions, touge runs~8 drivers
ProPublic lobbies, drift servers, heavy smoke & CSP effects~16 drivers
PremiumLeagues, events, large grids, live timing~24 drivers

  1. Create your server

    Go to panel.mambahost.com → Create Server → Assetto Corsa

  2. Select your plan and deploy

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

  3. Download default configs

    Get the autogenerated cfg files from /server

  4. Configure backups

    Enable backups before importing large mod packs

  5. Upload mods and start

    Add your tracks and cars, then start the server


  1. Upload tracks to /content/tracks/<track_name>

  2. Upload cars to /content/cars/<car_name>

  3. Place config files (server_cfg.ini, entry_list.ini) in /cfg

  4. Use SFTP for large mod collections — keep folder names consistent with Content Manager

  5. Restart the server to rebuild the checksum list


  1. Open Content Manager → Server → New Server

  2. Point CM to your Mamba Host instance via FTP credentials

  3. Configure sessions — practice, qualifying, race, weather, and penalties

  4. Export directly to the server via FTP or download and upload manually

  5. Test the connection from your game client


  • Open sessions for casual driving
  • Enable loop_mode=1 for infinite sessions
  • Good for testing and social driving
  • Increase CLIENT_SEND_INTERVAL_HZ for smoother tandem proximity
  • Limit grid size based on track width to prevent spawn collisions
  • Enable infinite sessions for continuous practice
  • Automate race weekends with CM presets (practice, quali, race, reverse-grid)
  • Use live timing tools (simresults, Rivals overlay)
  • Schedule restarts between sessions to archive results

FilePurpose
server_cfg.iniServer name, sessions, track, car list
entry_list.iniDriver entries, car assignments, ballast
welcome_message.txtMessage shown to joining drivers
; server_cfg.ini example
[SERVER]
NAME=My AC Server
TRACK=spa
CARS=ks_ferrari_488_gt3;ks_porsche_911_gt3_r
MAX_CLIENTS=16
LOOP_MODE=1

TaskRecommendation
Version control configsStore server_cfg.ini and entry_list.ini in git
Archive replaysInvaluable for protests and highlights
Schedule backupsBetween sessions to preserve results
Announce CSP/Sol versionsKeep server and community versions aligned
Document steward rulingsStore decisions in Discord or spreadsheets

RecommendationWhy
Use CSP versions matching your communityPrevents compatibility issues
Reduce max clients if smoke/weather causes lagHeavy effects increase CPU load
Schedule restarts between eventsClears memory and archives data
Pre-test mod packsCatch issues before race day

ProblemSolution
Checksum mismatchEnsure every driver has identical car/track versions
CSP conflictsAlign server CSP version with client recommendations
Mods not visibleConfirm folder names match and server_cfg.ini references correct layout
Performance drops with smoke/weatherReduce clients or upgrade plan
Entry list errorsVerify car names match exactly in entry_list.ini