Honeypot
Spam bots post everywhere they can. A honeypot is a bait channel your members are told never to use, so anyone who posts in it is almost certainly a bot or a hacked account, and Skipper removes them instantly.
/config Category dropdown Moderation Honeypot. Toggle the module on first.How it works
You pick one public channel as the honeypot. Skipper posts a live message in it warning members not to type there. When someone sends anything at all in that channel, their message is deleted and the action you chose (softban, ban, kick or mute) is applied straight away. Every catch is counted, optionally logged, and shown on the live message so members can see the trap working.
Nuking bots is only half the point. Because compromised accounts blast their scam link into every channel they can see, a honeypot usually catches them before they reach the channels your members actually read.
Set up your honeypot
- Create (or pick) a public text channel. Bait names work best, something like
#free-nitro,#giveaway-claimor#trading. Put it near the top of the channel list so bots hit it first. - Leave @everyone able to view and send in it. A locked channel catches nothing, the trap only works if a bot is able to post.
- Choose Channel and select it. Skipper needs View Channel, Send Messages, Read Message History and Manage Messages there.
- Set the Action. Softban is the default and the recommendation, see below. Tick DM if you want the caught user told why it happened.
- (Optional) Set a Log channel so staff can review every catch.
- (Optional) Add staff to the Whitelist so nobody gets punished for testing it.
Choosing an action
| Action | What happens |
|---|---|
| Softban (recommended) | Bans and instantly unbans, which removes the user and deletes their last 7 days of messages. A real member whose account was hacked can rejoin once they recover it. |
| Ban | Permanent ban, also deleting their last 7 days of messages. |
| Kick | Removes the user. They can rejoin, and their messages are left in place. |
| Mute | A 24-hour timeout. Nothing is removed, so the account stays in the server. |
Whatever you pick, the honeypot message itself is always deleted, and the audit-log reason records that the user was caught by the honeypot.
The live message and catch stats
The live message sits in the honeypot channel and updates itself with a Caught button. Anyone can press it for a private breakdown of how many users were banned, softbanned, kicked and muted, plus when the last catch happened.
Reference: all settings
| Setting | What it does |
|---|---|
| Channel | The bait channel. Text or announcement channels only, and it cannot be the log channel. |
| Action | Kick, softban, ban or mute a user who posts, plus a DM toggle to tell them why. |
| Log | Where catches are logged: the user, their account age, the action and what they posted. |
| Message | The live warning message with the running catch counter. |
| Whitelist | Up to 25 roles and users the honeypot ignores completely. |
Troubleshooting
| Problem | Fix |
|---|---|
| Nothing is ever caught | Check @everyone can actually send messages in the channel, and that the module is toggled on. |
| A real member got caught | Turn the live Message on so the warning is visible, and give the channel an obvious bait name. |
| Skipper reports missing permissions | It needs Manage Messages in the honeypot channel, plus Ban Members, Kick Members or Timeout Members for your chosen action. |
| A moderator was not removed | Skipper cannot action anyone whose top role sits above its own. Move Skipper’s role higher. |
| Nothing appears in the log channel | Give Skipper View Channel, Send Messages and Embed Links there. The log channel cannot be the honeypot channel. |
| The live message is missing | Skipper needs Send Messages and Read Message History in the honeypot channel. Toggle Message off and on to repost it. |