Getting started

Invite Nights, set your prefix and run your first commands.

Adding Nights takes about a minute. The bot works out of the box with the default , prefix — everything below is optional tuning.

Invite the bot#

1
Authorize Nights
Open the invite link and pick the server you want to add it to. You need Manage Server on that server for it to appear in the list.
2
Keep the default permissions
The invite requests the permissions Nights needs for moderation, voice and logging. Stripping them here is the most common cause of “the bot ignores my command” later.
3
Confirm it responds
Run ,prefix in any channel Nights can see. If it replies with the current prefix, you are done.
```
,prefix
```

No response at all?

Check that Nights can both View Channel and Send Messages in the channel you are testing in. Channel-level overrides silently win over the role permissions granted at invite time.

Change the prefix#

The default prefix is ,. If it collides with another bot, set your own — it applies to every prefix command on that server.

,prefix
,prefix set !

,prefix

View the current server prefix.

,prefix set <new prefix>Manage Guild

Set the server prefix.

,prefix removeManage Guild

Reset back to the default prefix.

Slash commands ignore the prefix

Changing the prefix only affects prefix commands. /prefix view and every other slash command keep working regardless.

Recommended first setup#

Three systems are worth configuring on day one, in this order:

Antinuke — protects against mass bans and channel deletion before you hand out staff roles. Run ,an enable.
Moderation — run ,mute setup once so the Muted role exists and is applied to every channel.
Tickets — ,setticketaio builds the whole support flow in a single command.

Still stuck?

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

Get support