Limit a LuckPerms command permission to one Minecraft world
Applies to: LuckPerms; match the linked maintainer documentation to your installed platform and release.
Documentation checked .
A build-world permission should not leak into survival. Add a world context to the exact node and verify the boundary with the same ordinary account in both worlds.
Follow the procedure
- Write down the internal world folder names, not the display names shown in a menu. Confirm the target world exists and the player can reach it.
- Inspect the group or user’s current node entries for an unconditional grant. A contextual permission does not cancel a separate global grant.
- For a test account, set the intended node with a world context, such as
/lp user PLAYER permission set example.build true world=buildworld. - Enter the target world and use the feature. Repeat from survival and the Nether, noting the world name and result for each attempt.
- If the node still applies everywhere, inspect direct and inherited global entries. Remove a global entry only after checking who else depends on it.
- Copy the verified rule to the intended group, then remove the test account’s direct exception. Re-test group members and a player outside that group.
Check the result
The feature should succeed in the named world and fail elsewhere for an ordinary player. A command permission check alone does not prove the action behaves correctly across worlds, because another plugin may enforce its own world list. Test a complete action in each relevant destination.
If the result is wrong
If the wrong world loses access, check spelling, world aliases and any global node left behind. Revert only the contextual entry you introduced. Avoid changing the default group or disabling protection across every world to work around a single incorrectly scoped permission.
No comments to display
No comments to display