Zones

Six modules turn a region of the world into something. All six are built from admin menus and stored in the database.

Mines, regenerating zones, AFK zones, jump pads and power-up zones record the server that created them. On a network whose servers share one database, each server loads and lists only its own. A row written before the server was recorded belongs to every server that reads it. Portals do not record a server.

Mines

A mine is a region that comes back. There are two kinds, and you pick which when you create it.

Classic

The whole region is rebuilt at once, from a composition — a weighted list of materials.

A player standing inside when it resets is a problem the mine solves for you: teleport to air lifts them to the nearest open block instead of letting them suffocate, and a safe teleport location can be set as well.

Realistic

Blocks do not come back all at once. Each block has levels — a chain of degrade stages it passes through as it is mined, each with its own regeneration time, loot and effects. mine_levels, mine_level_detail and mine_level_chain in the admin menus are where that chain is written.

default-realistic-regen-seconds is 60.

Every block still broken when the module starts is healed at once, whatever time it had left. A restart does not resume the timers. A block whose chunk is not loaded stays tracked and is retried every 10 seconds until the chunk loads; its row is only deleted once the block is back. Rows for a mine this server does not know are left alone, since on a shared database that mine belongs to another server.

Both kinds share: an entry teleport, a permission, auto-pickup — mined blocks go straight to the inventory — restrict-breaking, which stops anything not in the mine's own list from being broken, and break effects.

visuals carries the reset warning title, the reset boss bar, the entry title and the "next reset" bar, with %mine_name%, %seconds%, %next_reset% and %time%.

The "next reset" readout inside a classic mine is a boss bar, visuals.bossbar, no longer an action bar. It empties as the reset comes closer and gives way to the reset countdown bar for the warning seconds. An existing modules/mines/config.yml keeps its text: visuals.actionbar.text is moved to visuals.bossbar.text.

Breaking a block in a mine

A break the mine owns is performed by the plugin, not by the game:

• Experience goes straight to the miner, Mending included, instead of dropping an orb.
• The tool takes damage through the server's own path, so Unbreaking applies, PlayerItemDamageEvent fires and the tool breaks with its sound.
• Each drop and each loot item is offered to autosell first, for a player who has it on. See Economy.

Other plugins' tools break mine blocks through the same path. A 3x3 pickaxe calling breakMineBlock in the API gets the mine's permission check, its loot and its regeneration on all nine blocks. A MineBlockBreakEvent is fired before every such break, and cancelling it leaves the block alone.

Regenerating zones

A region saved as a schematic and pasted back over itself. Built from /regenzonesadmin; the schematic button in the editor saves the region as it stands right now, which is the state it will be restored to.

Two modes:

The warning applies to FIXED only.

The flags screen is ExyliaLib's region policies, one row per flag, cycling allow → deny → default. Two extra keys sit alongside them: an allowed-blocks list, and a seconds value for temporary blocks.

ExyliaLib only resolves the flags; this plugin is what enforces them, in every region it registers. A player in creative mode is held by none of them.

The temporary-blocks seconds only reach ExyliaLib while TEMPORARY_BLOCKS is on.

AFK zones

Stand in the region, get paid on a timer. /afkzone preview <id> shows what a zone pays.

Each zone has its own interval and its own reward list. visuals covers the boss bar, the entry title, the reward title, the action bar, and the two lines of the summary a player gets when they leave, with %zone_name%, %time_in_zone%, %next_reward%, %amount% and %reward_name%.

Item rewards are never dropped on the floor. On the first interval after a player's inventory fills up, they are told with afk-zones.inventory-full, and that round's items are kept for them and handed over on their next join. Every interval after that skips the item rewards until they make room. Money, commands, experience and messages need no room and are always paid.

Portals

A region that teleports whoever walks into it, or runs commands on them, or both. Built from /portalsadmin.

A portal is a region, a destination and a command list, stored in the database. The setup screen adds three more things:

modules/portals/config.yml holds what every portal shares:

settings:
  cooldown-seconds: 2
effects:
  enter-sound: "BLOCK_PORTAL_TRAVEL|0.4|1.6"
  enter-title: { … }   # %portal% is the portal's name

cooldown-seconds is how long the same portal waits before it takes the same player again, which is what stops two portals pointed at each other bouncing somebody back and forth. 0 turns it off. The wait is kept in memory and cleared when the player leaves.

A portal whose destination cannot be reached tells the player why, with the teleport lines described in Movement.

Jump pads

A block that launches whoever steps on it.

settings.launch-cooldown-ms is 500 by default. A gliding pad waits for the player to leave the ground before opening the elytra, and a pad is only looked up when a player changes block — not on every movement packet.

Power-ups

A floating item a player walks over to get a potion effect or a reward. They live in zones, and a zone spawns them either anywhere inside an area or at a list of fixed locations.

Each power-up has an icon, a name, a weight, potion effects, rewards, and a glow with a colour of its own.

The floating items are drawn packet-level through PacketEvents, a hard dependency of the plugin.