In this article
We’re not addicted to shipping panel updates. We can stop anytime… honest.
5.12 is now live on all nodes and it brings a shiny new toy: the Minecraft Mod Manager. Let’s dive in. Ever built your own modpack, it runs fine in single-player, you upload it to a server… and it just doesn’t. So frustrating. Nine times out of ten the culprit is a client-only mods. See these mods are never meant to run on servers, so they call client code that just isn't there, then boom a crash. Problem is there is really no easy way to sort client only mods, for the ones that do work on servers. Until now... The Mod Manager lets you scan your mods and flags anything that’s client-only so you can disable it before it ruins your day.
How the scan works,
Light scan - quick pass that reads mod metadata to spot client-only mods. Deep scan (slower) - peeks into the code to infer client/server. Great for tracking down that pesky outlier. (Heads-up: deep scans can over-flag, so treat it as a debugging tool.)
Change log,
Clicking the mods folder now opens the Mod Manager by default.,
Run a Light Scan to quickly find client-only mods.,
Run a Deep Scan if you still can’t find the problematic mod.,
Disable, upload, and delete mods directly from the Mod Manager.
