Auto-start and Auto-shutdown

Schedule Auto-start and Auto-shutdown for selected days in the timezone that matches your group's routine.

Create or change a schedule

  1. Open the server's Automation section.
  2. Select at least one active day.
  3. Choose the timezone used to interpret the times.
  4. Enter an Auto-start time, an Auto-shutdown time, or both.
  5. Select Save schedule.

Leave a time empty to turn that action off. A schedule with neither action enabled does not run. The same times apply to every selected day.

Auto-start preconditions

At the scheduled time, Auto-start behaves like pressing Start:

  • If the server is already active, the occurrence is skipped.
  • If the server is Stopped with Banked Hour remaining, that paid time resumes.
  • If no Banked Hour remains, the owner must have enough credits for one full hour.
  • If the owner's balance is too low, the server stays Stopped and that occurrence fails.

A failed occurrence is not retried continuously. The schedule advances to its next selected day, so top up before the next Auto-start or start the server manually after adding credits.

Auto-shutdown preconditions

At the scheduled time, Auto-shutdown behaves like pressing Stop:

  • If the server is already Stopped, the occurrence is skipped.
  • If it is Running, shutdown begins and the status changes to Stopping.
  • Save data is preserved through the normal stop process.
  • Billing pauses when the server reaches Stopped, and unused paid time becomes Banked Hour.

Auto-shutdown does not permanently delete the server.

Timezone and daylight changes

Schedule times use the timezone selected in Automation, not necessarily the timezone of the person who later opens the Console. Choose the location whose local clock should control the schedule. Future occurrences follow that timezone's clock changes.

Permissions and lifecycle conflicts

Only viewers allowed to edit the schedule can save it; others see a read-only schedule. A scheduled action does not interrupt another lifecycle transition. Check the Automation result and server status if an expected occurrence was skipped or failed.