Scheduled restarts on a FiveM server

#Setting the schedule

1. Open txAdmin → Settings → Restarter.
2. Add restart times in 24-hour format, for example 06:00, 14:00, 22:00.
3. Save. The next restart time appears on the dashboard.

#Saving data before the restart

AddEventHandler('txAdmin:events:scheduledRestart', function(data)
    if data.secondsRemaining == 60 then
        -- one minute left: save everything
        SaveAllPlayers()
    end
end)

AddEventHandler('txAdmin:events:serverShuttingDown', function(data)
    -- data.delay = ms before txAdmin kills the process
    SaveAllPlayers()
end)

SaveAllPlayers stands for your framework’s save function. serverShuttingDown fires for every stop or restart — scheduled, by an admin, or by the system — so it is the safest single place to save.

#Skipping and temporary restarts

From the dashboard an admin can skip the next scheduled restart (for an event running late) or schedule a one-off restart. Skips broadcast txAdmin:events:scheduledRestartSkipped, so a countdown UI can hide itself.

#Crash recovery

txAdmin monitors the server and restarts it when it crashes or stops responding. If it restarts often, read the console and crash logs instead of relying on it — see txAdmin setup.

#How often is right?

Every 6–8 hours suits most servers. If performance falls apart between restarts, a resource is leaking entities or memory: profile it rather than restarting more often — see server performance and entity limits.