> 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/asset-override-conflicts.md).

# 📁 Asset Override Conflicts

An asset override conflict happens when multiple resources stream a file with the same name but the actual file contents are different.

Examples can include:

* `.ytd`
* `.ydr`
* `.ydd`
* `.yft`
* `.ytyp`
* `.ybn`
* LOD-light `.ymap` containers

### When is it a conflict?

Conflict Tool compares file sizes and hashes.

If multiple resources ship byte-identical copies, the tool does not report a conflict.

If the files differ, only one version can win FiveM's streaming race, so the final result may depend on load order.

### Pick a winner

You can choose one resource as the winner.

Conflict Tool copies that resource's version over the other conflicting copies so every shipper contains consistent bytes.

### Merge

Merge is offered only when the scan proves the edits are compatible.

Typed merge support exists for:

* `.ydr` - drawable geometry, including terrain edits,
* `.ybn` - collision triangles and BVH,
* `.ydd` - LOD dictionaries,
* `.ytyp` - archetype definitions,
* LOD-light `.ymap` containers.

The merged asset is built at apply time using the vanilla version as its base, then written to each resource involved in the conflict.

If a merge fails during apply, Conflict Tool falls back to copying the selected winner instead of failing the entire apply operation.

### Ignore

**Ignore** explicitly leaves the conflicting files unchanged.

It counts as a resolved decision inside Conflict Tool, but FiveM's load order will continue deciding which file wins.

### No access

If Conflict Tool cannot read one of the files, the conflict is marked **no access**.

Typical causes are:

* escrow encryption
* locked or otherwise unreadable files.

Unreadable files cannot be merged. The panel identifies which copy cannot be accessed so you can decide how to handle the conflict.

### Needs review

If multiple resources edit the same part of an asset in incompatible ways, a clean merge cannot be proven safe.

Those conflicts require an administrator to pick the intended result.