How to Resolve Conflicts
A short guide to fixing each kind of conflict. Most of it happens in the dashboard with one or two clicks.
Open the dashboard with:
/conflictsThen press Scan (or Re-scan) at the top so the results are up to date.
[!NOTE] Every fix is backed up first. If something looks wrong in game, open Backups in the top bar and click Restore.
👕 Clothing Conflicts
You fix these straight from the dashboard. Work through them in this order.
Step 1: Run the 5-step repair strip
After a scan, the dashboard home screen shows a strip of five numbered clothing steps at the top, above the conflict counts. Click each one in order. Every step shows a preview first, and nothing is written until you confirm.
| Step | What it fixes |
|---|---|
| 1 - Declarations | Packs that stream more clothing than they list. Always safe. |
| 2 - Contested copies | Two packs using the same colour/variation of a garment. One moves to the next free variation. (Moves numbers.) |
| 3 - File placement | An item's files are spread across different folders. They are moved back into one folder. |
| 4 - Unreachable clothing | Clothing on disk that nothing lists. It gets numbered so it shows in the store. |
| 5 - Collections | Moves a pack into its own collection. This is the fix when a category is over the slot limit. (Moves numbers.) |
A step that has nothing to fix ticks itself off, and the strip moves on to the next one.
Step 2: Merge shared clothing files
If several packs ship their own copy of the same clothing definition file (.ymt), only one copy loads and the rest of the clothing disappears.
- Further down the dashboard home screen, the clothing file card lists every shared
.ymtclash. Click the flagged file. - Scroll to the bottom of the detail panel and click the green Fix button. It merges the copies. The copy that loads now keeps its numbers, so saved outfits stay valid.
[!WARNING] Don't just delete the losing
.ymtwhile its resource still streams clothing. That can crash the game or make clothing vanish. Merge instead.
Step 3: Resolve the remaining rows
Open the Clothing tab. For each remaining conflict, click the row to open its detail panel:
- Preview the garment's textures and 3D model, or spawn side-by-side clones in game to compare.
- Reindex: keeps both items and moves one to a free slot.
- Keep this: keeps the copy you choose and turns off the others (they are renamed to
.bak).
Step 4: Reindex clothing (bulk)
If many slot clashes are left, click Reindex clothing in the top bar to handle them all together. The first resource on each slot keeps it. The others move to a free slot, with their files renamed and metas updated.
Step 5: Restart
Restart the server and clear your client cache so the changes load.
[!NOTE] Steps that move numbers (contested copies, collections, reindex) change item slots. A player already wearing a moved item may need to pick it again, so it's best to do these on new packs or during maintenance.
More detail: Clothing Conflicts.
🚗 Vehicle Conflicts (Modkits)
Also fixed straight from the dashboard.
- Open the Modkits tab to see the clashing modkit IDs and broken kit references.
- Click Auto-fix modkits in the top bar.
- Confirm. Each conflicting kit gets a free ID, and every
carcols.meta/carvariations.metathat uses it is updated to match. - Restart the affected vehicle resources, or the whole server.
More detail: Vehicle Conflicts.
🚨 Siren Conflicts
Sirens have their own tab.
- Open the Sirens tab. It lists:
- Siren rows: two resources using the same siren ID.
- Siren ref rows: a vehicle pointing to a siren setting that doesn't exist.
- Fix them one at a time from a row, or click Auto-fix sirens in the top bar to fix every safe one together.
- The tool gives the clashing siren a free ID, then updates the
sirenSettingsin the matchingvehicles.meta/carvariations.meta. - Restart the affected vehicle resources.
🗺️ Map Conflicts
Maps have an Auto Resolve Map Conflicts button that handles most of the work.
Step 1: Auto Resolve
- Click Auto Resolve Map Conflicts in the top bar, then Resolve now.
- It runs these fixes in order:
- Hidden maps: sinks leftover occluders that make maps disappear from certain camera angles.
- Collision issues: merges clashing collision files, removes leftover collision from deleted objects, and removes objects that block an area another pack cleared.
- When it finishes you get a report showing what it fixed and what it left for you.
You can close the window while it runs. It keeps going, and the button reopens it.
[!TIP] Auto Resolve only fixes findings it is sure about. Anything uncertain is left in the Hidden maps or Collision issues panel so you can check it in game first.
Step 2: What's left
| Problem | Where to fix it |
|---|---|
| Same prop placed twice, or moved | Props tab: pick the placement to keep. See Prop Placement Conflicts |
| A map disappears or doesn't draw right | Hidden maps button |
| Invisible walls, or you fall through the floor | Collision issues button |
| NPC traffic driving through buildings | Auto-fix road paths, or Fix Road by Coords. See Road & Path Node Conflicts |
| Two packs built over each other in one area | Map editor → Zones. See Zone Ownership |
| Props clipping or flickering in one spot | Map editor (/mapeditor). See Usage & Controls |
After fixing map conflicts, restart the server and clear your client cache.
🔒 Protected (Escrow) Resources
Files inside escrow-protected resources show a 🔒 badge. The tool never changes them. See Protected Resources for how to handle them.
Usage & Controls
Learn how to scan your server, fix overlapping IDs, clean up duplicate assets, and modify clipping objects using the in-game UI and live map editor.
Understanding Conflicts
This document provides a deep dive into the technical details of the resource and map conflicts that occur in FiveM, how they affect your server, and how Conflict Resolver automatically resolves them.