near

From invite to a working server

Approve the bot, give it a high role, then set it up in Discord.

1. 1Invite

   Approve near. Put its role high.

2. 2Set up

   Run ,setup if this server is new. Point logs with ,logs channel #staff or ,logs setup.

3. 3Keep it in sync

   The Discord owner can edit the same settings on the dashboard. ,reload applies shipped filter updates. Deploys do not rewrite the server on their own.

Safety without Discord admin

Staff run the commands. near checks each one. Filters, antinuke, and case logs stay on even if nobody has Ban Members.

• Staff tools

  Warn, mute, jail, and ban from Discord. Grant the commands with ,fp. Their Discord role can stay empty.

• Filter and antilink

  The filter catches leetspeak and lookalikes. Antilink is a separate switch for random discord.gg posts.

• Antinuke

  Owner only. Turn the master switch on, then the events you care about. Whitelist last, not first.

• Cases and logs

  Bans, mutes, and warns write to the log channel so history survives a restart. Split message and member logs later if you want.

Play from apps people already use

Search a name or paste a link. One queue.

Music that stays in the call

Queue, skip, and EQ in Discord. Try ,play or ,jw below.

• Invite the music bots first

  Playback runs on worker bots. After you invite near, run ,addbots, approve each Music bot, join voice, then ,play.

• Preset filters

  Bass, crystal, punch, and more. Tap a preset on the player. Same list as ,eq.

• Several rooms at once

  Each music bot sits in one voice channel. Invite all of them if you want more than one room playing.

• Fallback

  If a source fails, playback moves to the next working source.

The rest of the server

Same prefix. Same permission check.