World Resets

A reset wipes a world and regenerates it with a new seed. This page covers when resets fire and what happens step by step.

Scheduling modes

Each world resets on its own schedule. Pick one of two modes with reset-schedule.mode.

Interval

Reset every reset-interval-days days, rolling from the last reset. Good for "every 3 days" style cycles.

Weekly

Reset on a fixed day and time, for example every Friday at 21:00. Set the day and time under reset-schedule.weekly.

Set either mode in-game:

/zrm setinterval nether 3
/zrm setschedule nether interval 3
/zrm setschedule nether weekly FRIDAY 21:00

Setting a schedule also enables the world. If a world was disabled, /zrm setinterval or /zrm setschedule turns it back on.

Time zones for weekly resets

Weekly resets fire against the timezone set at the top of config.yml. If your host runs on UTC but you think in local time, set your IANA zone (for example Europe/Paris) so a reset at 21:00 fires at 21:00 your time. A bad value falls back to the system zone. Interval resets do not care about the zone.

What happens during a reset

The sequence runs in this order. If a step fails, the reset aborts before anything is destroyed.

  1. Countdown warnings. Players get a broadcast at each minute mark in countdown-warnings (60, 30, 10, 5, 1 by default).

  2. Evacuate players. Everyone in the world is teleported to fallback-location in fallback-world.

  3. Save the spawn region (if enabled) to its schematic file. If this fails, the reset stops here so nothing is lost.

  4. Unload and delete the world folder off the main thread.

  5. Regenerate the world with a brand new random seed.

  6. Paste the spawn region back into the new world.

  7. Run post-reset commands (if any), after a short delay.

  8. Announce completion with the new seed.

Countdown broadcasts

countdown-warnings is a list of minute marks, in descending order. Add or remove entries per world.

countdown.broadcast-radius controls who hears the warning:

  • -1 sends it to every online player, on any world. Best for Nether or End resets that everyone should know about.

  • A positive number only warns players within that many blocks of the resetting world’s spawn.

Missed resets

If the server was offline when a reset was due, missed-reset decides what happens on startup:

immediate

Run the missed reset as soon as the server starts.

skip

Skip it and schedule the next one from now.

delay

Wait missed-reset-delay-minutes after startup, then run it. This is the default.

Seed history

Every new seed is logged to console and to plugins/zResetMap/seeds.log with a timestamp and world name, so you can look up or reuse a past seed.

After a reset

Two optional follow-ups pair well with resets:

  • World Lock keeps players out while the fresh world pre-generates.

  • Post-reset commands can kick off chunk pre-generation from another plugin. See the config page.