How to Set Up LuckPerms Context (Per-World Permissions)

Why Per-World Permissions?

On a multi-world server, players often need different abilities depending on where they are. Builders in a creative world need WorldEdit access, but those same commands would be destructive in survival. LuckPerms solves this with contexts, conditions attached to permission nodes that restrict where they apply. Using luckperms context per world, you can grant WorldEdit in the creative world and deny it everywhere else with a single command.

How Contexts Work

A context is a key-value pair. LuckPerms ships with several built-in context types: world, server, gamemode, and more. When you attach a context to a permission node, that node only activates when the player's current context matches. For luckperms context per world setups, the world key is the one you will use most.

# Grant WorldEdit in the creative world only
/lp group builder permission set worldedit.* true world=creative

# Grant fly in the lobby
/lp group vip permission set essentials.fly true world=lobby

Setting Up Per-World Groups

Instead of adding contexts to individual permissions, you can make an entire group apply only in a specific world. This is cleaner for large permission sets.

# Create a creative-only group
/lp creategroup creative-perms

# Add permissions to the group
/lp group creative-perms permission set worldedit.selection.* true
/lp group creative-perms permission set worldedit.clipboard.* true
/lp group creative-perms permission set worldedit.region.* true

# Assign the group to builders, but only in the creative world
/lp group builder parent add creative-perms world=creative

Now any player in the builder group inherits creative-perms only while they are in the creative world. The moment they teleport to survival, those permissions disappear.

Context Stacking

You can combine multiple contexts on a single node. For example, granting a permission only in the survival world and only in survival gamemode:

/lp group member permission set essentials.kit.starter true world=survival gamemode=survival

Both conditions must be true for the node to activate. This is useful for luckperms context per world configurations on servers that mix gamemodes within the same world.

Checking Active Contexts

# See what contexts apply to a player right now
/lp user Notch info

# Check a specific permission with context resolution
/lp user Notch permission check worldedit.selection.pos

The info command shows the player's active contexts at the bottom of the output, which helps you debug why a permission is or is not applying.

World Name Gotchas

• World names are case-sensitive. world=Creative and world=creative are different contexts. Use lowercase world folder names to keep things consistent.
• If you use Multiverse, the world name in LuckPerms matches the folder name, not the Multiverse alias.
• Nether and End worlds are separate contexts: world=world_nether and world=world_the_end by default.

Config File Reference

LuckPerms stores contextual permissions in its YAML/HOCON storage. Here is what a contextual node looks like in the groups/builder.yml file:

permissions:
  - permission: worldedit.*
    value: true
    context:
      world: creative

You can edit these files directly if you prefer file-based management over commands, then run /lp sync to reload.

For the full per-world permission architecture, see our How to Set Up Per-World Permissions in Minecraft tutorial and the broader Minecraft LuckPerms Permissions Guide.

Need hosting with full config access? Astroworld Hosting, Pterodactyl panel, NVMe SSDs, 24/7 support.