Skip to content

Permissions

Ghost edited this page Nov 15, 2026 · 1 revision

🔐 Permissions

Fabric Guard 1.7.10 uses worldguard.* permission nodes internally and also checks matching fabricguard.* aliases for many permissions. The bundled implementation uses the Fabric Permissions API and suggests LuckPerms or PlayerRoles as optional permission managers.

Administrative region permissions

The following worldguard.* nodes are declared in the source metadata/constants for this build:

Permission Purpose
worldguard.region.define Define a region.
worldguard.region.redefine.own Declared permission for redefining own region.
worldguard.region.redefine.other Declared permission for redefining other regions.
worldguard.region.claim Declared claim permission.
worldguard.region.info Read region information.
worldguard.region.info.others Read other users' region information.
worldguard.region.list List regions.
worldguard.region.list.others List other users' regions.
worldguard.region.flag Access flag editing.
worldguard.region.setpriority Change priority.
worldguard.region.setparent Set parent relationships.
worldguard.region.remove Remove a region.
worldguard.region.addowner Add an owner.
worldguard.region.addmember Add a member.
worldguard.region.removeowner Remove an owner.
worldguard.region.removemember Remove a member.
worldguard.region.select Select a region through WorldEdit.
worldguard.region.teleport Teleport to a region.
worldguard.region.load Declared region-load permission.
worldguard.region.save Save regions.
worldguard.reload Reload configuration / region data.
worldguard.build.bypass Global build-protection bypass.
worldguard.worldedit.bypass WorldEdit protection bypass.

Important: A declared constant is not proof that a corresponding subcommand exists. The 1.7.10 /rg command tree does not register /rg claim, /rg redefine, or /rg load. Do not promise those subcommands to users solely because permission constants are present.

Region-specific flag bypasses

This build generates bypass nodes in these two formats:

worldguard.region.flag.<flag>.<region>.bypass
fabricguard.region.flag.<flag>.<region>.bypass

For example:

worldguard.region.flag.block-break.spawn.bypass
fabricguard.region.flag.pvp.arena.bypass

A permission for one region and one flag should not be presented as bypassing all other region flags. A grass-spread/grass-growth compatibility alias is handled specially by the permission implementation.

Permission prefixes

For the declared worldguard.* command permissions, the compatibility logic can check an alternate fabricguard.* prefix. For predictability, select one prefix when designing a permissions scheme and test it on your installed permission manager.

Operators and bypasses

The inspected hasFlagBypass() implementation treats operator level 2+ as having a bypass, and permission providers can grant explicit per-region bypasses to non-operators. Test restrictions with a non-operator account; operators are not representative of ordinary players.

Suggested starting access policy

  • Give routine players no administrative /rg permissions.
  • Grant region-management permissions only to trusted staff.
  • Prefer precise per-region flag bypass nodes over broad global bypass permissions.
  • Test changes with at least one non-staff account.

Read more

Owners-and-Members · Flags · WorldEdit-Integration

Clone this wiki locally