Messages
Send server-wide announcements or focused player messages at the right moment, then verify the delivery outcome.
Choose the audience
Use a global message for information every connected player needs, such as a planned restart or event status. Use a private message for onboarding, guidance or a player-specific administrative conversation.
Write for the in-game context
- Put the important information first.
- Keep the text short enough to read during play.
- Use a clear time and timezone for planned events.
- Avoid internal team notes or sensitive account information.
- Use consistent language for warnings and maintenance notices.
Automated triggers
GAdmin supports configured messaging around server and player events, including server startup or player join flows. Choose private or global delivery according to the purpose, add any intended delay and verify the trigger against a controlled test.
A saved message definition does not prove that BattlEye accepted a later delivery. Review the recent outcome and investigate repeated failures through agent and RCON health.
Recommended restart sequence
- Create advance notices appropriate to the maintenance impact.
- Confirm the scheduler's next-run time.
- Send a final short notice immediately before the action.
- After startup, confirm server health and send a return-to-service message when appropriate.
- Review delivery and restart outcomes together.
Troubleshooting delivery
If messages remain pending or fail, confirm the player is still online for private delivery, then check agent status, RCON health and the operation result. Avoid creating duplicate automations while the original failure cause is unknown.