Minecraft Forums

This is a fairly small suggestion. I have two main features to suggest.

I think that most people use commands inside written books to give access to specific commands to players. The problem is, the player is still burdened by permissions. Running virtually any command will give you a "You're not allowed to use this command" message. There is a workaround for this, but it comes with a lot of drawbacks.

Essentially, you can use the "/trigger" command to edit a score (trigger is one of the only commands non-admins can use) and then have a set of command blocks react to that.

This requires a specific place for command blocks to be placed, and increases lag (you must run multiple commands every tick instead of just one command on-demand). Yes, I know that you can apply conditions to commands to stop them from running, but executing these conditions themselves have an impact on performance, and so does the very existence of the command block in the world. On a large scale, this could be a big problem.

Also, this feature makes it impossible to use the book alone without some kind of command block structure. You are required to make one-command creations rather than a simple give command.

What's more, it is fairly easy to duplicate this behavior using the "execute if" command. But this would require a scoreboard, so perhaps we could have an nbt tag called "isAdmin" or something similar (not sure if this exists yet). That way, you could test for that specific nbt tag instead of a score.

There are multiple ways to remedy this situation. My first idea would be to have commands run in books bypass permissions. But I understand that this may cause unexpected behavior. My second idea would be to have a flag inside the "run_command" event to indicate whether to bypass permissions. It could be a simple byte flag like "{bypassPermissions:1b}". It could either be specified in the book itself or on an event by event basis.

On that note, I think the "/" should not be required when running commands. A developer could simply use the "/say" command to send a message to the chat.

Also, I think that running a command shouldn't boot you out of the book. Again, this may cause confusion, so perhaps it could be implemented as a flag again.