Arena Regen Extension - Duels Optimized v1.3.0

💾 Snapshots Survive Restarts

Snapshots used to live only in memory, which caused two quiet problems.

With snapshot-each-match: false, every restart wiped your reference snapshot and regeneration stopped until you ran /duelregen save again. With it set to true, a crash mid-match left the arena wrecked with nothing to restore from.

Snapshots are now written to disk as they are captured, into plugins/Duel-Regen/snapshots/. Writing happens in the background and is done safely, so a crash partway through cannot corrupt a file you already had.

persist-snapshots: true

On by default. Turn it off if you would rather keep the old behaviour.

🔄 Crash Recovery

Because snapshots are on disk, the plugin can work out what happened while the server was down.

• With snapshot-each-match: true, a snapshot sitting there at startup can only mean the server went down mid-match, so that arena is regenerated automatically
• With snapshot-each-match: false, the file is your pristine reference. It is loaded straight back into memory and the arena is left alone

Loading happens off the main thread at startup, so it costs you nothing, and a snapshot already in memory is never overwritten by a file.

FAWE and WorldEdit snapshots are saved as standard Sponge schematics, so you can open one in WorldEdit yourself if you ever need to. A snapshot file from a different Minecraft version, or one that has been damaged, is skipped with a warning rather than restoring something broken.

🔤 Hand-Edited Arena Names Work

If you set regions up by editing the config rather than using the wand, the key had to match the Duels arena name exactly. Write arena_2 for an arena called Arena2 and every arena warned that no region was configured, with nothing regenerating.

Names are now matched loosely when an exact match fails, ignoring capitals, underscores, hyphens and spaces, so arena_2 finds Arena2. The console tells you once and suggests renaming the key, and any two keys that would collide are reported.

Your config is also checked against Duels at startup. A second after the server starts, the plugin compares your keys with the arenas Duels actually has, and reports any key that matches no arena, along with any Duels arena that has no region at all. If a fuzzy match will cover it, it says so.

config.yml now documents hand-editing properly, with a full example block and a note that keys are Duels arena names rather than world names. Handy if you already have the coordinates, say from a WorldGuard region, and would rather paste them than use the wand.

🛠 Also Fixed

/duelregen remove deleted nothing when you typed a loosely matched name. It found the region but removed it under the name you typed rather than its real key. It removes the right one now.

📦 Install

Stop the server, replace the old jar in plugins/ with Duel-Regen-1.3.0.jar, and start it again. Your config and your arenas carry over, and the new keys are added for you.

Worth doing once afterwards: read the console on that first start. The new cross-check will name any arena whose key does not line up with Duels.

📋 Version Breakdown

🧪 Compatibility

Minecraft 1.18.2 through 1.21.11.

🛠 Arenas Regenerate Reliably

Several things could stop an arena regenerating with no error in the console, so the first you knew was a broken map. All of them are fixed.

• Arenas in a world loaded by a world manager. If the world was not ready when the plugin started, that arena dropped out for the rest of the session, with no snapshot and no regen. Worlds are now resolved when they are actually needed
• snapshot-each-match: false regenerated an arena exactly once. Everything after the first match had nothing left to restore from. Snapshots are now kept when you are not taking a fresh one each match
• Entity cleanup did nothing on 1.20.5 and newer, because Minecraft renamed a few entity types. Both the old and new names are accepted now, and an entity name the server does not recognise is reported instead of ignored
• Load order was undefined. The plugin now loads properly after Duels, WorldEdit or FAWE, and common world managers
• Starting a match while a regen was still pending could reset the arena mid-match. Pending regens are cancelled properly now
• A world reload could break a regen partway through, and very large regions could be measured wrong

🔔 You Find Out When Something Is Wrong

Most of what went wrong before went wrong in silence. Now it does not:

• A warning when a match starts in an arena with no region configured, or whose world is not loaded. Once per arena, so it does not flood your console
• A startup check that reports any arena pointing at a world that never loaded
• A startup warning if Duels is missing or failed to enable
• /duelregen info and /duelregen list show whether each arena's world is loaded
• /duelregen reload tells you how many arenas it loaded
• A debug option for verbose snapshot and regen logging when you need to see exactly what is happening

📦 Install

Stop the server, replace the old jar in plugins/ with Duel-Regen-1.1.0.jar, and start it again. Your config and your arenas carry over.

Worth doing once afterwards: watch the console on that first start. If any of your arenas were quietly broken, this is the build that tells you which.

🧪 Compatibility

Minecraft 1.18.2 through 1.21.11. Nothing changed on the Duels side, so this works with the same versions it always did.

latest