-
Notifications
You must be signed in to change notification settings - Fork 46
Conflict Solver Modes
The Conflict Solver offers multiple modes that determine how Irony detects, displays, and processes mod conflicts.
Each mode changes how strictly conflicts are interpreted and whether Irony is allowed to generate patch output.
Modes fall into three families:
- Default
- Advanced
- Analyze Only
Each mode also has a No Localization variant.
When starting the Conflict Solver, Irony presents a mode selection dialog.
This determines:
- How conflicts are interpreted
- Whether dependency information is respected
- Whether patch output is generated
- Whether localization files are included
- How much detail is shown
Irony will prompt for mode selection every time you run the solver unless conflict history and state allow an automatic continuation.
The dialog provides:
- A mode selector (Default / Advanced / Analyze Only)
- A toggle to exclude localisation folders (“Without Localization”)
- A short description of each mode
After choosing a mode, Irony loads and analyzes all affected definitions.
Default Mode is designed for normal use and hides noise from expected overriding behavior.
- Respects
.moddescriptor dependencies - If Mod A supersedes Mod B via dependencies, Irony suppresses conflicts coming from B
- Shows only meaningful conflicts
- Reduces noise for typical playset management
- Produces patch output when conflicts are resolved
Recommended for all non-modders and for regular modlist maintenance.
Same behavior as Default Mode, but excludes localization files entirely.
- Skips all
localisation/folders - Useful when localization overrides are irrelevant or intentionally noisy
Advanced Mode bypasses dependency pruning entirely.
- Ignores dependencies
- Shows all conflicts, including:
- Overrides normally hidden due to “A replaces B” relationships
- Hidden conflicts masked by load order
- Provides maximum detail
- Generates patch output when conflicts are resolved
- Useful for mod developers
Full visibility for debugging, creating compatibility patches, or validating large overhauls.
Same as Advanced Mode, but excludes all localization files.
- Full conflict detail
- No localisation noise
- Faster analysis in localization-heavy modlists
Analyze Only Mode loads conflicts but never produces patch output.
- Fully read-only
- All conflict information is visible
- Same UI as full modes (except editing is disabled)
- Useful for debugging or checking overrides without altering anything
- Debugging large modsets
- Verifying mod interactions without creating a patch mod
- Cross-checking mod compatibility before making changes
Same as Analyze Only, but excludes localization folders.
- Read-only
- No localisation noise
- Faster analysis for content-focused debugging
Irony tracks the internal state of each conflict.
Even after selecting a mode, Irony will ask again under these conditions:
- Conflict state changed
- New conflicts were introduced
- Automatic reset happened
- The collection changed (mod added/removed)
- A mod updated a file (hash mismatch)
Irony does not automatically invalidate or delete patch output.
Instead:
- An updated mod or a collection change triggers a state mismatch
- The affected definition receives a yellow or red border depending on previous state
- Irony displays a notification such as “Please rerun Conflict Solver”
Patch output remains intact until the user resolves again or manually resets.
More info:
→ Reset Conflicts
Irony automatically scans mod structure in the background:
- File hashes
- Folder structure
- Definition hashes
- Contributor presence
If anything changes, Irony flags conflicts that may need attention.
Patch files are not removed automatically unless the conflict becomes irrelevant (no contributors), in which case Irony cleans old output silently.
- Normal gameplay
- Regular modlists
- Minimal noise
- Fastest workflow
- Debugging tricky mods
- Creating compatibility patches
- Investigating override chains
- Verifying mod interactions
- Multiplayer consistency checks
- Validating modset without touching patch output
- When localization overrides generate unnecessary noise
- When working only with gameplay files
Conflict Solver Modes define how Irony interprets and displays conflicts:
- Default respects dependencies
- Advanced shows everything
- Analyze Only is read-only
- “No Localization” variants exclude localization folders
- Irony warns about changes with visual indicators and prompts, but never removes patch data unless it becomes irrelevant
Choosing the right mode ensures the best balance between precision, clarity, and performance.