> For the complete documentation index, see [llms.txt](https://brunx-mods.gitbook.io/brunx-mods-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brunx-mods.gitbook.io/brunx-mods-docs/help-support/resolving-map-conflicts.md).

# Resolving Map Conflicts

Understand what FiveM map conflicts are, how to identify them, and how to fix them.

FiveM map conflicts happen when two resources try to use the same space, props, or game structures. This can cause broken textures, duplicated objects, bad collision, invisible parts, or overlapping maps. This page explains how to identify these conflicts, how to fix them, and which tools help.

### ❓ Do we guarantee compatibility with other maps?

⚠️ **No.**

We may help with some compatibility fixes when possible, but we do **not** guarantee 100% compatibility with third-party maps.

⚠️ Only **official compatibility patches** released by our store are supported.

⚠️ For all other cases, conflicts may need to be fixed manually or with tools such as **OpenIV**, **CodeWalker**, and **CompChecker**.

👉 If you use multiple maps in the same area, always test them together before using them on your main server.

### ❓ What is a map conflict?

A conflict happens when two maps or resources modify the same GTA V area.

The most common cases are:

* two `ymap` files in the same area
* duplicated props or objects
* broken collision or collision passing through walls
* IPLs or interiors loading at the same time
* one map removing parts of another

### ❓ How to tell when there is a conflict

Conflicts usually appear as visual or physical issues in-game.

The most common signs are:

* floating or duplicated objects
* invisible ground, walls, or ceilings
* one map clipping through another
* bad collision on doors, streets, or interiors
* FPS drops in one specific area

{% hint style="warning" %}
Not every visual issue is a conflict. Sometimes the problem is a corrupted file, an incomplete install, or a missing dependency.
{% endhint %}

### ❓ How to identify the resource causing the problem

Start by isolating the area and reducing the number of active resources.

{% stepper %}
{% step %}

### ❓ Test the area with fewer resources

Disable recently added maps.

Restart the server and test the affected area.
{% endstep %}

{% step %}

### ❓ Find which resource conflicts

Enable one map at a time.

When the issue returns, you have found the conflicting resource.
{% endstep %}

{% step %}

### ❓ Compare the files

Open the resources in CodeWalker or OpenIV.

Check `ymap` files, props, collision, and IPLs that use the same area.
{% endstep %}
{% endstepper %}

### ❓ How to fix map conflicts

There is no single fix for every case. The solution depends on the type of overlap.

The most common fixes are:

1. remove the `ymap` that duplicates the area
2. edit the map and remove conflicting props
3. disable IPLs that break the interior or structure
4. replace an old map version with a compatible one
5. adjust the installation so only required files load

If two maps use exactly the same location, the cleanest fix is to keep only one. If the conflict is small, removing duplicated objects from the resource you want to keep is usually enough.

### ❓ Tools that help fix conflicts

#### OpenIV

Use [OpenIV](https://openiv.com/) to open and review GTA V and map files.

It helps you:

* view file structure
* review map and asset content
* confirm that the correct file is being used

#### CodeWalker

Use [CodeWalker](https://discord.gg/Dct5nTMFaj) to inspect maps in more detail.

It helps you:

* open and inspect `ymap` files
* view objects in the world
* locate overlapping props, collision, and map areas

#### CompChecker from our store

**CompChecker** helps speed up map compatibility checks.

Use it to:

* check for possible conflicts before final installation
* compare resources faster
* reduce manual time spent searching for overlaps

If you install many maps on the same server, CompChecker helps you catch issues earlier and makes the process easier to manage.

### ❓ Is there a tutorial video that can help?

🎬 Yes. The nTeam released a video tutorial that has already helped thousands of people fix MLO conflicts. There is also another explanatory video from a different creator.

Recommended videos:

* [▶️ Watch on YouTube — How to Fix MLO Conflicts (nTeam)](https://youtu.be/XR9oRhCXdxU)
* [▶️ Watch on YouTube — FIX MLO CONFLICTS & PROP FLICKERING in FiveM!](https://www.youtube.com/watch?v=jlcLksfQU6c)

### ❓ Best practices to avoid conflicts

Before adding any new map:

* back up the current resource
* test the map in a clean environment
* avoid installing multiple maps for the same area
* keep resource names and versions organized
* validate compatibility before going live

### ❓ Summary

FiveM map conflicts are common when multiple resources change the same area. The best way to fix them is to identify the exact resource causing the issue, compare the files, and remove only what conflicts. Tools like **OpenIV**, **CodeWalker**, and **CompChecker** make this process much easier.