CoroUtil Mod FAQ

CoroUtil is a separate library that must be present alongside any Corosus mod that depends on it. Most launchers and mod loaders will not bundle it automatically, so you install it as its own file in your mods folder.

Any mod made by Corosus that lists CoroUtil as a dependency needs it. If you remove CoroUtil and a mod crashes on startup complaining about a missing dependency, that mod was relying on it.

CoroUtil is a shared code library, so it only does something when another mod calls into it. On its own it adds no gameplay, and it won't conflict with unrelated mods just by being installed.

No. It is a library of shared code, not a content mod, so it adds nothing you can craft, place, or interact with directly. Everything you see in-game comes from the Corosus mods that use it.

Yes, it just sits there unused. It won't change your world or your gameplay unless another mod is actively calling its code.

CoroUtil bundles several internal components (coroai, buildmod, configmod, and extendedrenderer) that each register separately. Seeing them listed individually is normal and not a sign of a duplicate install.

You either don't have CoroUtil installed or you have the wrong version for your game version. Match CoroUtil to the same Minecraft version as the Corosus mod that's asking for it, then relaunch.

Only if none of your remaining mods depend on it. If any Corosus mod is still installed, removing CoroUtil will cause that mod to fail to load, so remove the dependent mods first or keep CoroUtil in place.

CoroUtil itself is lightweight, but the mods that use it (especially ones with lots of AI or rendering work) can be heavy. If you see performance drops, check the Corosus mods you're running rather than CoroUtil alone.

Update CoroUtil and all Corosus mods that depend on it together, using versions built for the same Minecraft release. Mixing an old CoroUtil with a newer dependent mod (or vice versa) is the most common cause of post-update crashes.

CoroUtil is a shared library, not a standalone content mod, so it adds no items, blocks, or mobs on its own. Its job is to provide the common code that Corosus mods rely on, so you install it once and every Corosus mod that needs it can run.

Yes, if that mod lists CoroUtil as a dependency. Many Corosus mods will crash or fail to load without it, so keep it installed alongside whatever Corosus mod you're using.

You generally won't see it in-game because it has no visible content of its own. The clearest sign it's working is that the Corosus mods depending on it load without a missing dependency error.

You can, but there's usually no reason to. It exists to support other mods, so on its own it won't change your game in any noticeable way.

As a library, it's generally safe to run alongside unrelated mods since it doesn't add world content. Conflicts are rare and usually come from the Corosus mods using it rather than CoroUtil itself.

CoroUtil itself is lightweight and mostly idle when its dependent mods aren't doing heavy work. If you notice lag, it's more likely coming from the Corosus mod using CoroUtil than from the library alone.

Yes, in most cases both sides need it installed for Corosus mods to work correctly in multiplayer. Installing it only on the client or only on the server often causes connection or loading errors.

Yes, once no installed mod depends on it, you can safely remove it. Remove the dependent mods first, then CoroUtil, to avoid a missing dependency crash on startup.

This usually means a version mismatch between CoroUtil and the Corosus mod expecting it, or that it's only installed on one side in multiplayer. Make sure the CoroUtil build matches what your dependent mod requires and that both client and server have it.