8 min · Start here
Moderation setup
Point logs, then ban, mute, and warn from Discord.
You will
Staff can warn, mute, and ban, and every action has a case.
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.
Before you start
- Invite near and put it above the mute role.
- You need Manage Server or you own the guild.
Set it up
- Set a log channel. Cases live in the log channel. Pick one staff can read. near writes bans, mutes, and warns there so history survives a restart.
,logs
- Warn first. Warns stay in the case log. Use them when you want a record and not a mute.
,warn @user reason
- Mute. Mute uses the mute role from ,setupmute or Basics. Test on an alt before you need it live. Timed Discord timeouts are a separate command.
,mute @user reason
- Ban. Ban a member with a reason. Hierarchy still applies. near cannot ban someone whose top role is above the bot.
,ban @user reason
- Read the case. Open the log channel after each action. If the case is missing, near cannot talk there or logs were never pointed.
Examples
,ban @user invite spam
,mute @user ads
,warn @user tone
,timeout @user 10m
Do not
- Do not skip logs. You will not have history after a restart.
Troubleshooting
- If nothing logs, the log channel is missing or near cannot talk there.
- If mute does nothing, the mute role is missing or above near.
- If ban is denied, the target is higher than the bot or you lack the staff key.
Verify it works
- Warn an alt. Confirm a case appears in the log channel.
- Mute the alt. Confirm they cannot type in a test channel.