Everything the bot does

Discord only lets you add a bot where you have the Manage Server permission, so that is the short answer to which of your servers you can add it to.

The invite link asks for the exact permissions the bot's features need: reading and sending messages, embedding links, managing messages for the purge command, connecting and speaking in voice channels, timing members out, and managing roles. Discord shows you the full list on the authorisation screen before you accept.

There is also a second link that asks for Administrator instead. It is there for convenience: with it you never hit a missing-permission wall later. It also means the bot can do anything on your server, so pick the first one unless you have a reason not to.

The bot sees a channel when its role is allowed to see it. A channel with its own permission overwrites — a private channel where @everyone has been denied access — stays invisible until you add the bot's role to that channel. No invite link changes that: a per-channel overwrite beats a role permission, by Discord's design.

By default the bot answers in every channel it can see. You can narrow that down with the channel list, and then it only answers where you allow it.

The bot speaks Polish or English, set per server. The website language and the bot language are separate settings — changing one does not touch the other.

Join a voice channel and the bot follows you there. Searching goes through SoundCloud; links from Spotify and Apple Music work too — the bot reads the title and artist from them and finds the track in the source it can actually stream.

Music commands are open to everyone on the server. That is deliberate: gatekeeping a queue tends to create more arguments than it settles.

When a track starts, the bot posts a message with the cover art, a progress bar and control buttons. Switching tracks updates that message rather than posting a new one, so the channel does not fill up.

You can choose how the buttons look — icons only, text only, or both — in the dashboard.

The dashboard has a live player. Join a voice channel on Discord, open the player page, and the buttons there control the bot directly — play, pause, skip, volume, loop, and the radio stations.

The page also has a search box, a worldwide chart of the most played tracks, and what has recently been played on your server.

Every server gets the same shared pool of stations, and those cannot be edited or removed — that is what makes them shared. On top of that, a server can add its own stations by stream address.

Adding and removing stations is limited to the server owner and one role you designate in the dashboard. Listening is open to everyone.

Every moderation action opens a numbered case and, when a log channel is set, posts an entry there. The person on the receiving end gets a direct message explaining what happened and why, sent before they lose access — otherwise it would never reach them.

Moderation commands are available to the server owner and to the roles you list in the dashboard. Discord's own Administrator permission does not grant access on its own; this was deliberate, so that a role can moderate without also being able to change every other setting.

Automod watches messages and reacts on its own. Rules can be turned on one at a time: invites to other servers, links outside an allowed list, excessive capitals, mention floods, a blocked word list, and message spam.

A hit deletes the message, adds a strike and posts a short notice that removes itself after a few seconds. When strikes reach the threshold, the punishment you configured is applied — or nothing, if you would rather it only delete.

The word filter strips accents and repeated characters before matching, so simple masking does not get past it. Moderators are always skipped, and you can add further exceptions by role or channel.

With a log channel set, the bot records deleted and edited messages, moderation cases and automod hits. Message logs include the content, so pick a channel your moderators can see and your members cannot.

An empty channel list means the bot works everywhere. Add channels and it answers only there. The configuration commands themselves always go through, whatever the list says — otherwise a wrong entry would lock you out of fixing it.

Permissions are built on roles you name, not on Discord's permission flags. The server owner always passes — that is the way out if a role is ever set wrong.

Moderation goes to the moderator roles, automod to the automod roles, radio management to one designated role, music to everyone. Channel and language settings stay with the owner alone.