A trap channel that does not ban on sight. The message is deleted, the poster gets a card explaining what happened, and a timer starts: one click clears them, silence bans them. Far fewer false positives than an instant ban, and the panel keeps a running count of who got caught.
This preset can kick, ban, or time out members
Install only if you trust it. Review the placeholders below before enabling it on your server.
What it does
The trigger and the actions it runs. Values in grey are what you'll pick when installing.
Rule 1 · When
Message sent
Matchesany message
In Honeypot channel
Ignoring roles Exempt roles
Rule 1 · Then · step 1
Delete the message
Applies tothe trigger message
ReasonPosted in the honeypot channel
Rule 1 · Then · step 2
Add to counter
Variablehoneypot_pending
Storedper member
By1
Rule 1 · Then · step 3
Only if step 2's value is 1 — otherwise the rule stops here
Send a message
Channelthe trigger channel
Rule 1 · Then · step 4
Send a message
Channel Log channel
Message🍯 <@{user.id}> ({user.name:escape}, `{user.id}`) tripped the honeypot in {channel.mention}.
> {message.content:truncate(300):escape:default(no text, an attachment or an embed)}
Rule 1 · Then · step 5
Only if step 3 succeeded — otherwise the rule stops here
Wait (cancellable)
Wait Grace period
Rule 1 · Then · step 6
Delete the message
ReasonHoneypot warning resolved
Rule 1 · Then · step 7
Ban member
Applies tothe member who triggered it
ReasonPosted in the honeypot channel and did not clear it
Delete history1 hour
Rule 1 · Then · step 8
If step 7 succeeded
Send a message
Channel Log channel
Message🔨 Banned <@{user.id}> ({user.name:escape}, `{user.id}`) — posted in the honeypot and never cleared it.
Rule 1 · Then · step 9
Add to counter
Variablehoneypot_bans
Storedonce for the whole server
By1
Rule 1 · Then · step 10
Otherwise
Send a message
Channel Log channel
Message⚠️ Could NOT ban <@{user.id}> ({user.name:escape}, `{user.id}`) after they tripped the honeypot (`{steps.7.error_code}`). Check FlaviBot's Ban Members permission and its role position.
Rule 1 · Then · step 11
Only if step 9's value is set
Edit the message
Rule 2 · When
Button click
Rule 2 · Then · step 1
Cancel a pending wait
Rule 2 · Then · step 2
If step 1 failed
Reply privately
Message⚠️ We could not process that right now. Please tell a moderator before the timer runs out.
Rule 2 · Then · step 3
Send a message
Channel Log channel
Message⚠️ <@{user.id}> ({user.name:escape}, `{user.id}`) pressed "It was a mistake" but the request could not be processed (`{steps.1.error_code}`). Their ban is still armed.
Rule 2 · Then · step 4
Otherwise, if step 1's cancelled is true and step 1 succeeded
Reply privately
Message✅ You're clear. Please avoid that channel from now on.
Rule 2 · Then · step 5
Send a message
Channel Log channel
Message🙋 <@{user.id}> ({user.name:escape}, `{user.id}`) tripped the honeypot and cleared themselves in time.
Rule 2 · Then · step 6
Delete data
Variablehoneypot_pending
Storedper member
Rule 2 · Then · step 7
Edit the message
Applies tothe trigger message
Rule 2 · Then · step 8
Wait (cancellable)
Wait30
Rule 2 · Then · step 9
Delete the message
Applies tothe trigger message
ReasonHoneypot warning resolved
Rule 2 · Then · step 10
Otherwise
Reply privately
MessageThere is nothing pending for you any more. This warning was either already resolved, or the timer just ran out.
Rule 3 · When
Button click
Rule 3 · Then · step 1
Read data
Variablehoneypot_bans
Storedonce for the whole server
Rule 3 · Then · step 2
If step 1 succeeded
Reply privately
Message🔨 Caught so far: **{vars.bans.value}**
Rule 3 · Then · step 3
Otherwise
Reply privately
MessageThe count is unavailable right now. Try again in a moment.