RimWorld mods not working: outdated mods, requirements and load order
Updated 17 November 2026
1. Outdated mods
Each mod lists the RimWorld versions it supports. In the mod list, mods not marked for your version show a warning. After a big update, gameplay mods that aren't updated can cause red errors or even break saves. Small cosmetic mods often still work. Check each mod's Workshop page for an update.
2. Missing requirements
Many mods need another mod to work. Common ones are Harmony, HugsLib and Vanilla Expanded Framework. Some also need an expansion (Royalty, Ideology, Biotech, Anomaly, Odyssey). The mod's page lists what it needs; subscribe to it and switch it on.
3. Load order
- Harmony goes at the very top.
- Then Core, then the expansions.
- Then libraries and frameworks (HugsLib and similar).
- Then everything else. A mod that depends on another must load after it.
The in-game mod manager can sort for you, and the free RimSort tool does it with more detail. Both read each mod's "load after/before" rules.
Finding the mod behind red errors
Open Player.log (on Windows: Win + R, type %USERPROFILE%\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios). Errors often start with the mod's name in square brackets, or mention a file inside a mod's folder.
Questions
Can I add or remove mods mid-save?
Adding most mods is fine. Removing mods that add items, creatures or buildings can cause errors in that save. Back up your save first.
Why does the same mod show twice?
You probably have it both in your local Mods folder and from the Steam Workshop. Keep one.
Can a tool check all this for me?
Yes. The free FixMyMods RimWorld checker reads every mod's About.xml, lists outdated mods and missing requirements, checks load order from your ModsConfig.xml, and matches Player.log errors to mods.