Mystical Realms Modpack Fixes

v1.2.1 - Better Party guard gating fix

Bug-fix release. The Better Party member-health crash guard added in v1.2.0 was silently disabled and never applied, so the crash it was meant to prevent kept happening. No new features.

Fixed

• Soft-mixin gating disabled the guard entirely: BvaMixinPlugin.shouldApplyMixin decided whether to apply the optional-mod mixins by calling ModList.get().isLoaded(modId). Mixin queries config plugins while it prepares its configs, a phase that runs before FML has finished populating ModList, so the check saw a not-yet-ready list and answered false — which permanently disables that mixin for the entire session. Result: BetterPartyMemberHealthGuardMixin never mixed into BetterPartyServerApi, and PartyMemberHealth's uncaught IllegalArgumentException (thrown whenever a player's generic.max_health is momentarily <= 0/non-finite) kept propagating out of the event bus and crashing the whole dedicated server. The same bug also silently disabled the two Better Villager Animations dialogue-translation mixins.
• The plugin no longer gates at all. Every mixin in this mod's config is either an always-on vanilla target or a @Pseudo mixin aimed at an optional mod; @Pseudo already makes Mixin skip a mixin harmlessly when its target class is absent, so gating was unnecessary and only ever caused this failure mode.
• Added a postApply log line ([utility_nexus_fixes] Applied Better Party member-health guard to ...) so it is obvious in the server log when the guard is active.

Notes

Verified against better-party-neoforge-1.21.1-1.1.7.jar on a dev dedicated server: the mixin now reports Mixing BetterPartyMemberHealthGuardMixin from utility_nexus_fixes.mixins.json into dev.betterparty.api.v1.server.BetterPartyServerApi with no injection errors. As before, this patch stops the crash; it does not fix whatever corrupts the player's generic.max_health attribute in the first place.

JAR: utility_nexus_fixes-1.21.1-neoforge-21.1.249-1.2.1.jar

Tag: 1.21.1-neoforge-1.2.1