Security

Honeypot

Catch accounts posting in a clearly marked trap channel, with test mode, staff evidence, and configurable enforcement.

Updated October 21, 20262 min read

Getting started

Enable Honeypot

Honeypot works when Moderation is off or on. Enable Honeypot itself to start detection; test mode includes staff test messages.

Choose separate channels

Select a public honeypot text channel and a different private staff log channel. Members must be able to view and post in the trap; the bot must be able to read it.

Publish the warning

Use Publish warning to send the default warning image. Create channel is available when no channel is selected and requires Manage Channels. Warn members before enabling enforcement.

Start in test mode

Test mode is on by default. Enable Honeypot and post from your own account or a test member. Check Recent incidents and the staff log. Test mode logs matches without deleting messages or punishing members.

Choose enforcement

Choose log only, timeout, kick, or ban. Set the timeout duration, message deletion, and exempt roles as needed. Grant the required action permission and position the bot role above the test member.

Go live and review

Turn test mode off only after a successful test. Review the incident outcome; a detected message does not guarantee Discord accepted the punishment. Keep the bot and database online.

Settings reference

Use this reference when you need to check what a setting does.

Enable Honeypot

Starts detection independently of the Moderation module.

Honeypot channel

Trap text channel for member messages.

Staff log channel

Different private text channel for outcomes.

Test mode

Logs matches without punishment or message deletion; enabled by default.

Action

Log, timeout, kick, or ban.

Timeout duration

Between 60 seconds and 28 days.

Exempt roles

Additional roles excluded from enforcement; included in test mode.

Delete message

Removes a detected message during enforcement if allowed.

How it works

Here’s what happens once you’ve finished setup.

1
Message
A non-bot member posts in the configured trap.
2
Check
Honeypot verifies module state and exemptions.
3
Evidence
The incident must be saved before enforcement proceeds.
4
Outcome
Discord action succeeds or its failure is recorded and reported.

Example

EXAMPLE

Safe first test

Use a regular test member with Test mode on, confirm the logged incident, then choose an action and disable Test mode after checking bot permissions.

Permissions

What NightCrew needs

View Channel and Read Message History
Send Messages, Embed Links, and Attach Files for staff evidence and warning image
Moderate Members for timeouts, Kick Members for kicks, or Ban Members for bans
Manage Messages when deleting trap messages; Manage Channels when creating a channel

Things to know

Staff with administrative or moderation permissions and configured exempt roles are excluded. Test with a regular member.

The bot cannot detect new messages while its process is offline.

Troubleshooting

No incident or staff log appeared

Check Honeypot is enabled, the selected trap channel is correct, and the bot is online. Enforcement requires a non-exempt member and the correct bot permissions. If an incident exists without a staff message, read its delivery outcome and check channel permissions.

Incident exists but no ban

Read the outcome. Check Test mode, Ban Members permission, role hierarchy, and the selected action.

Database outage

If evidence cannot be saved, Honeypot takes no enforcement action.