Compatibility Data & Rules Evidence Center

Rules & Evidence

See how rule severity, independent confidence, evidence types, and limitations shape a conclusion.

Active rulesetrules-2026.07.12

Published rules4 sample rules

Evidence types5 traceable categories

Interpretation model

Read severity and confidence separately

How harmful the issue could be if the signal is correct. It does not say how certain the rule is.

How strongly the available evidence supports this specific conclusion. It does not reduce the possible impact.

Where each signal came from, so you can decide whether it applies to your setup.

ManifestDependency graphEnvironment matchChangelogAuthor note

Decision rules

rules-2026.07.12

Signal: A required package identifier appears in the dependency graph but not in the normalized setup.
Conclusion: Action required: install or restore the prerequisite before loading the dependent mod.
Known limitations: Renamed, bundled, or manually patched dependencies may not be recognized by identifier alone.

Evidence typesManifestDependency graphEnvironment match

Version rules-2026.07.12Changed Jul 12, 2026

Change history

Jul 12, 2026rules-2026.07.12Separated severity from confidence, added environment-match provenance, and clarified that missing verification is not known incompatibility.
Jul 5, 2026rules-2026.07.05Added dedicated-server scope and dependency-graph evidence categories.
Jun 28, 2026rules-2026.06.28Established the first traceable sample record set for version-aware compatibility review.

TamerTools is restoring the page and its local session state.