> For the complete documentation index, see [llms.txt](https://docs.17movement.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.17movement.net/conflict-tool/understanding-conflicts.md).

# ⚠️ Understanding Conflicts

Conflict Tool does **not** treat every duplicate file or every map edit as a conflict.

A conflict is reported only when the tool has enough information to prove that multiple resources disagree about the same part of the world.

### General rule

Something is considered a conflict when:

1. **Two or more resources** ship versions of the same thing,
2. those versions are **different**, and the vanilla GTA V baseline proves that at least one resource actually changed it.

### What is not a conflict?

#### Only one resource changes something

If only one resource ships an edited version, there is nothing to harmonize with another resource. That resource simply wins.

#### Multiple resources ship identical copies

If two or more resources contain the same bytes or agree on the same state, Conflict Tool does not report a conflict.

#### A custom asset has no vanilla original

Custom assets without a vanilla counterpart are intentionally skipped when the tool cannot establish a reliable baseline.

Without the original file, Conflict Tool cannot reliably tell whether a difference is an intentional custom edit or a conflicting modification. Automatically "fixing" that would be guesswork.

### Conflict categories

Conflict Tool groups detected issues into four main categories:

* [📦 Prop Conflicts](https://docs.17movement.net/conflict-tool/understanding-conflicts/prop-conflicts)
* [🧱 Collision Conflicts](https://docs.17movement.net/conflict-tool/understanding-conflicts/collision-conflicts)
* [👁️ Occlusion Conflicts](https://docs.17movement.net/conflict-tool/understanding-conflicts/occlusion-conflicts)
* [📁 Asset Override Conflicts](https://docs.17movement.net/conflict-tool/understanding-conflicts/asset-override-conflicts)

### Why some conflicts say "Needs review"

Auto-resolve only acts where the correct outcome can be proven with high confidence, such as:

* an unambiguous deletion,
* multiple resources agreeing on the same moved position,
* compatible non-overlapping edits,
* identical copies.

If two resources contain genuinely different authored edits, Conflict Tool cannot know which creator's intent is correct.

For example, two road models placed only a few centimeters apart may look like z-fighting, but they may also be intentionally layered geometry. Automatically deleting one could damage a map.

Those cases are marked **needs review** and skipped by Auto-resolve unless you explicitly choose to include them.