Raids, Nuking & Coordinated Disruption
Do not organise, join, recruit for, advertise, request, fund, celebrate, or provide targets for a raid, server nuke, mass-ban campaign, channel destruction, permission takeover, webhook flood, invite abuse, mass spam event, coordinated false-report campaign, or denial-of-service attack.
Do not ask for or distribute raid tools, nuking bots, stolen bot tokens, compromised accounts, bypass methods, destructive scripts, target lists, attack schedules, malicious configuration files, or step-by-step instructions that would materially enable abuse.
Merely claiming that an attack group exists, posting recruitment slogans, displaying attack statistics, sharing trophies from damaged communities, or repeatedly discussing whom to target can create fear and normalise abuse. Staff may act before an attack begins when the context shows recruitment, preparation, intimidation, or a credible risk.
Do not test anti-raid, anti-nuke, moderation, verification, rate-limit, or recovery systems without explicit authorisation from the responsible owner. Permission for one limited test does not authorise unrelated targets, greater impact, persistence, or retention of access.
Defensive and educational discussion is allowed only when it is clearly framed around prevention, recovery, or authorised testing and omits unnecessary operational detail. Vulnerabilities, exposed credentials, and suspected attack plans must be reported privately to authorised staff.