Honey Pot
Honey Pot is an optional moderation feature that treats a dedicated channel as a trap. When a member who is not exempt posts there, the bot deletes the message and applies your chosen action
Any new message can trigger the trap, including attachment-only messages and posts in the selected channel's threads. Use a dedicated channel with a clear warning, rather than a normal conversation channel.
Set up through the dashboard
The trap is active once its enabled settings are saved. Posting the warning is a separate action; enabling Honey Pot does not automatically publish one.
Bot permissions
Delete trap messages
View Channel and Manage Messages in the trap channel.
Time out members
Moderate Members.
Kick members
Kick Members.
Ban members
Ban Members.
Post or update the warning
View Channel, Send Messages, Read Message History and Attach Files. Threads use Send Messages in Threads and must be accessible, active and unlocked.
Deliver logs
View Channel and Send Messages in the selected log channels.
The bot's role must be above the member it needs to moderate. Discord's normal moderation restrictions still apply.
Configure using YAML
Edit the existing HoneyPot section in config/modules/moderation.yml. Keep the rest of the moderation file. Do not add a second HoneyPot: key or wrap the section in Moderation:.
This example times out members for five minutes, sends results to a log channel, and provides a simple warning with live statistics. Replace both example channel IDs before saving. Keep Discord IDs in quotation marks.
HoneyPot:
Enabled: true
Channels:
- "123456789012345678" # Dedicated trap channel.
BypassRoles: []
BypassPerms:
- ManageMessages
Action: Timeout
TimeoutTime: "5m"
LogsChannelID:
- "234567890123456789" # Staff log channel.
Warning:
Components:
- Type: container
AccentColor: "#F5B73B"
Components:
- Type: text_display
Content: |-
## Do not send messages here
This channel is a security trap.
Your message will be deleted and {consequence}.
This includes attachments and posts in this channel's threads.
- Type: separator
Divider: true
Spacing: small
- Type: text_display
Content: |-
**Do not test the trap.** Use the server's regular chat channels.
Kicked: {kicked} · Banned: {banned} · Timed out: {timedOut}
Triggers: {triggers} · Last triggered: {lastTriggered}
- Type: text_display
Content: '-# {guildName} · Automated moderation'To keep the supplied warning with the honey pot illustration, retain your existing Warning block instead of replacing it with the text-only design above.
Valid module YAML changes reload automatically during normal bot operation. Saved per-server settings take precedence over the local defaults, so use the dashboard for a server that already has its own moderation settings. After changing the warning or action, use Post warning to update the message members see.
Without the dashboard, the trap can still be configured in YAML. Post a clear warning yourself in each trap channel; the Warning design is published through the dashboard's posting control.
Settings reference
Enabled
Turns Honey Pot on or off. The default is false.
Channels
List of trap channel IDs. At least one is required when enabled. Selecting a parent channel also covers its threads.
BypassRoles
Members with any listed role are exempt. Use [] for no role-based exceptions.
BypassPerms
Members with any listed Discord permission are exempt. The default includes ManageMessages. Use permission identifiers such as ManageMessages, without spaces.
Action
Timeout, Kick or Ban. The default is Timeout; values are case-sensitive.
TimeoutTime
Timeout duration, from "1s" to "28d". The default is "5m". Only affects the Timeout action.
LogsChannelID
Optional list of additional log channels. Use [] to disable dedicated Honey Pot logs. Shared automatic moderation logs still apply.
Warning
The warning's component message design. Edit it in the dashboard or under Warning.Components in YAML.
Warning messages and statistics
The dashboard's Warning message design editor lets you change the text, colour, images and layout. Its preview uses sample statistics; the posted warning uses this server's actual values.
{consequence}
A description of the selected punishment, such as “you will receive a timeout,” with Discord formatting.
{action}
The configured action name: Timeout, Kick or Ban.
{guildName}
Server name.
{channelMention}
Mention of the warning's destination channel.
{kicked}
Successful Honey Pot kicks.
{banned}
Successful Honey Pot bans.
{timedOut}
Successful Honey Pot timeouts.
{triggers}
Non-exempt trap triggers, including triggers during the punishment cooldown and failed actions.
{lastTriggered}
Last trigger as a Discord relative timestamp, or Never if there have been none.
Post warning updates the existing tracked warning instead of adding another copy. If that warning was deleted, posting again creates a replacement. Warning message references and statistics persist across restarts.
Warnings containing statistics refresh automatically, with updates grouped every 30 seconds. These refreshes retain the last posted design and action; they do not publish an unposted design or recreate a deleted warning. Post again after changing the design or punishment so the warning stays accurate.
Statistics are server-wide. Successful actions remain counted even if a moderator later reverses them. Earlier successful Honey Pot cases can contribute to the totals, but older failed or cooldown-only triggers cannot be reconstructed.
Logs and member notices
Honey Pot sends successful action results and action failures to its LogsChannelID destinations and the shared AutoModeration.LogsChannelID destinations. A channel in both lists receives one copy.
To notify affected members privately, open Moderation → Automatic action notices and enable DM affected member. You can also update the existing AutoModeration section in the same module file:
These are shared settings for automatic moderation, so preserve any existing log channels and notice text you want to keep. The member notice is attempted after a successful punishment; Discord may prevent the DM from being delivered.
What triggers Honey Pot?
New messages in a selected trap channel or its threads, including messages containing only attachments.
Messages from members who have no bypass role or bypass permission.
Edits, system messages, webhooks, bot messages and messages from the server owner do not trigger Honey Pot. Configured exemptions apply before deleting or punishing.
For a burst of messages, the bot still attempts to delete each trap message, but applies at most one Honey Pot punishment per member per server every ten seconds. Failure to delete a message does not prevent the bot from attempting the selected punishment.
Turning Honey Pot off stops future enforcement. It does not undo previous punishments or remove an existing warning.
Troubleshooting
Last updated