Back up a FiveM server or restore a player by asking the chat

A player says the last restart ate his inventory. The restore screen is a few clicks away, but you can also write in the chat in the corner of fivedock.dev: “restore Kowalski from six hours ago”. FiveDock’s support chat runs on FiveBot, and for a signed-in user it can check your servers, start a backup, restore one player and change settings.

What you can ask

• “Is my server online?” Each server’s agent and its last backup, answered straight away.
• “Back up the main server.” A card with the server name and a Run button. Owners and admins can do this.
• “Restore Kowalski from six hours ago.” One player from the latest backup at or before that time. Only the owner can, on Metro and up.
• “Keep daily backups for 60 days.” One setting changed through the same save code the panel uses.
• “Add a cron monitor for the nightly restart”, “invite Marta as an admin”, “delete the old alert”. A Manage FiveDock card.

The chat knows which servers you have and which one is open in the panel, so it fills in the server itself. When it can’t tell, it asks one short question and names the choices.

Restoring one player by name

You can give the player’s name instead of the license. FiveDock looks the name up in that server’s Black Box events from the last 90 days. One match restores that license, and the reply names both. Two or more and it asks which license you mean. No match and it asks for the license, which you can copy from Players.

The restore then runs like one started in the panel. FiveDock takes a safety backup first. If you are the only owner, the restore starts right away; if the workspace has another owner, it waits for their approval in Backups. When a restore can’t run, the chat says why in one sentence: the agent is offline, the player is still on the server, Live ops is off, or the plan is below Metro.

What a player restore puts back, and how to do it by hand, is in restoring one player’s inventory.

Settings and the rest of the panel

The chat reads your workspace and server settings and changes one at a time: how long backups are kept, inventory, Live ops, the server kind, observability, the command policy, the workspace name and its language. It saves through the same code as the panel, so the same roles, ranges and plan limits apply. Ask for 91 days of daily backups on a plan that keeps 90 and it tells you the plan doesn’t allow it.

Manage FiveDock covers the rest: alerts and where they are sent, cron monitors, economy rules, upload portals, Discord events, members and invitations, ingest keys, the backup mirror and your plan. It can also revoke API tokens and agent keys.

What stays in the panel

• The chat acts only for a user signed in to fivedock.dev. On Discord, or signed out, it tells you where to sign in.
• Anything that hands out a secret stays in the panel: new API tokens and agent keys, webhook URLs, mirror access keys and the backup key. The chat sends a link to the right page.
• Backups, restores and Manage FiveDock changes show a card first and run when you press Run.
• Every change made from the chat is in the audit log as FiveBot chat.

The same from a terminal

The FiveDock CLI does the same from a shell. fivedock status lists the latest snapshots, and a player restore takes the license instead of the name:

fivedock status main
fivedock backup main --agent
fivedock restore main <snapshot> --scope player --ref <license>

Common questions

Which plan do I need?

Server status, backups and settings work on every plan. Restoring one player needs Metro or Enterprise, as it does in the panel.

Can I undo a player restore?

FiveDock takes a safety backup before the restore starts, so you can restore the player again from that backup if you picked the wrong time.

What if the player is online?

The restore doesn’t start. The framework would save what the player holds in memory over the restored rows, so the chat asks you to wait until they are offline.