🌎 WorldGuard

This page covers the compatibility with WorldGuard.

Conditions

Is Owner

Checks if the player is an Owner of the region at their current location.

Syntax: worldGuardIsOwner

Is Member

Checks if the player is a Member of the region at their current location.

Syntax: worldGuardIsMember

Example

conditions:
  checkIfIAmOwner: worldGuardIsOwner
  checkIfIAmMember: worldGuardIsMember

Has Owner

Checks if the specified region has any Owner assigned to it.

Syntax: worldGuardHasOwner [world] [region]

Has Member

Checks if the specified region has any Member assigned to it.

Syntax: worldGuardHasMember [world] [region]

Parameter	Syntax	Default Value	Explanation
world	world:name	player location	The world where the region is located.
region	region:name	player location	The unique ID of the WorldGuard region to check.

Example

conditions:
  ownerExistsHere: worldGuardHasOwner
  ownerExistsInRoom: worldGuardHasOwner world:world region:room
  memberExistsHere: worldGuardHasMember
  memberExistsInTest: worldGuardHasMember world:town region:test

Note on Arguments

• When executed from the Console, the [world] and [region] arguments are mandatory.
• Regions are world-specific. For example, a region named test in world_a is different from a region named test in world_b.

Has Flag

Checks if the specified region has any Flag assigned to it.

Syntax: worldGuardHasFlag <flag> [world] [region]

Parameter	Syntax	Default Value	Explanation
flag	flag	none	The name of the WorldGuard flag to check for existence (e.g., pvp, entry, greeting).
world	world:name	player location	The world where the region is located.
region	region:name	player location	The unique ID of the WorldGuard region to check.

Example

conditions:
  hasBuildEnabled: worldGuardHasFlag build
  hasGreetingEnabled: worldGuardHasFlag greeting-title world:world region:house

danger

CAUTION: This condition only checks for the existence of a flag key; it returns true even if the value is set to deny, false, or an empty string. To validate specific states like allow or custom values, you must implement a separate value-check logic as this provider ignores all flag data.