DZR DevelopmentDZR Development
Skip to content

Map conflicts

Why two maps in the same area can break each other, how to find the conflict, and who fixes what.

updated 2026-10-24

# on this page

Maps, MLOs, and shells change the game world by streaming files. Two maps can break each other in two ways, and they need different fixes.

Why maps conflict

Same file name. FiveM keeps one copy of each streamed file name. When two resources stream a file with the same name, the copy registered last wins and the other is ignored. This applies even when the two maps are in different places, because files are matched by name only. Start order in server.cfg usually decides the winner, but it is not guaranteed, and either way only one map works.

Same area, different files. Two maps that edit the same part of the world with differently named files both load. Their props, collision, and occlusion overlap, which shows up as doubled props, invisible walls, or flicker.

Conflicts are most likely when two maps:

  • Replace or edit the same vanilla building or block.
  • Edit the same area: prop removals, occlusion, or collision.
  • Ship files with the same name, even at different locations.
  • Change an interior that an IPL loader, such as bob74_ipl, also loads.
Tip

Restarting one map while the server runs can change which copy players get. Test conflicts after a full server restart.

Common symptoms

What you see Likely cause
The outside flickers or vanishes from inside Overlapping occlusion, or an interior missing its portal or proxy setup
Invisible walls, or falling through the floor Two collision (.ybn) files, or a vanilla or IPL building still loading its collision
Extra, missing, or floating props Two placement (.ymap) files placing or removing props in the same area
Wrong model or texture Same-named .ydr or .ytd files
Flickering surfaces Two maps placing geometry in the same spot
Old interior shows through the new one An IPL or the vanilla building still loading
Doors or interactions fail Interior proxies not loaded, or a door or script conflict

Before you buy

  • Check the map's location against the other maps you run. Maps at the same building or block are the ones that conflict.
  • If you run another map there, ask in our Discord before buying.
  • Read the map's install notes for its game build and any interiors or IPLs to turn off. Missing props can also mean the server runs an older game build; see Common errors.

Find the conflict

Do this on a test server or at a quiet time: it takes maps offline for players.

  1. Stop every map resource except the DZR map, including IPL loaders like bob74_ipl. Leave the DZR map's dependencies running.
  2. Restart the whole server.
  3. Confirm the DZR map works on its own.
  4. Start your other maps again one at a time, restarting the server after each.
  5. The map that brings the problem back is the conflict.

Tools that speed this up:

  • CodeWalker shows which .ymap places an entity when you select it in the world view.
  • FiveM's developer console commands strlist true, strdbg true, and strmem true show what the game is streaming; use false to close them. They need developer mode. See console commands.

Back up both resources before editing either one.

Note

Clearing the server cache folder is old advice. Current FiveM rebuilds it from your resources on its own, and it does not fix map conflicts.

Fixing a conflict

Conflict Usual fix
Same-named files Keep one copy, or rename one and update every file that references it
Two maps in the same area Run one of them, or move or remove the overlapping props, occlusion, or collision in one map
An IPL loader changes the same interior Turn off only the interiors that clash, such as their lines in bob74_ipl's client.lua, instead of removing the loader (example)

Before deleting a duplicate file, check whether it is meant to replace a vanilla file. After editing a .ymap in CodeWalker, run Calculate Extents and Calculate All Flags before saving.

Protected files in escrowed maps, including paid DZR maps, cannot be edited or merged; only files the creator leaves editable can be changed. Their conflicts are usually fixed in the other map, with a compatibility patch, or by running one of the two.

Who fixes what

Situation Who handles it
The DZR map is broken with no other maps running Us - open a Bug Report ticket
Two DZR maps conflict Us - report it as a bug
A DZR map conflicts with another creator's map You, or that creator. We will try to provide a compatibility patch, but we cannot guarantee one.
You edited either map's files You. We may ask for a clean install first.
Note

We cannot edit or redistribute another creator's files. A compatibility patch from us only changes DZR files, so some conflicts can only be fixed by the other creator or by choosing one map.

Ask for a compatibility patch

Open a Bug Report ticket in Discord with:

  • The DZR map name and the other map's name and creator.
  • The location, with coordinates if you have them.
  • What you see, with a screenshot or clip.
  • Confirmation that each map works when run on its own.

Sources

< prevFAQnext >Common errors