promotional bannermobile promotional banner

LRM Fixes

Patches API breaks between mods so you can keep updating instead of holding a mod back. Each patch is an independent mixin that cites the bytecode proving the break, and fails inert if its target is absent.
Back to Files

lrm-fixes-1.0.0.jar

File namelrm-fixes-1.0.0.jar
Uploader
BahanosBahanos
Uploaded
Aug 7, 2026
Downloads
5
Size
4.5 KB
Mod Loaders
Fabric
File ID
8591825
Type
R
Release
Supported game versions
  • 1.20.1

Curse Maven Snippet

Fabric

modImplementation "curse.maven:lrm-fixes-1642385:8591825"

Learn more about Curse Maven

What's new

LRM Fixes 1.0.0

Added

  • FIX-01: Berserker Class Mod x More RPG Classes. CustomMethods.clearNegativeEffects(LivingEntity, boolean) returned boolean up to More RPG Classes 1.2.18 and returns void from 1.2.19 on. The return type is part of the JVM signature, so the old descriptor no longer exists, and Berserker 1.2.5 still calls it from CustomSpells.lambda$register$3 - the outrage spell at maximum RAGE. Casting it threw NoSuchMethodError.

    • The patch resolves the method by name and parameter count, never by return type - which is exactly what broke. It therefore keeps working whether upstream returns boolean, void, or something else later.
    • The redirect cannot change gameplay: Berserker discards the return value (pop immediately follows the call in its bytecode), so no value this mod returns is ever read.
    • The handle is resolved once and cached.
  • Fail-inert by design. Mixins are declared with defaultRequire: 0. If a target mod is absent, or upstream finally fixes the signature, the patch is skipped instead of breaking startup. It can never become the reason your game will not launch.

  • Logs that report the effect, not the intention. Startup says 1 patch armed - armed means registered, not proven, which is all that is true at that moment. Each patch then logs once more, the first time it actually intercepts a call:

    [FIX-01] redirected a live call to CustomMethods.clearNegativeEffects - the patch is doing its job
    

    That second line cannot appear unless the patch has genuinely done something, so it answers the only question that matters for a compatibility mod. Its absence is informative too: the broken code path was simply never reached in that session. A patch that fails inert would otherwise be indistinguishable from one that works.

Compatibility

  • Minecraft 1.20.x, Fabric. Works on client and server.
  • No dependencies beyond Fabric Loader. The mods it patches are optional at runtime - the mod does nothing at all if they are not installed.
  • No config, no world or save data, no items or blocks. Drop in and remove freely.

This mod has no related projects