Plan once, keep control
Routine administration should not depend on someone remembering the same checklist every day. GAdmin's scheduler gives supported server actions a clear time, day and timezone. Active state and the next planned run remain visible, and an administrator can edit, disable or remove the schedule when conditions change.
Automation is useful precisely because it is repeatable. It should also stay inspectable. GAdmin keeps schedules in the same workspace as the server, so the team does not have to search another service to learn why a restart or message occurred.
Operations that match real server routines
- Recurring restart plans with visible timing.
- Global or targeted messages around important events.
- Supported lock, unlock and player-management actions.
- Saved locations, equipment kits and operational templates.
- Clear active state and recent execution outcomes.
Communicate before and after
A restart is not only a technical action; it is also a player communication event. Message automation can welcome a player after joining, send a global notice after startup or deliver a private message when the configured trigger occurs. Recent delivery history shows whether the operation completed successfully.
Use templates for consistent manual work
Not every action should run on a timer. Saved operations let an experienced administrator define a known location, kit or supported sequence once and make it ready for deliberate use later. The team still chooses when to run it, but the important parameters no longer need to be reconstructed from memory.
Scheduled and saved operations still pass through backend plan, permission and payload validation. A timer is not a path around the workspace security model.
Frequently asked questions
Can I see when a schedule runs next?
Yes. The scheduler is designed to show active state and next-run timing directly in the task list.
Can an automation be paused?
Supported scheduled tasks can be disabled and later re-enabled without recreating the full definition.
Does automation require the GAdmin Agent?
Remote server operations need a healthy control path to the server. Depending on the operation, that includes the paired GAdmin Agent and working RCON configuration.