How to Fix a "Missing CoroUtil" Crash or Dependency Error

The most common problem players hit with CoroUtil is a crash or error screen saying a mod requires CoroUtil and it could not be found. This almost always comes down to one of a few mismatches. Work through them in order.

Step 1: Confirm the File Is in the Right Place

Make sure the CoroUtil file is in the same mods folder as the mod that needs it. If you use a launcher with per-profile folders, confirm you are editing the profile you are actually launching. A file dropped into the wrong profile's folder will not be seen.

Step 2: Match the Loader

CoroUtil builds exist for different mod loaders. If your dependent mod is a Forge mod but you downloaded a Fabric build of CoroUtil (or vice versa), the game will not load it. Delete the wrong file and use the build for the same loader as your other mods.

Step 3: Match the Minecraft Version

A CoroUtil build for one Minecraft version will not satisfy a dependent mod built for another. Check the dependent mod's supported Minecraft version and use the CoroUtil build for that same version.

Step 4: Check for Duplicates

Having two different CoroUtil files in the mods folder at once can cause conflicts. Remove all but the single correct one.

Step 5: Read the Crash Report

The crash report names the exact mod and the exact reason. If it says "missing dependency," it is a file problem. If it says a class failed to load, it is a version or loader mismatch. Fix according to the message rather than guessing.