How It Works
The actual logic behind the trap and the moderation flow.
The core loop
Spammers (or compromised accounts) typically blast every visible channel. Honeypot works because the trap channel is visible and looks ordinary, so their automation hits it and gets caught.
A trap channel is defined
/honeypot.Message is detected
Optional DM is sent
Action runs
Log + counter update
Action details
Softban uses a ban/unban sequence to remove the last hour of messages. Ban removes the user permanently and also clears their recent messages.
Honeypot bans and softbans instead of timeouts or role quarantine because bans delete the spammer's recent messages - the alternatives leave the spam in place. This also keeps those accounts out of your server, where they can't mass DM members.
Softban is default
Edge cases
Honeypot is conservative and logs failures clearly:
Server owner
Missing permissions
Flow diagrams
For the sequence of events, commands and buttons in more detail, see the flow diagrams. They show the path each action takes, with short notes where the logic needs more context.