Ventura

Loading a backup

/backup load id: → confirmation → progress → result. Only the server owner, and the bot needs Administrator - both checked again at every click. A backup of another server first asks for its transfer code (6a).

The confirmation#

  • Mode (only for backups of this server): Replace server or Repair only (see 7). Backups of other servers can only replace.
  • Contents (multi-select, all preselected): Emojis, stickers & sounds · Nicknames & roles · Bans · Threads & messages · Keep an undo copy. Structure and settings are always loaded.
  • Shows what will be deleted, what will be created, roles that stay in place (above the bot's role) and an estimated duration. Valid for 10 minutes, works once, ends when the bot restarts.

What happens, in this order#

  1. Undo copy (if selected) - the server is read like a backup and stored (8).
  2. Delete - all channels except the one the load runs in, and all roles the bot may manage. Kept: @everyone, roles above the bot's role, the bot's own roles, and roles managed by Discord (bots, boosters).
  3. Server settings - name, levels, AFK timeout, icon, banner, invite background.
  4. Roles - recreated from top to bottom. Roles that still exist on the same server (kept ones) are reused; bot and booster roles are mapped to their counterparts on the target server.
  5. Categories & channels - with permissions and settings. Then Community (rules and updates channel), announcement channels, system and AFK channel. If a single setting fails, the channel is created without it.
  6. Emojis, stickers & sounds (if selected) - see 10.
  7. AutoMod, welcome screen & onboarding - see 11.
  8. Nicknames & roles of members still on the server.
  9. Bans - applied in bulk.
  10. Threads & messages - see 9.

Progress and result#

  • The progress shows every step with counts, a bar and the remaining time.
  • The result lists what was restored and everything that isn't as in the backup - with the reason where it helps (e.g. "the bot's role is too low", Discord's limit of 250 roles). Too many for the message → attached as a text file.
  • Bots to invite again: bots that were on the backed-up server but aren't on this one, each with an invite link that asks for the permissions it had and preselects the server. For a few very old bots (from before 2017) the link may not work - invite those from their own website. Their channel permissions don't come back automatically.
  • Buttons: Undo (if an undo copy was kept) and Delete this channel (the channel the load ran in wasn't part of the backup).
  • The interaction expires after 15 minutes. For long loads the result is posted into the channel instead, and the owner gets a DM when it's done. Loads of 10 minutes or more always end with a DM.

If the bot restarts in the middle#

A load, repair or undo doesn't stop halfway for good when the bot restarts - for an update, after a crash or a reboot of its machine. After the restart, the bot continues it by itself: it posts "Continuing after a restart" in the channel the load ran in (mentioning the owner) and runs it again from the start with a new progress display. That gives the same result as an uninterrupted run:

  • Replacing deletes everything the first attempt created anyway.
  • Repairing finds roles, channels and emojis by their ID in the backup - what the first attempt recreated has a new one. So before the repair starts over, the bot removes exactly what the first attempt created: roles, categories, channels, emojis, stickers, sounds and AutoMod rules, and the messages it had reposted into existing channels. Nothing exists twice afterwards. Channels it had refilled are refilled again, even if members wrote something meanwhile.

The undo copy taken before the first attempt stays; no new one is taken. After three interrupted attempts, the bot gives up and says so in the channel - an interrupted repair is removed like before continuing it, so it can simply be started again.