Mystical Realms Modpack Fixes

v2.0.0 - Renamed to Mystical Realms Modpack Fixes

Breaking change: this mod has been renamed. "Utility Nexus Fixes" is now "Mystical Realms Modpack Fixes" — same author, same patches, same behavior, new identity. It leaves the utility_nexus_* family (Utility Nexus Admin/QoL/Core are unaffected) to stand on its own as a mod built for and named after the Mystical Realms modpack.

What you need to do when updating

• Remove the old JAR (utility_nexus_fixes-...jar) before adding this one — NeoForge treats the new mod_id as a different mod, it will not replace the old one in place.
• Config moved: config/utility_nexus/fixes/config.toml → config/mystical_realms_modpack_fixes/config.toml. If you changed any setting from its default, reapply it in the new file (the old one can be deleted).
• No functional changes otherwise — every patch behaves exactly as in 1.4.0.

Changed (BREAKING)

• mod_id: utility_nexus_fixes → mystical_realms_modpack_fixes
• Java package: com.skd.utilitynexusfixes → com.skd.mysticalrealmsmodpackfixes
• Assets namespace: assets/utility_nexus_fixes/ → assets/mystical_realms_modpack_fixes/
• NeoForge data-attachment registry name changed accordingly — any previously-remembered Nether return-portal mapping is dropped and regenerates on its own (in-memory-equivalent convenience data, not a data-loss concern)
• Repository moved to gitlab.com/stalking-dragons/minecraft/mystical-realms-modpack-fixes

JAR: mystical_realms_modpack_fixes-1.21.1-neoforge-21.1.249-2.0.0.jar

Tag: 1.21.1-neoforge-2.0.0