> 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/vehicle-dirt-system/mlo-problems.md). # MLO Problems Because there are many different maps you can install on your server, there is a high chance you may have **conflicts**. This is **not a problem with our map**. It usually happens because of **duplicate files** on your server.

*** ## What is a Conflict? Sometimes addon maps, even if they are in **different locations**, share the **same files**. Unfortunately, FiveM cannot load multiple copies of the same streamed files. The way FiveM decides which file to use is **alphabetical order**: > Last file loaded wins. If FiveM does not load one of our files (because another file with the same name was already loaded), you may see problems such as: * Flickering buildings * Collision issues * Missing or broken map parts *** ## How to Fix This? There is no universal fix, because **every server is using different maps and has different conflicts**.\ But here are two possible solutions you can try: ### Solution 1: Manual Conflict Fix The idea is simple, find the **duplicate files** and manually **merge them**. 1. Use our automatic conflict scanner. It will show you which files are duplicated automatically after your server starts *(see example below)*

This image is only an example, by default 17mov_GarbaceCollector does not conflicts with 17mov_VehicleDirtSystem

2. Once you know the files, follow [the tutorial made by our partners NT**eam**](https://www.youtube.com/watch?v=XR9oRhCXdxU). They explain step by step how to merge two files into one *** ### Solution 2: Use 17 Movement Conflict Tool You can also use our **Conflict Tool**, which automatically finds and helps fix map conflicts on your server. You can check it out [here](https://17movement.net/products/17mov-conflict-tool).