Bot Commands
Parrot & Pinger Backups
Save and restore parrots and role pingers using a backup ID
Blaze backups save all parrot and role pinger configurations for your server, including source channels, destination channels, roles, positive and negative keywords, and pinger cooldown settings.
You need Manage Server permission and Blaze owner/staff access or the Blaze role. Backup IDs and restore previews are visible only to the person running the command.
Blaze saves the backup and gives you a backup ID. Create one before rebuilding your server or making major changes. Backups are stored by Blaze and survive deletion of the Discord server.
Blaze also checks for changes once a day while the bot is running, with an initial check when the bot starts. A new automatic backup is saved only when the configuration or referenced structure has changed. Older backups are retained. Missing channels or roles prevent a new backup from being saved; existing backups remain available.
This lists the 20 most recent backups, their IDs, timestamps, and whether they were created manually or automatically. An older backup can still be restored using its saved ID.
Blaze checks the current server and shows a preview. If all references match, click Restore parrots and pingers within 10 minutes. The requester must still have access when confirming.
Existing channel and role IDs are used when they still exist in the original server, so ordinary renames do not break those references. When IDs have changed, channels are matched by category name, channel name, and channel type; roles are matched by name. Names are case sensitive. Channels without a category must still be outside a category.
If multiple channels or roles match, Blaze reports the problem instead of choosing one. Correct the structure or remove the ambiguity and run restore again. Roles managed by another bot or integration cannot be matched by name; recreate the pinger’s role configuration manually if its original managed role no longer exists.
Restoring updates configurations with the same Blaze parrot/pinger IDs and adds missing configurations. Unrelated configurations remain. A destination already assigned to a different parrot blocks restoration. Repeating a restore does not create duplicates. All configuration changes are committed together, and Blaze checks again for changes before applying the restore.
Pinger cooldown durations are restored. A changed pinger starts with fresh cooldown timers; an already restored, unchanged pinger keeps its current timers.
This command restores Blaze configurations. Your server restoration tool must recreate channels, roles, permissions, and other server content. Ensure Blaze can still access the channels and send messages. Monitor webhook setup and personalized user pingers (PUPs) are outside this backup.
You must have the required access in the replacement server and either have created the manual backup yourself or retain Blaze owner/staff membership for the original server. A backup ID alone does not grant access. Contact support if the original server’s account membership is no longer available.