Docs
Understanding map conflicts
A conflict happens when two map mods change the same file. On a FiveM / GTA V server only one resource's copy of that file can load, so the other map's work is silently overridden. Here are the conflict types Luman Hub detects and merges.
Prop placement conflict (.ymap)
Two maps both edit the same .ymap, so one resource's props, removed objects or entity edits replace the other's. Merging keeps both sets of changes against the vanilla base.
Collision conflict (.ybn)
Duplicate .ybn collision files mean only one wins — you fall through the map or hit invisible walls. Merging unions the collision changes so every map stays walkable.
Model conflict (.ydr / .ydd)
When two resources ship the same drawable, one model overrides the other. A 3-way merge by geometry keeps each map's intended models.
Occlusion conflict (map flickering)
Conflicting occlusion data makes parts of the map flicker or z-fight as the engine can't decide what's visible. See the dedicated guide on fixing it.
Instead of picking a winner, Luman Hub performs a 3-way merge against the original base files, so each map keeps its changes in one combined resource. Start with getting started.