Currently you can only lock chests, barrels, furnaces and a few other block-entities.
Unfortunately, operator utilities such as command blocks, structure blocks, and test blocks aren't among them; and I think it's a huge missed opportunity.
Why?
It'd be a huge help in map-making
Being able to lock important blocks that you may not want certain people to have access is very important, especially the danger they can possess if anyone with malicious intents gets their hands on one.
Currently there's no way to do so
As of yet, there's no real way to lock operator blocks away from people without the use of external plugins or disabling command blocks altogether. This is a huge bummer for map-makers and server owners as disabling such blocks can heavily limit creativity and leaving them on can leave the whole server vulnerable to attacks.
It just makes sense (and there's no performance overhead)
command blocks, structure blocks, test blocks and the such are already block-entites, meaning adding this ability is as simple as changing a few lines of code and shouldn't introduce any performance problems. It'd also bring consistency among block-entities and less uncertainty on whether a block is able to be locked or not.
Some footnotes to close things off
- The lock would only affect the ability for players to edit the contents, meaning the execution of commands or the placement of structures would be left unaffected
- Locked blocks would still be able to interact with redstone.
Thanks for reading!
Please sign in to leave a comment.
0 Comments