Honeypot Commands And Workflow

Commands

Both replies are private. The command and subcommand wording can be changed in the language config. The default Athena permission level is management.

Startup Workflow

When warning.post_on_ready is enabled, AthenaBot checks the configured honeypot channel after startup. It updates the stored warning message when it can find it, or posts a new warning if the saved message no longer exists.

Trigger Workflow

1. A non-bot member sends a message in honeypot_channel.
2. The plugin checks the ignored user and role lists.
3. It deletes the trigger message when enabled.
4. It sends the configured member DM when enabled.
5. It applies the selected punishment.
6. It sends an incident embed to honeypot_log when that channel is configured.

Messages in every other channel are ignored. Messages from bots are also ignored.

Mute Workflow

With punishment.action: "mute", the plugin reads punishment.mute_method:

• athena calls Athena’s moderation mute handler. Existing Athena mutes count as successful, and the punishment is tracked by the moderation system.
• discord applies a direct Discord timeout to the member.

Both methods use punishment.timeout_duration_minutes, capped at Discord’s 28-day timeout limit.

If Athena mode is selected but the moderation plugin or mute handler is not available, the plugin records the failure in AthenaBot’s logs and does not apply a Discord timeout automatically.

Incident Logs

The log embed includes:

• Member mention and ID
• Trigger channel
• Selected punishment or mute method
• Trigger-message content, trimmed to Discord’s field limit
• Audit reason
• A (failed) marker when the selected punishment could not be applied

The trigger can still be deleted and the member can still receive a DM when the punishment itself fails because those steps run first.