-
Notifications
You must be signed in to change notification settings - Fork 0
08. World Border & Zones
Finerus edited this page Aug 16, 2026
·
1 revision
Distance based warnings around spawn, independent of the vanilla world border, plus named zones with their own enter and exit messages.
Config: [World Border Warning] section of rpessentials-core.toml.
| Option | Default | Description |
|---|---|---|
enableWorldBorderWarning |
true |
Master switch. Since 4.2.0, setting this to false fully disables the system. |
worldBorderDistance |
1500 |
Distance from spawn, in blocks, that triggers the warning. |
worldBorderTeleportEnabled |
false |
If true, players reaching the border are teleported to the opposite side. |
worldBorderPrewarnDistance |
0 |
Distance for an earlier soft warning, must be less than worldBorderDistance, 0 disables it. |
worldBorderPrewarnMessage |
see config | Placeholders: {distance}, {player}, {border}. |
worldBorderMessage |
see config | Placeholders: {distance}, {player}. |
worldBorderCheckInterval |
40 |
Check frequency in ticks, 20 ticks equals one second. |
worldBorderDimensionOverrides |
[] |
Per dimension overrides, format dimension;distance;teleport;prewarnDistance. |
zoneMessageMode |
ACTION_BAR |
Display mode for both border and zone messages: IMMERSIVE, CHAT, ACTION_BAR. |
Zones defined by a center, a radius, and enter/exit messages.
namedZones = [
"name;centerX;centerZ;radius;messageEnter;messageExit",
"name;centerX;centerZ;radius;dimension;messageEnter;messageExit"
]
The dimension field is optional, if omitted the zone applies in every dimension the player is in. Leaving messageExit empty means nothing is sent when leaving the zone.
Zone state is tracked per player, so entry and exit messages only fire once when actually crossing the boundary, not on every tick.
Both systems run on the same periodic tick (worldBorderCheckInterval, default every 2 seconds), scanning only connected players.