xedit-conflict-audit

Audit Bethesda mod load orders for conflicting override records and remediation actions.

11|3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill xedit-conflict-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xedit-conflict-audit
Source: https://github.com/BB-84C/bgs-modding-superpowers/tree/main/plugins/bgs-modding-superpowers/skills/xedit-conflict-audit
Command: npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill xedit-conflict-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about xedit-conflict-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify conflicting override records in a Bethesda mod load order?

To identify conflicting override records in a Bethesda mod load order, audit your plugins to determine which overrides win and what references the conflicting record. This process produces structured conflict verdicts and winning override chains.

Why does a mod's NPC or weapon changes not appear in-game?

Missing NPC or weapon changes in-game are typically caused by conflicting plugin records where another mod's override wins the load order. Auditing overlapping edits helps identify if the conflict causes broken or missing behavior.

How do I validate load order safety before shipping a modpack?

Validating load order safety before shipping a modpack requires running a full conflict audit to generate a prioritized list of breaking and minor issues. This verifies overlapping edits to NPCs, weapons, and keywords are resolved.

What is the best way to resolve mod conflicts found during a load order audit?

The best way to resolve mod conflicts found during a load order audit is to follow remediation guidance that recommends patching, reordering the load order, accepting normal overlap, cleaning unused ITMs, or removing problematic mods.

Can I audit all records for a specific weapon across a large Bethesda mod list?

Yes, you can audit all records for a specific weapon across a large Bethesda mod list by leveraging recursive reference lookups and child-group conflict summaries to efficiently audit overlapping edits without manual per-record looping.

What do ITM and ITPO conflict labels mean when checking mod overrides?

ITM and ITPO are standardized verdict labels used when checking mod overrides to classify record conflicts. ITM identifies identical to master records for cleaning, while ITPO indicates identical to previous override conflicts in the load order.