Mixin Helper

Take control of mixin conflicts in your modpack. Mixin Helper lets you blacklist, prioritize, and surgically modify mixins from any loaded mod — all from a single JSON config file. No code, no recompiling, no removing mods.

Documentation

Full documentation, guides, and examples at https://tysontheember.dev/mixin-helper/intro/

---

⚠️ USE AT YOUR OWN RISK ⚠️

This is an advanced tool. If you don't know what mixins are or how they work, this mod is not for you.

While there are guardrails Mixin Helper directly interferes with how other mods patch the game. Incorrect use will break things. This includes but is not limited to:

• Game crashes with difficult-to-diagnose stacktraces
• Broken mod features that may not be immediately obvious
• World corruption — back up your worlds before making changes
• Incompatible save files if disabled mixins affect world data

Do NOT report bugs to mod authors if you have modified their mixins with this tool. Any issues caused by Mixin Helper are your responsibility.

---

Features

• Mixin Blacklisting — Disable individual mixins, entire mixin configs, or block all mixins targeting a specific class
• Priority Control — Override mixin execution order to resolve load-order conflicts between mods
• Method Removal — Neutralize or remove specific injected methods without disabling the entire mixin
• Audit Report — Generate a detailed JSON report of every loaded mixin config, including annotations, to diagnose conflicts fast

Supported Versions

Minecraft Version	Loader	Status
1.20.1	Forge	Fully Supported
1.20.1	Fabric	Fully Supported
1.21.1	NeoForge	Fully Supported
1.21.1	Fabric	Fully Supported

How It Works

1. Install Mixin Helper — drop the jar in your mods folder
2. Launch the game — a default config is generated at config/mixinhelper.json
3. Check the audit report at config/mixinhelper-report.json to see every mixin loaded in your game
4. Edit the config to blacklist, reprioritize, or strip methods as needed
5. Restart and you're done

Quick Example

Two mods crash because they both modify the same class? Blacklist the offending mixin:

{
  "enabled": true,
  "blacklist": {
    "mixins": ["com.conflictingmod.mixin.MixinLevelRenderer"],
    "mixinConfigs": [],
    "targetClasses": []
  }
}

Need finer control? Neutralize a single injected method instead of the whole mixin:

{
  "methodRemovals": {
    "rules": [
      {
        "targetClass": "net.minecraft.world.level.Level",
        "method": "brokenMethod",
        "action": "nop"
      }
    ]
  }
}

Use Cases

• Modpack developers resolving mod conflicts without waiting for mod authors to fix them
• Server admins disabling specific mod behaviors that cause instability
• Debugging which mixins are causing crashes or unexpected behavior
• Fine-tuning mod interactions by controlling execution order

Notes

• Config changes require a full game restart — mixins load very early in startup
• Mixin Helper itself has no mixins — it uses the Mixin plugin system to intercept other mods
• Zero runtime performance impact — all work is done during startup