Before you start
You need the exact game-server assignment and schedule-writing permission. For a world wipe, you also need explicit authority for its displayed reset scope and a verified recovery point.
What to do
- Open the intended game server and Schedules. Review existing managed schedules and native action sequences, including enabled state, time zone, next action and any pending countdown or running action.
- Use Add schedule or Edit for the intended managed schedule. Choose its action, selected days or one-time date, action times and explicit time zone. Review the warning and run-only-when-online choices where offered.
- For an existing native sequence, review its own time zone, cron fields and action offsets before editing its start timing. Preserve the sequence's commands and offsets unless you intend to change that work through the appropriate controls.
- For a supported world wipe, read What this wipe resets in full, including reset data, preserved material and player-account handling. Use the required confirmation only for that intended server and scope; do not assume another server has the same wipe policy.
- Save, reload the list and inspect the next action in the schedule's stated time zone. Use Run history to distinguish a completed, missed or failed action from the saved schedule configuration.
- Use Pause or Enable for future scheduling and inspect any pending action separately. Delete schedule removes future runs while retaining completed run history; review its confirmation before submitting.
What happens next
You can inspect the accepted schedule and the outcome of its individual actions. The interface explains that missed actions are recorded rather than automatically performed late; a wipe's outcome remains tied to its own displayed policy and operation result.
If something goes wrong
Check the schedule's time zone, selected days, online-only choice, next time, pending countdown and run history before creating another schedule. Editing or pausing can be unavailable while an action is executing. Stop and contact the infrastructure administrator if the reset scope or account-retention warning is unclear; never test a destructive action merely to resolve a display question.
