Conflicted Objects - bcssov/IronyModManager GitHub Wiki

The Conflicted Objects view shows all detected conflicts for the currently selected collection.
It presents a structured, game-logic hierarchy where you can inspect definitions, understand which mods touch the same objects, and open them in the Merge Viewer for resolution β†’ Merge Viewer.

1. Overview

Conflicted Objects are displayed in two parts:

  • A dropdown showing the full conflict hierarchy (folders β†’ files β†’ definitions)
  • A listbox showing the definitions inside the selected file or node

Selecting a definition opens the Merge Viewer, where differences between mods can be examined and resolved (if the game supports full merging).
β†’ Merge Viewer

This view is the starting point for analyzing and fixing mod conflicts.

2. Navigating Conflicts

Conflict Hierarchy Dropdown

The dropdown displays all conflicted files and logic nodes Irony has detected.
Each entry expands the game’s internal structure, allowing you to drill down to the exact definition that has conflicting contributors.

Example:

  • common
  • common/ship_behaviors
  • common/ship_behaviors/behavior_type_1.txt

Simply select a node to load its definitions in the listbox.

1

Definitions Listbox

After selecting a node, the listbox shows all definitions inside that file that have conflicts.

Selecting a definition loads it into the Merge Viewer β†’ Merge Viewer

2

3

3. Reset Indicators

Irony automatically resets conflicts when it detects that mod files have changed
(for example, a mod author updated a file after you previously resolved or ignored a conflict).

Reset indicators help highlight these cases:

  • Red border β†’ previously resolved conflict has changed
  • Yellow border β†’ previously ignored conflict has changed

These indicators appear directly in the definitions listbox.

You can filter to only show reset conflicts by enabling:
Conflict Filter β†’ Show Only Reset Conflicts β†’ Conflict Filter

4. Invalid Objects

Occasionally, Irony can detect invalid definitions.
This analysis is powered by CWTools.

Invalid items appear in a separate dropdown section labeled Invalid.

Selecting an invalid entry shows a detailed parsing error on the right-hand panel.

4

Invalid definitions often indicate:

  • Mistyped syntax
  • Broken scopes
  • Missing brackets
  • Misplaced keywords

These issues may prevent a mod from working correctly in-game.

5. Developer Overrides

Mod developers can instruct Irony how to treat certain files or definitions.

Irony supports three special comment directives:

1. Fallback to Simple Parser

### Dear Irony please fallback to simple parser

Forces Irony to bypass CWTools parsing for this file and use a less strict parser.

2. Ignore Entire File (placeholder)

### Irony this is a placeholder file please ignore it

Irony will ignore duplicate detection inside this file.

3. Ignore Specific Definitions (placeholder objects)

### Irony these are placeholder objects please ignore them: id1,id2

Only the listed definition IDs will be ignored.

Important Note

If Irony detects that your placeholder object would win a conflict in a FIOS/LIOS scenario,
it may override your ignore directive to avoid giving placeholders unintended priority.

This is intentional to prevent mod load order issues.

6. Tips for Modders

  • Use placeholder ignore comments for prototype or empty files
  • Use fallback parser for files with non-standard syntax
  • Validate definitions inside CWTools errors to ensure compatibility
  • Use the Conflict Filter to focus on important conflicts β†’ Conflict Filter
  • If you ran the Conflict Solver once and changed your collection, run it again to refresh patch mods β†’ Conflict Solver Modes

Summary

The Conflicted Objects view provides:

  • A hierarchical overview of all detected conflicts
  • Direct access to definitions that require attention
  • Visual reset indicators for changed items
  • Tools to inspect invalid definitions
  • Developer-side control via Irony directives

This section is the core of conflict analysis in Irony and the main entry point to the Merge Viewer and further conflict resolution tools.