Repository navigation
Installation
| Minecraft | 1.20 to 26.x |
| Server | Spigot, Paper, Folia, and their forks. One jar for all of them |
| Voice chat | Simple Voice Chat, Plasmo Voice, or both |
| Optional | WorldGuard, PlaceholderAPI |
No database, no API keys and no accounts are needed.
- Put the voice plugin into
plugins/. - Put the CDisc jar from Modrinth into
plugins/. - Restart the server. A real restart, not
/reload. The first start createsplugins/CDisc/. - Tell players to install the client mod of the same voice chat. Without it everything works, but they hear nothing.
Then hold any music disc and run /cdisc create never gonna give you up. See Creating discs.
# config.yml
voice-backend: auto| Value | Meaning |
|---|---|
auto |
Whichever is installed. With both installed, the same as multi
|
multi |
Plays through every installed voice plugin at once, so players on either mod hear the jukebox. Costs one extra Opus encode per plugin |
simplevoicechat |
Simple Voice Chat only |
plasmovoice |
Plasmo Voice only |
With neither installed, CDisc disables itself and says so in the console.
Everything lives in plugins/CDisc/.
| File | Holds |
|---|---|
config.yml |
How the plugin behaves: voice backend, jukeboxes, lyrics, broadcasts |
sources.yml |
Which services it may play from, and how it talks to them |
tokens.yml |
Keys, tokens and passwords. Treat it as a password |
permissions.yml |
Who may do what, and limits for players who aren't staff |
languages/ |
Message files. See Languages |
local/ |
Your own audio files. See Local music folder |
/cdisc admin reload re-reads all of them. Every setting is described by the comment beside it, and Configuration covers the files in more detail.
CDisc looks for new releases on Modrinth and GitHub every six hours, downloads one into plugins/CDisc/update, and swaps the jar when the server stops. update-checker.auto-update: false in config.yml turns that off; you are still told about new releases.
On the first start of a new version, each config file is rebuilt from the copy inside the new jar: new settings arrive with their defaults, the comments are refreshed, removed settings are named in the console, and every value you changed stays changed. The previous file is kept beside it as <name>.old.
Sources and keys used to live in config.yml. They move into sources.yml and tokens.yml on their own, and the original is kept as config-before-split.yml.bak. That backup holds your keys in plain text: delete it once everything works.