Discortics logo
CommandsPremium
Login

The next generation of Discord community management — maximising engagement in the quickest and most transparent way.

Honeypot

Create a visible warning channel that catches automated scam posts and immediately removes the sender.

4 min readUpdated Sep 1, 2026

The Honeypot is a public warning channel designed to catch automated scam accounts. Any non-bot member who sends a message there immediately receives the selected action.

Honeypot is configured from the Anti-Spam command, but it works even when the main Spam Protection toggle is disabled.

Set up the Honeypot

Create the Honeypot channelChoose the action before enabling the channel.
  1. Run /autopilot antispam.
  2. Select Honeypot.
  3. Choose Ban or Soft Ban.
  4. Select Enable.
  5. Confirm that Discortics creates the public #honeypot channel.

[Insert screenshot here]

The Honeypot settings inside /autopilot antispam

Discortics adds a warning to the channel topic and first message.

Choose the action

  • Ban removes the member and deletes their messages from the previous 24 hours.
  • Soft Ban removes the member, deletes their messages from the previous 24 hours, then immediately unbans them so they can rejoin.

Actions are sent to the moderation log channel when one is configured. Otherwise, Discortics uses the Autopilot log channel.

Keep the channel convincing

  • Leave the channel visible to normal members.
  • Do not place it behind a special role.
  • Do not use it for staff conversation.
  • Keep the warning clear so a real member knows not to post.

The channel needs to look like a normal target to automated scam accounts. Hiding it prevents the trap from working.

Warning: Every non-bot member who posts in the Honeypot receives the selected action. Do not test it with a real member account.

Disable the Honeypot

Run /autopilot antispam, open Honeypot, and select Disable. Confirm the channel state afterward.

Common questions

Does Anti-Spam need to be enabled?

No. The Honeypot toggle is separate from the main Spam Protection toggle.

Why was a real member removed?

Any non-bot message triggers the action. Restore the member if appropriate, then make the channel warning clearer and remind staff not to use it for testing.