PerWorldChange

What's New in PerWorldChange 1.3.0

PerWorldChange 1.3.0 is a modernization and quality-of-life update focused on safer world switching, easier configuration, and less repeated admin work.

New Features

• Added /pwc reload: Reload config.json without restarting the server.
• Added per-player gamemode memory: Worlds without an explicit worldGamemodes entry now remember each player's last gamemode for that world.
• Added safer config reload behavior: If the JSON is malformed, the previous valid config stays active.
• Added config validation: Invalid gamemode names, duplicate worlds, blank entries, and suspicious config references are logged clearly.
• Added dedicated wildcard matching utility: Wildcard world matching is cleaner and covered by tests.

Improvements

• Improved dungeon and instance handling: Instance worlds continue to inherit from their origin or parent world where possible.
• Improved debug logging: Debug logs now include player name, source world, destination world, resolved inventory group, and applied gamemode.
• Improved inventory saving: Inventory disk writes are handled asynchronously with save coalescing to reduce world-switch overhead.
• Improved fallback behavior: Unconfigured worlds now fall back to a default group when present, otherwise they use isolated world-specific storage.
• Updated documentation: README and CurseForge description now include 1.3.0 features and the reload command.

Compatibility

• Built against Hytale release server build 2026.03.26-89796e57b.
• Does not target pre-release server builds such as 0.5.0-pre.*.

Notes for Server Owners

• Replace the old jar with PerWorldChange-1.3.0.jar.
• Review your config.json after updating.
• Use /pwc reload after config edits instead of restarting when possible.
• If you want a world to force a specific gamemode every time, keep it listed in worldGamemodes.
• If you want admins' manual gamemode changes to stick per player, leave that world out of worldGamemodes.