Documentation

How to run near

near is a Discord bot. You type commands in chat. Each server picks its own prefix. Examples on this site start with a comma so they stay readable.

21 guides · 134 commands

Examples on this site start with a comma. Your server can use a different prefix. Change it with `,prefix` or in Basics if you own the server.

How these docs work

Read the chapters below in order the first time. After the first hour you can skip around. Each guide has what to do before you start, the commands to run, what good looks like, and what to check when it fails.

• All guides grouped by job: start, moderation, safety, voice, messages, studio.
• Command reference with usage, aliases, permission, and copyable examples.
• Search across guides and commands.
• /commands is the same list as cards if you already know the name.

Read in order

Invite, first hour, prefix, dashboard, then verification, logs, moderation, and staff tools. Stop after first hour if you only need warn and mute today.

1. 01Invite nearAdd the bot and put its role high.
2. 02First hourLogs, mute, and one staff grant.
3. 03Prefix and settingsSee the prefix. Change it if you want.
4. 04DashboardThe Discord owner edits the same settings on the web.
5. 05VerificationButton, web check, staff gate, or an automatic role.
6. 06LoggingOne staff channel first. Split later if you want.
7. 07ModerationBan, mute, warn, and cases.
8. 08Staff toolsStaff run commands without Discord Administrator.

Then go deeper

Filters, antinuke, voice rooms, music workers, welcome, tickets, giveaways, rep rewards, reaction roles, and Embed Studio each have a chapter. Deploys do not rewrite Discord. Stay in sync when you want shipped filter updates.