Repository navigation
Limits
Some things the addon can't do. Most of them come from how Minecraft handles commands.
A stage can give a command because the addon hooks into the check every command node has. Vanilla commands use that check almost everywhere. Some mods check permissions a second time inside their own code, and the addon can't reach that. A stage can still take those commands away, but giving them to someone who isn't an operator may not work.
The addon knows the game modes of /gamemode. Everything else is compared exactly as it was typed. An
entry on time.set.1000 won't match 1000t, and tp.steve won't match a UUID or @p. Values are meant
for fixed words like game modes, not for numbers or player names.
An entry also covers everything behind it: gamemode.creative allows /gamemode creative <OtherPlayer>
as well.
NeoForge wants operator level 2 for @p, @a and the rest. If a moderator stage has minecraft.tp, the
moderator can run /tp Steve, but /tp @p fails.
Some commands have requirements that have nothing to do with permissions. When a stage gives such a command, those requirements are skipped too.
If another mod runs a command for a player, say as a quest reward, it gets checked as if the player had typed it. A locked command stays locked there too.
The console, command blocks and functions are never checked. Think twice before giving setblock,
fill, clone, summon, data, function or schedule to a stage. Where command blocks are enabled
(single player always has them), a player with those commands can place a command block and run whatever
they like with it, /history included.
They can join. They just don't get the editor tab, the greyed out F3+F4 menu or ranks on name tags.