Honeypot

A honeypot is a channel you hide from honest members and leave visible to anyone who digs around the server list. Bots and raiders find it, post in it, and get punished on sight. Nobody who is meant to be there ever types in one, so a message in it is close to proof.

Every honeypot command needs Administrator (real or fake).

Adding one

,honeypot add #staff-tools ban

The punishment is required and must be one of three words:

Adding the same channel again just updates its punishment.

softban is the polite option for a human who wandered in. jail needs a role set up first, see below.

Managing them

,honeypot list
,honeypot remove #staff-tools

The jail role

,honeypot jailrole @Jailed

Required before a channel can use the jail punishment. The role has to sit below bore's top role, and @everyone cannot be used as a jail role. If it is not set, or set too high, the jail punishment fails and the log says so.

Staff who are allowed to post there

,honeypot staffrole @Moderator

Members with this role are skipped entirely. Use it if your own team legitimately posts in the channel you chose as bait, though picking a channel nobody uses is cleaner.

Omit the role to clear it.

Logging

,honeypot logchannel #mod-logs

Every trigger posts who did it, what the punishment was, and whether it succeeded. Without a log channel you will not see anything happen.

Checking the setup

,honeypot settings

Shows the log channel, staff role and jail role, with "Not configured" for anything you have not set.

Making it work

A honeypot only catches people who can find it. Practical version:

1. Create a channel with an inviting name, something a bot would post spam into.
2. Hide it from @everyone with ,hide #that-channel, then unhide it for a specific permission override so invited bots still see it, or leave it visible to everyone but out of every sensible channel list.
3. ,honeypot add #that-channel softban.
4. ,honeypot logchannel #mod-logs so you know when it fired.