Skip to main content
Hedwig has three layers of server protection:
  1. Antinuke monitors destructive server and member actions and provides user, role, and extra-owner trust lists.
  2. Automod filters risky or unwanted messages with 13 selectable modules.
  3. Logging records message, member, moderation, voice, and server events for staff review.
Read the focused guides for Antinuke, Automod, and Logging when you are ready to configure each layer.
1

Set up logging

Run /logging setup, choose the log channels, then /logging enable. Logging gives staff the context needed to tune the other layers.
2

Configure automod

Run /automod setup, review the modules, then /automod enable. Use /automod whitelist for carefully reviewed exceptions.
3

Enable antinuke

Run /antinuke enable, inspect /antinuke status, and manage trusted exceptions with /whitelist and /extraowner.

​
Antinuke commands

An allowlist is a trust boundary, not a convenience list. Keep it small, review it regularly, and never add a role just because it is easy to select.

​
Automod commands

​
Logging commands

​
Practical operating rules

  • Keep logs in staff-only channels. Automatic logging creates five channels under a private Hedwig Logs category when it has the required permissions.
  • Test filters with a moderator account before enabling them server-wide.
  • Pair automated action with logs so staff can audit false positives.
  • Pause a layer before changing it if the server is actively busy.
  • If you are responding to an incident, use /antinuke status before changing configuration.