The shipped clips point at
https://cdn.yourserver.com/..., which resolves to nothing. Replace every URL in config/soundboard.lua before going live, or the soundboard silently does nothing.An entry
Hosting the files
Host your own. Don’t hotlink someone else’s CDN, and only use audio you have the right to distribute. Practical notes:- Keep clips short — under five seconds. They layer over the music.
- Normalise them. A clip mastered louder than the track will make people jump.
- The host must be publicly resolvable. Private IPs, loopback,
.local,.internaland cloud metadata addresses are all rejected — the same URL rules that apply to queued tracks. Config.Security.allowedHostsalso applies here. If you’ve locked direct media to your own CDN, your soundboard files need to be on it.
Cooldowns
Config.SoundboardCooldown (default 1500 ms) is enforced per player and per clip, on top of a rate limit. Two DJs cannot machine-gun the same sound, and one DJ cannot machine-gun anything.
Turning it off
Setsoundboard = false on a booth to disable it there entirely — for everyone, including admins. It’s a capability of the booth, not a permission. See Booth locations.
To gate it rather than disable it, use the soundboard action tier instead. See Permissions.
What players can see
Clients send a key. The server resolves it against your config, checks the booth has the soundboard enabled, checks the cooldown, then broadcasts the key to everyone in range.The panel never receives your URL list. It only ever gets the key, label, icon and category — so your CDN paths aren’t exposed to players.
Adding your own
Add entries toConfig.Soundboard in config/soundboard.lua. Use a new category string and it becomes a new tab in the panel automatically — you don’t have to stick to the four that ship.
Restart the resource after editing.
