跳到内容
全部指南

Schedules and Discord notifications

Restart your server automatically and get crash alerts in your league's Discord.

Scheduled restarts

Long-running servers like a fresh start now and then. Open your server → Schedules → Add schedule, then pick:

  • Action - restart, stop, start or update the game.
  • Days and time, in the timezone you choose (daylight saving is handled for you).

Good to know:

  • If we can’t run a schedule on time (for example during maintenance), it’s skipped if it would be more than 10 minutes late - we never restart your server late into a race.
  • Turn on Only when the server is empty to leave drivers alone. The server is checked every minute for up to the wait you choose; it runs the moment nobody is connected. If players are still there when the wait ends it is skipped, or runs anyway if you chose that.
  • If we can’t tell who is connected (live data is off, degraded or not arriving), the server is never treated as empty: the run waits, then is skipped. Only Run even if players are unknown overrides that. AC EVO has no in-game messages, so players can’t be warned first.
  • A scheduled restart also applies any changes waiting for a restart (plan changes, staged config).
  • Every run (or skip) shows in the Activity log.

Restart before an event

In the Schedules tab, Restart before events restarts the server a set number of minutes before a scheduled event starts, so it is up and loaded at the start. It only restarts if nobody is connected (and never if we can’t tell, unless the event is set to force the restart), and only once: at the start time the event is already loaded. You can override the time per event. Postponed, skipped and completed restarts all show in the Activity log.

Discord notifications

  1. In Discord: Server Settings → Integrations → Webhooks → New Webhook, choose the channel, then Copy Webhook URL.
  2. In Pitwall: your server → Settings → Discord notifications, paste the URL, tick the events you want and Save. Use Send test to check it arrives.

Events include crashes, recoveries, the server coming online or stopping, losing contact with the machine it runs on, schedules, plan changes and billing suspensions.

If Discord says the webhook no longer exists, notifications switch off and the card tells you why.