Overview
After battling with mods overwriting other mods & conflicting with each other, I took an old (but promising) mod tool and expanded upon it.Features:Checks for the same nameDef defined in 2 or more modsLists all core (game default) nameDef’s overwritten by modsFinds any DLL existing in 2 or more modsIdentifies possibly corrupt or incomplete mods (partially implemented)Checks versions of all mods against the RimWorld versionLists mods load order also showing disabled modshttps://ludeon.com/forums/index.php?topic=25305.msg258525#msg258525Download link: https://github.com/biship/RimworldConflictChecker/releases(Windows only sorry!)
Download
[link]Features
- Checks for the same nameDef defined in 2 or more mods
- Lists all core (game default) nameDef’s overwritten by mods
- Finds any DLL existing in 2 or more mods
- Identifies possibly corrupt or incomplete mods (partially implemented)
- Checks versions of all mods against the RimWorld version
- Lists mods load order also showing disabled mods
Instructions
When RCC.exe is run it will open the UI for you to pick at least 2 paths (RimWorldWin.exe & Mod folder path).
The first 2 folders are required (Mod folder 1 is auto-calculated when you choose the RimWorldWin.exe folder – but it can be changed).
Mod Folder 2 is only needed for Steam users.
It can also be run from the command line with parameters:
Results
Open RCC.txt from the same folder as RCC.exe and look for issues.
Bugs
NB: Uses opensource library NBug to submit crashes to a Mantis tracker so I can fix any issues.
Feel free to block it if you do not want the reports sent.
Please report bugs in this guide, or on GitHub.