DyClaim v1.0.2 — Maintenance Update

Maintenance changes from v1.0.1, focused on clearer commands, console administration, claim protection and failure recovery.

Fixed

• Server console senders can reload and manage global configuration through the existing admin commands; console help and TAB suggestions match the supported commands and permission checks.
• Trust-right editing is available under /claim trust <player> <right> <allow|deny> and mob explosions under /claim explosion mob. Help and root TAB no longer advertise separate trustperm and mobexplosion commands; existing English/Turkish aliases remain valid.
• Invalid explosion arguments no longer toggle a setting, and denied trust-right permissions no longer also report that the feature is disabled.
• Recognized shipped help and usage messages follow the grouped commands when loading older message files, while custom translations remain intact.
• Turkish TAB completion accepts ASCII prefixes while retaining localized suggestion text.
• Administrator TAB suggestions respect the additional purge and bypass permissions, including bypass arguments.
• Hostile mob spawning checks and the optional hostile cleanup scope include slime, ghast and phantom through Spigot's Enemy interface. Existing spawn-reason filters and passive-animal behavior remain unchanged.
• Reload and shutdown invalidate active inactive-claim purge batches, preventing continued deletion under old rules, including shutdown during a refunded deletion within the current batch.
• A failing shutdown component no longer prevents independent claim saving and visualization cleanup; failures are logged with their cause.
• Failed transaction journal stage writes preserve the prior stage in memory, keeping locked transactions visible for reconciliation.
• Administrative delete and bulk-sale batches stop after reload or shutdown, including shutdown triggered by a failed refund mutation.
• Bulk sales recheck the confirmed refund before each remaining claim, preventing removal under changed economy or refund settings.
• New financial transactions are rejected after claim storage becomes unwritable, preventing further payments in a price-difference refund batch.
• Mob-fired explosive projectiles use the mob-explosion setting consistently for blocks, protected entities and hanging entities, including when the ordinary explosion setting differs.
• Optional mob cleanup rechecks the current spawning choice while consuming a batch, so enabling mob spawning preserves queued mobs when cleanup is restricted to spawning-disabled claims.

Documentation

• Added short comments to the default configuration and English/Turkish message files without changing keys, values or placeholders.
• Recorded the second review's automated tests and isolated Purpur 1.20.4 scenarios in the compatibility notes.

Compatibility

• Retained schema 2, existing configuration, commands, permissions, English/Turkish messages, Java 17 bytecode target and Spigot API 1.20.4 baseline.
• No dependency updates or new features.

Verification and upgrading

148 automated tests and targeted Purpur 1.20.4 scenarios. The full historical server matrix and real optional integrations were not repeated for this release. Back up the existing JAR and complete DyClaim data folder before replacing the JAR with the server stopped. Existing stable claim data and legacy command aliases are retained.