Ludicrous BotLudicrousBot
Backups

Backups

One snapshot per server, stored by server ID, covering the channel layout, every role with its permissions, and all Ludicrous Bot configuration. Creating a new snapshot replaces the previous one.

Overview

Ludicrous Bot stores this module as structured server configuration. The Discord bot worker should read the saved guild settings, watch the relevant Discord events, and apply the behavior described by each field.

Before You Start

Test changes in a staff channel first, especially when roles, punishments, or message deletion are involved.

Required Discord Permissions

  • Server owner or a Ludicrous Bot co-owner for every backup action: create, view, export, restore, and delete
  • Administrator is deliberately not enough, in Discord or on the dashboard, so a staff account cannot destroy the snapshot it would be recovered from
  • Manage Roles and Manage Channels for the bot, with its role above the roles it recreates

Setup Steps

  1. Open Backups in the dashboard, or run ,backup in your server to get the control panel.
  2. Press Create backup. The snapshot captures roles, channels, overwrites, emojis, stickers, bans, member roles, and every guild-scoped bot setting.
  3. To restore, use the panel in Discord: pick a scope, then confirm.
  4. Choose merge to only recreate what is missing, or clean to also delete channels and roles that are not in the backup.

Dashboard Instructions

  1. Open the server dashboard.
  2. Select this module in the sidebar.
  3. Review warnings and empty states.
  4. Save once the preview matches your desired behavior.

Example Use Cases

  • Take a snapshot before a large permissions rewrite, then restore settings only if it goes wrong.
  • Rebuild a server after a raid by restoring structure, then everything.
  • Export the JSON with ,backup export to keep an offline copy.

Troubleshooting

  • Roles at or above Ludicrous Bot's highest role can never be created or edited. Move the bot's role up before restoring.
  • Permissions the bot does not itself hold are dropped from restored roles rather than failing the restore. The completion report lists which roles were affected.
  • Integration and booster roles are managed by Discord and are skipped.
  • A restore rewrites saved channel and role IDs to the new objects, so settings like the jail role or log channel keep working after a rebuild.

FAQ

Why can I not restore from the dashboard?

Restoring rewrites roles, channels, and permissions for several minutes and cannot be undone. It stays behind the in-Discord panel so the server owner confirms it directly.

How many backups are kept?

One per server. Snapshots are keyed by server ID, so creating a new one replaces the old one.

Is member data included?

Role assignments and bans are, capped for very large servers. History is not: moderation cases, warnings, XP, balances, tickets, and analytics are all excluded. A backup restores how the server is set up, not what happened in it.