Worlds and the border
The three ways to provide the event world, what happens to it between events, the border and the crystals.
The worlds
settings:
lobby-world-name: world
event-world-name: 'dragonevent_end'
worldguard-region-name: dragonportal
| Setting | Role |
|---|---|
lobby-world-name | The world holding the entrance region |
event-world-name | The name of the world the fight happens in |
worldguard-region-name | The WorldGuard region in lobby-world-name that players walk into to join |
The lobby spawn itself is set with /dragon setlobbyspawn and can be in any world but the event
world.
Three ways to provide the event world
custom-world:
enabled: false
type: CUSTOM
folder-name: ""
| Setting | The event world | Between events |
|---|---|---|
enabled: false (default) | A new end world named event-world-name, generated by the plugin | Deleted and generated again before every event |
enabled: true, type: CUSTOM | A copy of the map in plugins/uxmDragonEvent/<folder-name> | The copy is deleted and made again from the original before every event |
enabled: true, type: VANILLA | An existing, loaded world named event-world-name | Left as it is |
Generated is the simplest: every event starts in an untouched end.
Custom is for an arena you built. See A custom event world for the setup.
Vanilla uses a world you already have, and keeps it between events, so anything the dragon or
the players break stays broken. The plugin does not build the spawn platform, apply the world
border or set the game rules in it. Set the dragon's spawn with /dragon setdragonspawn while
standing in that world; without it the event ends as soon as it starts. Set the players' spawn with
/dragon setcustomspawn, or use spawn-type: SURFACE, since there is no platform to land on.
A vanilla event world belongs to the event: outside an event nobody can teleport into it, and players who log in there are sent to the lobby spawn. Pointing it at the end your players use every day closes that end to them.
In the default mode the folder named event-world-name is deleted before every event and when the
plugin reloads. Never give it the name of a world you want to keep. Only type: VANILLA leaves the
world alone.
Game rules in the event world
When the plugin generates or copies the event world, it sets three game rules from end-rules:
| End rule | Game rule |
|---|---|
keepInventory | keepInventory |
announceAdvancements | announceAdvancements |
showDeathMessages | showDeathMessages |
end-rules.generateStructures: false keeps end cities out of a generated world. See
End rules for the rest.
The world border
world-border:
enabled: true
size: 1000
center-x: 0
center-z: -30
size is the full width in blocks, not the distance from the centre. The default is a 1000 block
square centred on the spawn platform.
The border keeps the fight in one place. Without it, the dragon can drift toward the outer islands
and take the event with it. In a custom world, set center-x and center-z to your arena's centre
and size it to the arena: a border far larger than the arena is the same as no border.
End crystals
settings:
delete-end-crystals: true
Removes the crystals on the end pillars, the ones that heal the dragon, shortly after each player
joins. Keep it on in a generated end: a fight where players first have to break ten crystals is far
longer than dragon-event-time usually allows. If you want that fight, turn it off and raise the
timer.
end-rules.disableCrystalDamage and disableCrystalDestroy control what crystal explosions do.
Players left in the event world
The event world is only for players in the event:
- When an event ends, every player in the event is sent to the lobby spawn.
- When the next event starts, anyone still in the world is sent to the lobby spawn first.
- A player who logs in inside the event world without being in the event is sent to the lobby spawn.
- Teleporting into the event world without joining is refused, except for players with
dragonevent.adminordragonevent.teleport.bypass.
Was this page helpful?