Permissions and Security

Permissions And Security

Ownership

Each stored music entry records the creator's UUID and name in the server music index. Written Blueprint CDs also carry disc metadata on the ItemStack.

Trading a physical Blueprint CD does not transfer ownership of the server-side audio entry.

Normal Players

Players can:

• create discs through the CD Writer
• list their own available entries
• inspect their own entries
• delete their own entries
• manage local cache downloads

Player commands use uploaded file names where possible. Players can manage only music entries they own.

Admins

Admins can:

• import from server paths where config allows it
• request a client upload through the admin upload command
• inspect all entries
• delete any entry
• test-play entries
• view detailed server storage
• manage server FFmpeg setup
• reload config/index
• repair the index

Admin commands require server admin permission level.

Security Behavior

• The server validates paths, extensions, sizes, durations, quotas, statuses, and checksums.
• Dedicated servers cannot read arbitrary files from a player's computer through commands.
• Absolute server paths are disabled by default on dedicated servers.
• Audio chunks sent to clients are bounded and verified with SHA-256.
• Managed FFmpeg downloads require explicit action and SHA-256 verification before use.
• Public release jars do not contain FFmpeg executables, native libraries, or hidden binary archives.
• Uploaded audio rights are the responsibility of users and server operators.