• Separate break and placement delays. Replace a broken floor quickly while allowing temporary cover to last longer. Add material-specific delays for blocks such as wool.
• Fluid tracking. Record water and lava spread, level changes, supported waterlogged flow, and mixing products such as stone, cobblestone, obsidian and basalt. Fluid tracking is enabled by default, independently of general natural-change tracking.
• Control what gets restored. Include or exclude materials, choose whether original air removes new builds, and configure placement, explosion, fluid and supported natural-change tracking.
• Player-aware restoration. Defer blocks that would intersect players. Optionally preserve temporary blocks beneath their feet until removal is safe, or wait until the arena is empty.
• Boundary protection. Block supported liquid and piston movement across the arena boundary.
• Arena menus. Change modes, delays, intervals, automation, drops, air restoration and notifications from a restrained gold-and-gray inventory menu.
• Subzones. Give a floor, building section or decoration area its own supported local rules while sharing the parent arena's snapshot and schedule.
• Reusable profiles. Save an arena's settings and apply them to another arena without copying its world or blocks.
• Drop controls. Configure direct player-break item and experience drops.
• Notifications. Use chat, action bar or no announcements, with configurable warning and completion messages.
• English and Spanish. Switch the server-wide plugin language in game; the choice survives restarts.
• Recovery tools. Compressed snapshots, a previous-capture backup when available, saved pending changes, retry commands and cancellable jobs.
• Bounded processing. Arenas share a configurable block and time budget each tick. Changed-only modes avoid routine full scans when they are unnecessary.
• Integration API. Other plugins can listen to the cancellable BlockRestoreEvent to veto individual writes. Administrative commands can also be called by compatible command-based integrations.

Large resets still take work. A manual reset starts processing on the next server tick, but completing a large arena can take multiple ticks. Performance depends on region size, chunk loading, configuration and server hardware.

This example creates practice: broken blocks return after 5 seconds, placed blocks after 20 seconds, and fluid changes are tracked. Players can remain in the arena while individual blocks regenerate.

1. Build first, then select the entire volume.

Run these commands in game as an operator or an administrator:

/rz language en
/rz wand

With the golden hoe, left-click the first corner and right-click the opposite corner. Include the floor and enough air above it to contain player builds and liquid spread. Both corners are included. The selection must be in one world and must not overlap another arena.

2. Save the original layout.

/rz create practice

Wait for the snapshot saved confirmation before continuing. This snapshot is the layout Regen Zone will restore, so capture the finished arena before players damage it.

3. Apply the rules. Run one command per line.

/rz set practice enabled false
/rz set practice mode block
/rz set practice block-delay-seconds 10
/rz set practice break-delay-seconds 5
/rz set practice place-delay-seconds 20
/rz set practice block-wait-until-empty false
/rz set practice restore-air true
/rz set practice track-placements true
/rz set practice track-explosions true
/rz set practice track-fluids true
/rz set practice track-natural-changes false
/rz set practice protect-boundary true
/rz set practice protect-player-floor true
/rz set practice drop-items false
/rz set practice drop-experience false
/rz set practice notification-channel none
/rz set practice enabled true

restore-air true matters: if a player builds where the snapshot contains air, regeneration removes that build. Liquid cleanup and other restoration still respect material filters and protected block entities.

4. Inspect and test.

/rz info practice
/rz menu practice

Break a normal block, place another in an originally empty position, and check both timers. Move clear of positions being restored. To restore the whole saved area manually:

/rz regen practice

Optional: make wool restore in three seconds.

/rz material practice WHITE_WOOL 3

Material delays override the category delay. Remove that override with:

/rz material practice WHITE_WOOL remove

Prefer a changed-only reset every minute? Replace the block mode with:

/rz set practice mode changes
/rz set practice interval-seconds 60
/rz set practice wait-until-empty true
/rz set practice empty-seconds 5

This waits for the interval and an arena that has been empty for five seconds, then processes pending changes. If nothing was tracked, there is no reset job. The individual five- and twenty-second timers apply when using block mode.

After rebuilding the original arena, replace its saved layout deliberately:

/rz save practice confirm

Do not run save to clean up damage: it makes the current blocks the new original. Use regen to restore the existing original.

Use /rz or /regenzone. Angle brackets indicate required arguments; square brackets indicate optional arguments. Do not type the brackets. Selection and menu commands require an in-game player. Use TAB for available arena names and supported setting options.

Spanish aliases remain available in either language: ayuda → help, crear → create, guardar → save, recuperar → recover, reintentar → retry, cancelar → cancel, ver → show, ocultar → hide, lista → list, borrar → delete. lang and idioma are aliases for language. Confirmation accepts both confirm and confirmar.

Profiles copy settings, not blocks, boundaries or subzones. Subzones share their parent's snapshot and schedule; they do not create independent regeneration engines. Configuration changes affect future events and do not rewrite every existing block deadline.

All administrative nodes default to operators only. regenzone.support is available to everyone by default. A permissions plugin can grant or deny individual nodes; installing one is optional.

Players do not need an administrative Regen Zone permission simply to play in an arena. Protection rules still apply to them. Granting menu access alone does not grant editing access.

Regen Zone restores block states inside a saved cuboid. It is not a complete world-backup system.

• Original air can be restored, so player-built blocks disappear when the configuration permits it.
• Block entities such as chests, signs and spawners are protected rather than fully serialized and rebuilt. Inventories and their contents are not reset.
• Players, creatures, dropped items, paintings, armor stands, biomes and other plugins' metadata are not restored.
• Changes outside the selected bounds belong to the outside world. Include the necessary height and keep boundary protection enabled for fluid-heavy arenas.
• General natural-change tracking is optional. Fluid tracking does not enable every unrelated growth, fire or physics event.
• Other plugins' cancelled events are ignored. Plugins that write blocks directly may bypass event tracking; a full manual reset or interval scan can reconcile those positions.
• Waiting rules, player safety checks, material filters and integration vetoes can postpone or prevent particular writes.
• Pause automatic scheduling with enabled false. To stop an already active world operation, also use cancel.

For old fluid residue left by releases before 0.3.4, run one full /rz regen <arena> after updating. Do not overwrite your clean snapshot with the damaged layout.

See the documentation for configuration details, storage behavior and integration guidance. The hosted guide may describe an earlier release; the source package includes the updated Markdown guide.