Retold

Patch release focused on reliability, automated coverage, and the ocean-monument guardian crash fix.

Player-Facing

• Updated packaged mod metadata to use Retold branding, the current generated version, and working project and issue-tracker links.
• Fixed territory suspicion carrying process-wide save and decay timing between worlds; reputation now belongs to the current saved world.
• Fixed a crash when a non-player mob, such as a drowned, damaged a guardian at an ocean monument.

Technical

• Added separate MIT code and protected creative-asset licenses, including permission to redistribute the complete, unmodified Retold JAR in modpacks.
• Added structured bug and suggestion forms, a pull-request template, and monthly Gradle and GitHub Actions dependency checks.
• Added SHA-256 checksum assets to the release workflow.
• Updated the Gradle wrapper, ModDev, JUnit, and GitHub Actions dependencies used by builds and releases.
• Moved territory reputation into versioned Minecraft SavedData with safe one-time migration and retained backups for legacy JSON data.
• Updated NeoForge metadata to report the split code/asset license and routed Aender cleanup and recipe inspection failures through structured logging.
• Added deterministic GameTests for Aender portal shapes, coordinate scaling, counterpart creation, stability serialization, and volatile-chunk regeneration policy.
• Added deterministic Gale Core GameTests for activation, damage aggro, phase changes, disengagement, serialization, and duplicate-spawn repair.
• Fixed AI sight-cache cleanup detaching the current observer's fresh result and forcing avoidable repeat raycasts.
• Added a regression GameTest verifying that guardian defense assist safely ignores non-player attackers.