UniMixins Mod FAQ

Check your game log for UniMixins startup messages during launch, which appear before the main mod list loads. If you see mixin-related errors referencing UniMixins, it is loading but something else is wrong.

The combined jar is the simplest option and works for most players. Use separate modules only if you want to run UniMixins alongside another mixin loader and need to avoid feature overlap.

Two loaders providing the same extra feature will conflict, causing a crash during mixin application. Disable the overlapping module in UniMixins or remove the other loader's equivalent feature.

Install only the specific UniMixins modules that the other loader does not already provide. Keep the combined jar out of your mods folder in this setup, since it bundles everything.

Start with the base mixin module, then add extras only when another mod explicitly requires them. If nothing requires a specific extra, leaving it out reduces the chance of conflicts.

Support for those versions is partial, so some modules may not function or may behave differently than on 1.7.10. Test with your specific modpack before relying on it there.

Yes, but any mod that depends on a UniMixins module will fail to load or crash without it. Check your mods' dependencies before removing it.

This usually means a feature overlap where UniMixins handles the same mixin target differently. Try disabling the relevant UniMixins module or check the log for which loader claimed the mixin first.

Mixin loading adds a small startup cost, but runtime performance impact is generally negligible. Extra modules you do not need can add unnecessary overhead, so keep only what is required.

Identify which two loaders or modules are providing the same feature from the crash log, then remove or disable one of them. Running only the base module alongside another loader often resolves it.