Moderation & safety

Keep your server clean with a verification gate (Free), auto-moderation, an infractions log with warn escalation, an optional AI check, and alt-account detection.

HoneyGate gives you a full safety toolkit: a verification gate (Free — your front door), anti-nuke (Pro — stop a rogue admin), auto-moderation (Pro — filter bad messages), an infractions log (Pro — a permanent record with optional warn escalation), and alt detection (Pro — flag likely duplicate accounts).

Verification gate (Free)

New members click a Verify button to receive your verified role and unlock the rest of the server. Set your channel permissions so unverified members can only see the verify channel until they pass.

• Account-age check (optional) — deny accounts younger than a number of days you set. Raiders and scammers overwhelmingly use brand-new accounts.
• Network alt screen (optional, uses Alt Detection) — if the account is confirmed as an alt anywhere on the HoneyGate network, you can hold it for staff review or deny it. Single-server bots can't see across servers like this.
• Every attempt is logged, and holds/denials post to a staff channel you choose.

Setup: turn it on, pick the verified role + verify channel, optionally set the account age and alt action, then click Post panel. Your bot's role must sit above the verified role so it can assign it.

Anti-nuke (Pro)

Protects your server from its worst-case scenario: a compromised or rogue admin (or a malicious bot) suddenly mass-deleting channels/roles, mass-banning members, or spamming webhooks. The bot watches your audit log and, when one actor crosses a threshold of destructive actions in a short window, it responds — alert only, strip the offender's dangerous roles, kick, or ban — and pings your staff channel.

• Always exempt: the server owner, the bot, and anyone you whitelist (by role, or by user/bot ID for trusted bots).
• Two requirements: the bot needs the View Audit Log permission, and its role must sit above anyone it might need to stop (otherwise it can only alert).
• Start with Strip dangerous roles once your whitelist is set.

Auto-moderation

Auto-moderation watches messages and acts on the ones that break your rules.

Quick start: pick a protection level

You don't have to reason about every setting. At the top of the auto-moderation page, pick a one-click protection level and it fills in sensible settings for you:

• Relaxed — light touch: stops invite spam and message flooding, but won't punish enthusiasm (all-caps, lots of pings).
• Balanced (recommended) — the sensible default for most communities: filters invites, mass-pings, all-caps shouting and spam, and times out repeat offenders for 5 minutes.
• Strict — locked down for large or raid-prone servers: tighter limits and a 10-minute timeout.

Picking a level fills the settings and turns auto-moderation on — review them and click Save. You can fine-tune anything afterwards (that simply shows as a "Custom" level). Your banned-words list, exempt roles/channels, log channel and the AI check are never changed by a preset.

Fine-tuning

What you can filter:

• Invite links to other Discord servers.
• Links in general.
• Mass mentions (over a limit you set).
• Excessive caps (over a percentage you set).
• Spam (too many messages in a short window).
• Banned words (your own list; whole-word, case-insensitive).

What happens on a violation: the message is deleted and, optionally, the member is timed out for a duration you choose. Everything is logged to a channel you pick. You can exempt trusted roles and specific channels.

The optional AI check

You can turn on an AI second pass that catches things simple word-filters miss — context-based toxicity, scams, and shilling. Two important things:

• It only flags suspicious messages for your staff to review (it doesn't delete on its own) — so it fails on the safe side.
• It runs after the keyword rules, is rate-limited, and if it's ever unavailable your normal rules still work.

Infractions & mod log (Pro)

A permanent record of every moderation action against a member — your paper trail.

• Log a case from the admin page: a note (record only), a warning, a timeout, kick, ban, or unban. Add a reason and an optional link to evidence. Timeouts, kicks, bans, and unbans are also carried out on Discord for you.
• It records actions you take in Discord too. When a moderator bans, kicks, or times someone out directly in Discord, HoneyGate notices and adds it to the log automatically — so the history is complete, not just what was done through the panel.
• Per-member history. Click any member to see everything on file: total cases, how many active warnings they have, and a full timeline.
• Automatic escalation (optional). Set thresholds like "3 warnings → timeout", "5 → kick", "7 → ban". Once a member collects that many active warnings, HoneyGate acts automatically (the most serious threshold they've crossed wins). You can pardon a warning so it stops counting.
• Optional log channel posts a tidy summary for every case, and you can DM the member the action and reason.

Setup: open Infractions, pick a log channel if you want one, decide whether to DM members, and (optionally) turn on escalation and set your thresholds — then Save. For the bot to record Discord-side actions and carry out timeouts/kicks/bans, it needs the matching permissions (View Audit Log, Moderate Members, Kick/Ban Members) and its role must sit above the members it acts on.

Alt detection

Alt detection flags accounts that are likely run by the same person, using signals like shared network fingerprints, timezone/locale overlap, and VPN/proxy use.

Setting it up: turn it on, optionally enable the VPN/proxy check, set a confidence threshold for flagging, and choose a staff channel for alerts. You review each flag and confirm or dismiss it.

Use judgment. These signals are probabilistic. People on the same home network, a campus Wi-Fi, or a shared VPN can look like alts. Review flags before acting — and be cautious with any auto-kick option.

Why it pairs with giveaways

Once alt detection is on, you can switch on "exclude alts" in giveaways so one person can't enter with five accounts.

Tips

• Start auto-mod gently (invites + spam + a short banned-words list), then tighten.
• Always set a log channel so you can see what's being actioned.
• Keep your staff roles exempt so moderators aren't caught by their own filters.