guildsave.app

Restore guide

A raid, a deleted channel, a permission change gone wrong: here is how to get your server back.

1. Find the right snapshot

Run /snapshots or open Dashboard → Snapshots. Pick the last snapshot from before the damage and note its ID.

2. Dry-run first

/restore id:42 dry_run:true

Shows which roles and channels would be created and which ones are not in the snapshot. Nothing changes yet.

3. Restore

/restore id:42

Before anything is touched, Guild Save seals a safety snapshot of the current state. Then it:

  • creates roles and channels that are missing,
  • updates roles and channels that differ from the snapshot,
  • sets each channel’s permission overwrites again.

Roles and channels are matched by name (channels also by type).

4. Remove what the raid added (optional)

/restore id:42 prune:true

Also deletes roles and channels that are not in the snapshot, for example spam channels from a raid.

Careful: prune deletes for real. Always look at the dry-run first.

Undo a restore

Every restore writes a safety snapshot first. It is labelled “pre-restore” and marked Safety in the dashboard. Restore that one to go back.

What a restore does not bring back

  • Messages, pins and threads. They are never part of a snapshot.
  • Which member had which role. The roles come back, the assignments do not.
  • Webhooks and integrations, and roles managed by other bots.

Only the same server: a snapshot can be restored into the server it was taken from. Moving to a new server is covered in the migration playbook.

If something fails

The reply lists errors per role or channel. The usual cause: the Guild Save role sits below the roles it should edit. Move it up in Server settings → Roles and run the restore again. It only changes what still differs.