Skip to content

Region Priority and Parents

Ghost edited this page Nov 15, 2026 · 1 revision

🧩 Region Priority and Parents

Multiple regions may overlap. Fabric Guard records a priority and an optional parent for each region so that policies can be organized without duplicating every flag.

Priority

/rg setpriority town 10
/rg setpriority town_market 20

A higher number indicates greater priority when overlap resolution is applied. If two regions overlap, explicitly inspect the final behavior rather than assuming every flag uses the same conflict behavior.

Parent regions

/rg setparent town_market town

Use a parent relationship when a subregion should share broader policy with a containing region. The build stores parent IDs and resolves parent references when loading region data.

Remove a parent

/rg setparent town_market

The __global__ region cannot have a parent. The implementation also checks for parent cycles and rejects a relationship that would create a loop.

Example — Town and market

  1. Create town and configure general restrictions.
  2. Create town_market within the town.
  3. Run /rg setpriority town_market 20 and /rg setpriority town 10.
  4. Set the parent of town_market to town if inheritance is desired.
  5. Apply any market-specific flags and test with a regular player.

Global region

__global__ is evaluated as the dimension's global region. Its flags act as a broad baseline; a more specific region can affect the result. See Region-Management.

Tips

  • Document your chosen priority scheme for admins.
  • Avoid arbitrarily large numbers: consistency matters more than magnitude.
  • Test overlapping protection, especially entry, exit, build and passthrough.

Clone this wiki locally