michael/Sentinel
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions
3 releases 4 tags
  • 2.0.0 2d5c9cf47d

    2.0.0 Stable

    michael released this 2026-07-05 21:57:03 +02:00 | 22 commits to main since this release

    Sentinel 2.0.0

    Sentinel 2.0.0 introduces Discord AutoMod-powered honeypot detection. Sentinel can now intercept trap-role pings before they reach a channel, tally blocked attempts inside a rolling window, and ban repeat offenders once a configurable threshold is crossed. The original message-based detection mode remains available and fully functional.

    Highlights

    • AutoMod detection mode. Discord's native AutoMod blocks trap-role mentions before they are posted; Sentinel counts those blocked attempts toward enforcement.
    • Threshold-based enforcement. Define how many pings are tolerated within a rolling window before a ban is issued.
    • Managed AutoMod rules. Sentinel can create, enable, update, adopt, and recreate its own Sentinel Honeypot rule automatically.
    • Verify-only mode. Prefer to manage the AutoMod rule externally? Sentinel can enforce against an existing rule without modifying it.
    • Leaner intents. AutoMod mode skips the privileged Message Content intent entirely.
    • Message-independent bans. Enforcement can fire from AutoMod events alone — no Discord message object required.

    Detection & Enforcement

    • Only attributable BLOCK_MESSAGE actions from the configured AutoMod rule and guild count toward enforcement. Alert actions, unrelated rules, other guilds, bots, and exempt users are all ignored.
    • Each user's attempt count is tracked independently within the configured rolling window.
    • When managing a rule, Sentinel preserves any existing regex patterns while injecting the trap-role mention pattern.
    • Deleted managed rules are recreated automatically; missing, disabled, or incompatible externally managed rules produce critical diagnostics instead.
    • Message mode retains its existing messageCreate and messageUpdate behavior unchanged.
    • AutoMod-triggered bans record the ping count and rolling-window duration in their audit-log reason.
    • Ban operations accept guild and user inputs directly — no offending message needed.
    • Message-mode enforcement still attempts to delete the triggering message before banning.
    • Discord bans now respect the configured message-deletion window.

    Configuration & Permissions

    • detection_mode selects the strategy: message (default) or automod.
    • ban_threshold and ban_window_seconds govern enforcement timing.
    • manage_automod_rule controls rule ownership; automod_rule_id enables verify-only operation against an external rule.
    • ban_delete_message_seconds configures Discord's message-history deletion window on ban.
    • AutoMod mode requires Manage Guild, Manage Roles, and Ban Members permissions.
    • AutoMod mode uses the AutoModerationConfiguration and AutoModerationExecution gateway intents rather than message-content intents.

    Compatibility

    • Existing deployments stay on message mode unless explicitly switched.
    • Message mode bans after a single ping by default.
    • AutoMod mode bans after three blocked pings within one hour by default.
    • AutoMod attempt counters are in-memory and reset on restart.

    Full changelog: 1f314ad...2d5c9cf

    Downloads