Curios Mod Performance and Compatibility Checklist

Curios is not a performance mod, but clean dependency management can improve the stability of a Curios-based modpack and reduce time lost to repeated crashes or conflict testing.

Keep one intentional version

Avoid leaving old Curios JARs in the mods folder after updates. A single deliberate dependency version is easier to reason about and troubleshoot.

Related: Browse all Curios mod guides or check the homepage compatibility overview.

Update connected mods together

When a content mod moves to a newer Curios API range, update the connected dependency set as a group. Random partial updates can create version drift.

Use logs before changing settings

Startup logs and loader errors are more useful than generic performance tweaks when the problem is an API mismatch. Fix structural errors first.

Test after small changes

Add or update a few mods at a time and launch between changes. That makes it easier to identify the exact modification that introduced a conflict.

Quick checklist

• Write down the exact Minecraft version.
• Confirm the loader family before choosing a file.
• Check which installed mod requires Curios.
• Back up worlds and configs before dependency changes.
• Read loader errors before trying another version.