Restarts & monitoring
Plan restarts and use monitoring to understand the server’s health.
Scheduled restarts
Configure a restart schedule in the panel. Check the displayed next-restart time against the host’s clock and timezone before relying on it. Tell your community when routine downtime occurs.
The upstream event reference describes announcements at 30, 15, 10, 5, 4, 3, 2, and 1 minute before scheduled restarts. Resources can listen for txAdmin:events:scheduledRestart, which includes secondsRemaining and translatedMessage.
Save data deliberately
If your framework needs an explicit save before a restart, integrate using its current server-side API and test the timing on a staging server. The historical ESX sample in the upstream reference is version-specific; do not copy it into a different framework unchanged.
txAdmin:events:serverShuttingDown also signals shutdowns with a delay, author, and message. Events are notifications, not a guarantee that a resource was online to receive them.
Crash and hang recovery
Automatic recovery is useful when FXServer crashes or becomes unresponsive. Repeated restarts indicate an underlying problem. Inspect Live Console and logs for the first failure, missing dependency, or stalled resource.
Tune boot grace periods only after measuring normal startup. Increasing timeouts can hide a broken boot without solving it.
Read the charts
Use the server thread performance chart with player count and CPU/RAM readings to compare periods. A change under a different player count is not a controlled benchmark. Check resource-level behavior with your game’s profiling tools when needed.
For event payloads and deprecated names, see Events broadcasted. For recovery checks, use Crashes & restart loops.
Source: txAdmin upstream documentation.