Honeypot

Honeypot is an anti-spam trap channel. If a user posts in the configured trap channel, Vör can immediately run moderation action and record the event.

What It Does

  • Watches one configured trap channel per server
  • Triggers when a non-staff user sends a message in that channel
  • Supports configurable trigger actions: none, mute, kick, softban, comped, perm-ban
  • Sends a pre-action alert to the configured Result Channel (or fallback log channel)
  • Deletes the offending message after the action (when it has Manage Messages)
  • Updates a persistent status panel with total triggers and most recent trigger
  • Stores trigger history for stats
  • Rotates the trap channel name to random warning-style names on each trigger
  • Auto-redeploys the status panel if the panel message is deleted

Setup

  1. Open config:
/config cog Honeypot
  1. Set these values:
    • Honeypot Channel: required trap channel
    • Result Channel: optional channel for trigger/action notices
    • Trigger Action: select which moderation action runs on trigger
    • Enabled: turn on after channel setup
  2. Deploy or refresh the panel:
/honeypot deploy

Trigger Flow

When a message is sent in the Honeypot Channel:

  1. Vör posts a Honeypot Triggered alert embed in the Result Channel (or fallback channel)
  2. Vör rotates the trap channel name
  3. Vör runs the configured moderation action
  4. Vör deletes the offending message (if permitted)
  5. Vör records the event in Honeypot state/history tables and refreshes the status panel

Commands

Command Purpose Access
/honeypot help Show setup steps and command reference Guild members with app command access
/honeypot config Open Honeypot config UI Administrator
/honeypot deploy Send or refresh the status panel Administrator
/honeypot stats Show recent honeypot removals and totals Manage Messages

Result Channel Output

The trigger alert is sent as an embed and includes:

  • User mention and name
  • Trigger channel
  • Message jump link
  • Trigger message content summary
  • Selected action label
  • Timestamp

If Result Channel is not configured or inaccessible, Vör falls back to the guild command log channel, then the honeypot channel.

Channel Name Rotation

On each trigger, Honeypot renames the trap channel to a random warning-style name using a simple word-combination generator.

Examples:

  • no-chat-here
  • do-not-use
  • do-not-talk-here
  • chat-is-disabled

If rename permissions are missing, Honeypot continues operation and logs the rename failure.

Notes

  • Honeypot ignores bot messages.
  • Honeypot ignores members with Manage Messages or Administrator.
  • If the configured Honeypot Channel is deleted or inaccessible, the cog auto-disables and logs why.
  • If the panel message is deleted, Honeypot recreates it automatically.
  • Message deletion requires Manage Messages in the honeypot channel.