$snipe /snipeRecover a deleted message
Shows the most recently deleted message in the current channel. BigBrother also attempts to preserve images, GIFs and other attachments.
$snipeRun it in the channel where the message was deleted.
BIGBROTHERBY ZEROTECH
DISCORD SECURITY / MODERATION / OPERATIONS
Your server’s digital watchdog. Anti-nuke, anti-raid, AutoMod and accountable moderation—built as one coherent system, not a pile of plugins.
QUICK ACCESS / 05 ESSENTIALS
Five commands worth knowing before you need them. Prefix examples use $; each command also has the matching slash interface.
$snipe /snipeShows the most recently deleted message in the current channel. BigBrother also attempts to preserve images, GIFs and other attachments.
$snipeRun it in the channel where the message was deleted.$report /reportSends a reasoned report to the configured reports channel. The log identifies the reporter and target; count checks do not expose reporters.
$report @member reasonA reason is required. Slash: choose the member and enter the reason.$purge /purgeClears recent messages with tiered staff limits. You can optionally limit deletion to messages from one member.
$purge 20 [@member]Requires moderation permissions; slash offers amount and member fields.$nuke /nukeSnapshots the current channel, asks for confirmation, then deletes and recreates it with its configuration preserved.
$nukeAdministrator only. Confirm in the 30-second safety prompt.$nukeserver /nukeserverSnapshots categories and channels, requests explicit confirmation, then reconstructs the channel tree. Partial failures are reported and a five-minute guild cooldown prevents repeat execution.
$nukeserverAdministrator only. Review the confirmation carefully before proceeding.Windowed signals identify raids, floods and destructive bursts before they become cleanup work.
Permission checks, hierarchy rules, confirmations and cooldowns guard every consequential action.
Cases, incidents and audit correlation preserve context—without fabricating an executor when Discord cannot verify one.
PROTECTION MATRIX / 06 SYSTEMS
From routine moderation to emergency lockdown, every module shares the same permission, service, state and logging layers.
Detects destructive bursts and join raids, raises verification, quarantines new arrivals and preserves the original server state for a controlled unlock.
Configurable rules for spam, mentions, repeated text, character floods, invites, GIF bursts and server-specific word filters.
bw aliasesBan, kick, timeout, warn, purge and channel lock with native permission checks and hierarchy-aware enforcement.
Separate MODLOG, SERVERLOG, ANLOG and reports channels. Audit-log correlation shows who acted whenever Discord can prove it.
/say recordsMembers report with a required reason; staff see reporter, target and context while public checks reveal counts only.
Interactive reaction-role setup, autoroles and an enforced Blacklisted role that preserves access to ticket-style resolution channels.
EVENT PIPELINE
BigBrother does not split detection, punishment and evidence across disconnected systems. A shared action engine carries the event from signal to permanent record.
Rate windows, content rules, join velocity and audit events.
Permissions, hierarchy, whitelist and reliable executor lookup.
Delete, warn, timeout, quarantine, lock or escalate.
Case, incident, timeline and the correct destination log.
ESCALATION POLICY
A report is not just a message in a channel. It is a persistent signal that can drive a controlled, reversible access response.
$report or /report requires a reason and logs reporter + target.
$checkreports exposes only the total—not the identities behind it.
At 10+, roles are stripped and the managed Blacklisted role is applied.
Chat is blocked except ticket-style channels; the member receives a DM.
OPERATOR-GRADE DETAILS
Small reliability decisions are what keep a moderation system useful when the server is busy, degraded or under attack.
Deletes and log sends back off after Discord 429 or Cloudflare 1015 responses instead of hammering a blocked route.
Timeouts and quarantines are stored so temporary enforcement survives process restarts.
Deleted images, GIFs, video and audio attachments are recovered where possible—with honest failure text when they are not.
Detection and logging can remain live while destructive actions are skipped for safer testing and deployment checks.
If audit data cannot establish an executor, BigBrother reports “Unknown / unavailable.” It never invents a name.
Both interfaces call the same service layer, preventing command behavior from drifting across two implementations.
A concealed owner safeguard can run a high-volume channel simulation and restore it. It stays outside slash commands and public help, supports protected channel IDs, and is intentionally absent from the command directory below.
COMMAND DIRECTORY
Search the public command surface. Prefix commands use $ by default and can be changed per server.
The owner-only simulation and revert triggers are intentionally not exposed here, in slash commands, or in BigBrother help.
ARCHITECTURE
Command handlers only parse input and present results. Business logic lives in shared services; database access stays inside repositories.
MEMBER UTILITIES
Public avatar, banner, profile, roles, account age and server lookups sit beside invite stats, welcome hooks, coinflip, latency and uptime. Admin tooling should reduce friction—not only respond to disasters.
$ status ✓ Anti-Nuke active · Anti-Raid armed / security status ✓ raid mode inactive · ANLOG routed $ case 184 ✓ timeout · actor verified · reason attached / panel ✓ opening staff control panel…
DEVELOPED BY ZEROTECHBIG BROTHER IS ALWAYS WATCHING
No music. No filler. Security, moderation, logging and the admin tools needed to operate a Discord server with context.