So, I have changed functions.permission.level to 4 even though /tick's permission level is only 3. I am unable to run the command on the command block despite having a functional permission level higher than /tick's permission level. It should have ran the command but it did not.
Environment
Multiplayer vanilla server, tick freeze is not active
Linked issues
Comments 2
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm in 1.21.7-rc2, also happens with
setidletimeoutand presumably other commands as well, so I updated the title. This behavior is probably intentional since it is called “function-permission-level” and there are surely cases where it is desired to empower functions in this way without giving anyone in creative mode the same capabilities. That said, the output message (eg.[13:49:55] tick rate 1<--[HERE]) does not make it clear why the command was not run, something likeCommand "tick" requires permission level 4, but command blocks only have permission level 2would be better.