Understanding OpenAudioMc Permissions and Commands

This document explains the permission system used by OpenAudioMc and how to control access to commands and speaker interactions. Use these guidelines to give players the right level of control without granting more access than needed.

Overview

OpenAudioMc permissions are fully configurable and can be tailored to your server. If you prefer a quick setup, grant server operators OP or the global permission openaudiomc.* on BungeeCord to provide full access. For finer control, assign specific permissions listed below.

Command permissions

OpenAudioMc exposes a permissions tree for commands under openaudiomc.commands.*. Granting openaudiomc.commands.* provides access to every administrative subcommand.

To allow or deny a specific subcommand, use openaudiomc.commands.<subcommand> where <subcommand> is the second argument in the command syntax. Examples

• To allow using region create grant openaudiomc.commands.region
• To allow using show start grant openaudiomc.commands.show

When you want players to run session commands use the following permission

• openaudiomc.commands.audio for the /audio command
• openaudiomc.commands.play for the /oa play or /openaudio play command

Speaker permissions

Speaker interactions have their own permissions group under openaudiomc.speakers.*. Granting openaudiomc.speakers.* allows all speaker related actions. For more granular control use these specific permissions

• openaudiomc.speakers.create to place speakers
• openaudiomc.speakers.destroy to remove speakers
• openaudiomc.speakers.manage to interact with or edit speakers for example changing source or volume

Common grant patterns

• Give staff full admin access without OP by assigning these two entries on BungeeCord
  • openaudiomc.*
  • openaudiomc.commands.*
• Give builders permission only to place and remove speakers
  • openaudiomc.speakers.create
  • openaudiomc.speakers.destroy

Notes and tips

• Permission names are case sensitive. Use the exact strings shown above.
• If a player has both a general wildcard and specific denies the exact behavior depends on your permission manager. Test permission assignments after applying them.
• For scripted automation or external tools use the named command permissions rather than OP for safer delegation.

Example commands for testing

Use these commands in game to confirm permission behavior

• openaudio show info demo to inspect a show
• openaudio show create demo to create a show
• openaudio show add demo 0s command say Hello to add a cue to a show
• openaudio show start demo to start a show

If a player cannot run a command check that their permission node is present and that no incompatible deny node is applied by your permissions plugin.

Where to get help

If you run into issues consult the official OpenAudioMc documentation or ask in the community support channels for examples specific to your permissions plugin.