FAQ
My spawn build did not come back after a reset
Check three things:
-
spawn-region.enabledistruefor that world. -
You actually saved the region with
/zrm savespawn <world>after setting both corners. -
paste-at-corner1istrue, so the build pastes back where you saved it.
If the schematic file at save-path does not exist, the save never ran. Set the corners and run /zrm savespawn again.
My chests came back empty
Block data is preserved, but tile-entity contents are not yet. The chest, sign, or barrel comes back, but not what was inside it. This is a known limit, planned for a later version. See Spawn Protection.
The weekly reset fired at the wrong time
Weekly resets use the timezone set at the top of config.yml. If your host runs on UTC but you read local time, set your IANA zone, for example Europe/Paris. A reset at 21:00 then fires at 21:00 in that zone. A bad value falls back to the system zone.
A world shows as disabled even though I set a schedule
Setting a schedule enables the world. If it still shows disabled, run /zrm setinterval <world> <days> or /zrm setschedule … again, then check /zrm status <world>.
Players are still getting into a world right after a reset
Turn on lock-after-reset for that world, or lock it by hand with /zrm lock <world> <duration>. See World Lock.
Do I need WorldEdit?
No. zResetMap saves and pastes the spawn region with its own lightweight schematic. No WorldEdit or FAWE required.
Does it need internet access?
Only on the first start, to download boosted-yaml through Spigot’s library loader. After that the library is cached and the plugin runs offline.
How do I add another language?
Copy lang/en.yml, translate the values, set language to your new file’s name, and run /zrm reload. See Messages & Language.
Where are the seeds logged?
Every new seed goes to console and to plugins/zResetMap/seeds.log with a timestamp and world name.
The reset did not run while the server was offline
That is expected. missed-reset decides what happens on the next startup: immediate, skip, or delay. See Missed resets.
Still stuck? See Support.