NightsNights
Terms of ServicePrivacy PolicyAvatar HistoryTickets
CommandsDocsBuySupportAdd to Discord
NightsNights

A premium Discord bot for moderation, voice, music and support — built for communities that outgrow everything else.

Add to Discord

Navigate

  • home
  • commands
  • docs
  • support
  • invite

Legal

  • Terms of Service
  • Privacy Policy
  • Tickets

© 2026 Nights. All rights reserved.

discord.gg/scares

Introduction

  • Overview
  • Getting started
  • Permissions

Safety

  • Moderation
  • Antinuke

Features

  • VoiceMaster
  • Music
  • Tickets
  • Starboard
  1. Docs
  2. Introduction
  3. Permissions

Permissions

How Nights resolves Discord permissions and its own antinuke roles.

Nights checks two independent things before running a command: the Discord permission the invoking member holds, and — for destructive commands — its own antinuke allowlist.

Discord permissions#

Most commands map onto a native Discord permission. Grant it through a role and the member can use the matching commands; no bot-side configuration is involved.

ParameterTypeDescription
Ban MembersdiscordRequired for ,ban and the unban family.
Kick MembersdiscordRequired for ,kick.
Moderate MembersdiscordRequired for ,timeout, ,mute and ,jail.
Manage MessagesdiscordRequired for ,purge, ,warn and ,history.
Manage ServerdiscordRequired for configuration: welcome, starboard, logging.
AdministratordiscordRequired for whole-system setup such as ,setticketaio and ,voice setup.

Manage Server and Manage Guild

Discord renames this permission between its UI and its API. Nights accepts either name in command output — they are the same permission.

Antinuke admins#

Antinuke configuration sits behind its own role, not a Discord permission. This is deliberate: a compromised administrator should not be able to disable the system that limits the damage they can do.

  • Only the server owner may grant or revoke antinuke admin.
  • Antinuke admins may configure thresholds and actions, but hold no extra Discord permissions.
  • Having Administrator in Discord does not imply antinuke admin.
,antinuke admin add @Lupos
,antinuke admin list
,antinuke admin remove @Lupos
,antinuke admin add <user>Server Owner

Grant a member antinuke admin privileges.

,antinuke admin listServer Owner

List every current antinuke admin.

,antinuke admin remove <user>Server Owner

Revoke a member's antinuke admin privileges.

Role hierarchy#

Discord will not let any bot act on a member whose highest role sits above the bot’s own. If moderation commands fail against staff but work against everyone else, this is almost always why.

Keep the Nights role near the top

Drag the Nights role above every role it needs to moderate. It cannot ban, kick, timeout or rename anyone positioned above it, regardless of the permissions you grant.

Still stuck?

Ask in the support server — a human will get back to you.

Get support
PreviousGetting startedNextModeration