Skip to content
Nighthawk LogoNighthawk
Documentation

Nighthawk documentation

Everything in one place: step-by-step guides for setting Nighthawk up, and a reference for every command it understands.

Guides

Start with Getting started, then work through whichever features your community needs.

Getting startedAdd Nighthawk to your Fluxer community and run your first moderation command.Cases & moderationHow every moderation action becomes a searchable, permanent case.Automod setupBuild automated moderation rules that catch rule-breakers before your team sees them.Anti-raidLock down your community the moment joins, messages or invites spike beyond normal levels.Verification gateHold new members behind a check before they get access, and kick the ones who never complete it.Ban appealsGive banned users a fair way to appeal and review submissions from one inbox.Watchlist networkShare ban reports with other Nighthawk communities and act on flagged users when they join.LoggingStream server events to dedicated channels so your team never misses important activity.SlowmodeKeep channels usable during busy periods without punishing normal conversation.Roles & permissionsMap your existing Fluxer roles to Nighthawk permission groups.Reaction rolesBuild self-assignable role panels members claim with a reaction.TemplatesSave reusable moderation messages and apply them with a single argument across warns, mutes, kicks and bans.Security scoreA health check that scores your moderation setup out of 100 and fixes common gaps with one click.EncryptionEnd-to-end encrypted appeals, encrypted moderation data at rest, and the keys that unlock both.Incident replayBuild a post-mortem timeline of what happened in your community with a single command.AI moderationScore every message against hate, harassment, violence and more, and act on what keyword filters cannot catch.Nighthawk DeepIntelThe paid plan: a much larger AI moderation allowance and image attachment scanning, for one server.

Command reference

All 67 commands, grouped by what they do. Each entry lists its usage, aliases and the permission group needed to run it.

Conventions

The prefix
Every command uses the n! prefix by default.
Arguments
<required> must be supplied; [optional] can be left out. A user can be a mention or an ID.
Permission groups
Each command lists the group needed to run it. Groups are mapped to your own server roles, and any command can be re-pointed at a different group with n!delegatecommand. See Roles & permissions.