Current Situation:
The CustomCommandRegistry in the Script API allows creators to register custom / commands. However, the only way to allow non-operators to use a specific command is by setting the permissionLevel to Any.
The Problem:
When permissionLevel is set to Any, the command is broadcasted to the autocomplete list of every player on the server. If an add-on creator wants to make a command exclusively for a specific group of players (for example: players with a "VIP" tag, custom factions, or specific roles) without giving them Operator status, they are forced to show this command to everyone.
This clutters the chat UI for regular players who can't even use the command, and it ruins the immersion or secrecy of role-specific commands. Because of this limitation, developers often have to fall back to the beforeEvents.chatSend method (using !command) just to keep the interface clean.
Proposed Solution:
Please add a way to control the visibility of custom commands in the autocomplete menu on a per-player basis. This could be achieved by:
Adding an allowedTags, allowScoreboard or even visibility array parameter during command registration (so only players who have the requerment see the autocomplete).
Why this is important:
This would allow creators to build much cleaner, professional-looking add-ons where players only see the commands they are actually allowed to use—exactly like how Operator commands are hidden from regular players.
Please sign in to leave a comment.
0 Comments