This is how modLang checks compatibility
The compatibility section on a mod detail page gathers the six sources of evidence below. Each source has limits, so please treat this as a reference rather than a definitive verdict.
Declarations the mod makes itself
We carry over the required mods, incompatible mods, and supported version declarations that the mod writes directly in About.xml. Because these are values written by the creator, they may be wrong or missing.
RimSort community rules
This is a compatibility rule database collected by people. It reflects real usage experience, but it does not cover every mod.
Use This Instead list
This is a list of mods that are no longer updated and the mods to use instead. It also mixes in recommendations for other mods with the same function, so it is hard to view as a confirmed lineage.
Static analysis
modLang automatically analyzes the mod's XML and code to see whether it overwrites the same definitions or references classes that do not exist. Because it is automated analysis, there are many false positives.
Server load test
On a server in a virtual display environment, we actually put the mod in, start the game, and check whether loading stops. Limits: it is an environment without a display, it checks only up to loading, and errors during play cannot be known.
User reports
We collect anonymous reports that users send after giving separate consent in modLang's error log analysis (or through the companion mod). We show the label "n user reports (last 90 days)" on the mod detail page only when the same error message points to the same mod as a candidate cause in 3 or more separate reports. Limits: the candidate cause from log analysis is an estimate and may not be the actual cause, and the same person can send multiple reports (limit 10 per day). It is a reference, not a definitive verdict.
Update frequency
Updated daily at 05:30. For 1.7, checks will begin after the official release.