Repository navigation
Permissions and Server Settings
English | 繁體中文
Who can run what, and how to configure a server's DJ role, restricted channels, skip ratio,
and language — mostly through the /settings panel.
NextVoiceCord has three access levels. A command's help entry in Commands tells you which level it needs.
No role or permission required. Any member of the server can use these commands.
A command marked DJ can be run by:
- the bot owner (the Discord user ID configured as
discord.owner), or - any member with the Manage Server permission, or
- any member holding the server's configured DJ role.
If the DJ role is set to the server's own @everyone role, every member of the server
counts as a DJ — there is no separate "DJ mode" switch, setting the role this way is the
mechanism. This is a legitimate way to run an open server where anyone can pause, skip
outright, or change the volume, without granting Manage Server to everyone.
If no DJ role has been set at all, only the bot owner and members with Manage Server pass the DJ check — an unconfigured server behaves as if DJ commands were Admin-only.
A command marked Admin can be run by the bot owner, or by any member with the Manage Server permission. There is no separate "bot admin" role — Admin access follows Discord's own Manage Server permission directly.
Restricted to the single Discord user ID set as discord.owner in the bot's configuration.
This is the person running the bot, not necessarily anyone with server permissions — a
server's own owner cannot run Owner commands unless their Discord ID is the one configured.
/settings (or the text command settings) is open to everyone, but shows a different
panel depending on who opens it:
- Anyone who can manage the server (Manage Server permission, or the bot owner) lands on the server settings view — text/voice channel restrictions, DJ role, prefix, skip ratio, queue type, and now-playing layout/buttons. This is the view whose controls they are actually allowed to use, and the reason most people run the command.
- Everyone else lands directly on their personal settings view, which currently holds only their language preference. They never see the server controls, because those controls would reject them.
Someone who can manage the server also gets a dropdown on their panel that switches between
the server view and their own personal view — the only way to reach both from one command
invocation. Someone without Manage Server has no such dropdown, since the server view isn't
open to them anyway; their /settings is the personal view outright.
From the server settings view, use the role selector to pick a role, or run:
setdj <rolename>
setdj NONE
Setting it to @everyone makes every member a DJ, as described above. NONE clears the DJ
role entirely, which — per the rule above — leaves only the owner and Manage Server members
with DJ access.
Two independent restrictions, both set from the server settings view or with commands:
settc <channel> # restrict music commands to one text channel
settc NONE # remove the restriction
setvc <channel> # restrict playback to one voice channel
setvc NONE # remove the restriction
With a text channel set, running a music command in any other text channel gets an error back instead of executing. With a voice channel set, the bot only joins and plays in that channel.
The skip command lets any member vote to skip the current song; once enough of the
listeners in the voice channel have voted, the song skips. The ratio required is set per
server with:
setskip <0-100>
or from the server settings view, via the skip-ratio control. If a server has never set its own ratio, the bot's configured default (55%) applies.
NextVoiceCord's interface text resolves in this order, first match wins:
- Per-user — a language the individual member has chosen for themselves.
- Per-guild — the server's configured default language, if the user has not chosen their own.
- Global default — the bot's configured default language, if the server has not set one either.
A user sets their own language from the personal settings view of /settings (available to
everyone, per the two-view behaviour above): the language selector lists every language that
loaded successfully, each shown in its own name (so "日本語" rather than "Japanese"), plus a
"follow the server" option that clears the personal override and goes back to inheriting
from the guild. Only English is human-reviewed; the other eleven bundled languages are
machine-generated and marked as unreviewed.
Setting the server's own default language, like the rest of the server settings view, is available to anyone who can manage the server.
Commands for the full command list with access levels noted per command,
Controller-Panel for customising the now-playing panel (edited with controller, an
Admin command), Getting-Started for first-time setup including discord.owner, and
Troubleshooting if a permission check is not behaving as documented here.