What problem does it solve?
Bethesda modpack creators often struggle with conflicting plugin records that cause broken or missing in-game behavior, with no clear way to identify which overrides win, what references the conflicting record, or if their load order is safe to ship.
Core Features & Use Cases
- Structured Conflict Verdicts: Produces clear, standardized labels (no_conflict, itpo, itm, minor, breaking) for any audited record or plugin, plus the winning override chain and list of referencing plugins.
- Remediation Guidance: Includes a decision matrix to choose between accepting normal overlap, reordering load order, creating a patch, cleaning unused ITMs, or removing problematic mods.
- Broad Audit Support: Leverages r6 xEdit shortcuts like recursive reference lookups and child-group conflict summaries to efficiently audit large mod lists without manual per-record looping.
- Use Case: Troubleshoot why a mod's NPC changes are not appearing in-game, validate a modpack's load order before public release, or audit all records for a specific weapon to identify overlapping edits.
Quick Start
Use the xedit-conflict-audit skill to run a full conflict audit of your active Bethesda mod load order and get a prioritized list of breaking and minor issues that need resolution.