Wiki Release: 2026.09.8 · UltimateRaids: 0.12.0 · Documentation branch: 1

Locations, bounds and borders#

Locations are resolved relative to the raid origin unless the configured location mode says otherwise. The main raid locations are origin, lobby, player spawn, spectator, exit and optional arena bounds.

In-game location commands#

/uraid location origin <raid>
/uraid location lobby <raid>
/uraid location spawn <raid>
/uraid location spectator <raid>
/uraid location exit <raid>
/uraid location pos1 <raid>
/uraid location pos2 <raid>

Use /uraid location gui <raid> to open the environment/location editor.

Bounds#

bounds:
  enabled: true
  teleport-back: true
  pos1: ...
  pos2: ...

Bounds define the physical raid area used by player/environment checks. With teleport-back, participants who leave the allowed area can be returned.

Borders#

A raid border is independent from bounds:

border:
  enabled: true
  provider: AUTO
  mode: BOTH
  center: ...
  size: 32
  teleport-back: true

Modes:

VISUAL — show a client/player border without using it as the physical enforcement layer.
PHYSICAL — physical enforcement only.
BOTH — visual + physical.

Provider AUTO follows the modules.yml border priority. The default priority is PacketEvents, EntityWizard, ProtocolLib, then native/default when those providers are registered.

Stage borders#

A stage can temporarily resize/override the border. This is useful for boss-room transitions:

border:
  enabled: true
  size: 11
  transition: 5s

Use descending stage sizes to create a shrinking encounter.

Common mistake#

A visual border can work while bounds or physical enforcement are misconfigured. Treat bounds, border mode, border provider and teleport-back as separate settings and test each one deliberately.