Auto Nuke

Auto Nuke recreates Discord channels on a schedule so message history is cleared while permissions, category, topic, slowmode, and related settings stay the same. You configure rules in the Antidote dashboard; a server cron job queues work and the bot performs each nuke when the interval elapses.

What happens when a channel is “nuked”

1. Antidote captures the channel’s settings (name, type, topic, NSFW, bitrate / user limit for voice, slowmode, category, permission overwrites, position).
2. Depending on your disposition, it may create a hidden archive copy first (see below).
3. It creates a new channel with those settings, then deletes the old channel.
4. Antidote updates database references so dashboard setups (welcomer, collectors, command channel limits, automod log channels, tickets, voice control, and similar) point at the new channel ID instead of the deleted one.

Dispositions

Mode (dashboard)	What the bot does
Recreate only	Deletes the channel and recreates it with identical settings. No archive copy.
Archive then recreate	Creates a hidden archive channel (timestamped name, e.g. general-archive-2026-06-04 08-30), then recreates the live channel. Only roles you select can view the archive.

Archive mode options

• Roles that can view archives — Required. At least one role must be selected; those roles get View Channel and Read Message History on the archive copy. Everyone else (including @everyone) is denied view on the archive.
• Archive category (optional) — Discord category where archive copies are placed. If empty or invalid, Antidote uses an existing category named auto-nuke-archives or creates one (hidden from @everyone).

Archive channels are not wired into welcomer, collectors, or other setups—they are read-only history for staff.

Schedule intervals

Each rule runs on a rolling timer from the last successful auto nuke (last_auto_nuke_at), not a fixed clock time.

Interval	Minimum time between runs
Hourly	1 hour
Daily	24 hours
Weekly	7 days
Monthly	30 days

Disabled rules are skipped. The dashboard shows Last run when a rule has completed at least once.

After each automatic nuke

When the bot finishes successfully, the API records:

• last_auto_nuke_at — timestamp for the next interval check
• channel_id — updated to the new live channel ID so future runs target the correct channel
• last_archive_channel_id — set when archive mode was used
• archive_category_id — refreshed if the bot resolved or created a category

[!tip] Scheduled rules stay in sync You do not need to re-select the channel in the dashboard after each auto nuke—the stored channel ID is updated automatically.

Manual !nuke command

Moderators can also nuke immediately with the nuke command (aliases: nuke). It recreates the current channel or a channel you mention, with a confirmation button and the same setting preservation as auto nuke.

• Permissions: Manage Channels for both the member and Antidote.
• Allowed types: Text and voice channels only.
• Blocked: System / rules / community update channels.
• Database remap: Manual nuke calls /servers/remap-channel-id so other Antidote features keep working.

What database references are remapped

Channel remap runs for this server when IDs change, including (among others):

• Command channel limits and module limited_to JSON
• Welcomer / leaver channels
• Interaction collectors
• Tickets and ticket archive channels
• Voice join channels and voice interaction channels
• Crosschat, streamer alerts, automod log channels
• Voice control personal / hub channel IDs where stored

Collectors, ticket panels, and other in-channel Discord content (messages, buttons on old messages) are not recreated—only IDs in Antidote’s database are updated.

Bot permissions (checklist)

Antidote needs enough power to delete and recreate channels and to manage archive visibility:

• Manage Channels — delete, create, and position channels
• View Channel / Connect (as needed) on the channels you nuke
• Manage Roles — not required for basic recreate, but archive overwrites apply role visibility
• For archive mode, the bot must be able to create channels in the chosen category and set permission overwrites

If the bot lacks permissions, the queue task fails, last_auto_nuke_at is not advanced on failure, and the rule may retry when the channel still exists.

Managing rules in the dashboard

1. Click Add channel and pick a text or voice channel.
2. Set Enabled, interval, and disposition.
3. For archive mode, choose roles and optionally an archive category.
4. Click Save all (rules are stored server-wide in one save).
5. Use Edit / trash on each row to change or remove rules before saving.

You can configure multiple channels per server, each with its own schedule and disposition.

Related

• Dashboard — Auto Nuke under server management.
• nuke moderation command — on-demand recreation with confirmation.
• Antinuke — separate protection against mass channel deletes; does not replace Auto Nuke.
• Server logging — optional; pair with moderation logs if staff should see when channels were recreated.