Understanding Conflicts
What causes mod conflicts and which files Vertex Hub can merge
Why Conflicts Happen
GTA5 mods use various file types to define the game world. When two mods modify the same area or use overlapping assets, they create duplicate files with the same name but different content.
The game's streaming system loads resources in alphabetical order by resource name. When duplicates exist, only one version loads — breaking the other mod.
How Vertex Hub Fixes This
Vertex Hub creates a merged compatibility resource with special scripts that force the merged versions to dominate over original files.
Start vertex-hub LAST
You must ensure vertex-hub starts last in your server.cfg. This allows our scripts to override conflicting files from other resources.
File Types
Map Files
Placement of MLOs, props, grass batches, occlusion, lodlights, cargenerators.
Conflict symptoms: Missing props, buildings popping in/out, broken occlusion, LOD issues
Type Definitions
Prop definitions — archetypes that define what objects look like.
Usually do not need to merge. Only merge if you're certain it's causing issues.
Collisions
External collision boundaries — what you can and can't walk through.
Conflict symptoms: Walking through walls, invisible barriers, can't enter buildings
Models
3D drawable models — props, ground, buildings, and other geometry.
Conflict symptoms: Missing or corrupted props, wrong textures, model glitches
What Vertex Hub Merges
Vertex Hub intelligently combines:
- Map files (
.ymap) — Handles entity placement, occlusion data, LOD definitions - Type files (
.ytyp) — Merges archetype definitions - Collision files (
.ybn) — Combines collision meshes - Model files (
.ydr) — Merges 3D drawable models
When NOT to Merge
Not every duplicate needs merging
Vertex Hub automatically identifies all conflicts, but you decide what to merge. Only merge when you see actual in-game problems.
Don't merge if:
- Both mods work fine despite showing duplicates
- The mods are in completely different map areas
- You're not experiencing visual or collision issues
Merging unnecessarily can introduce new conflicts.
Identifying Problem Resources
Vertex Hub automatically scans and shows you all conflicting files. Use these symptoms to decide which ones need merging:
Walk through solid objects
.ybn collision conflict
Objects disappear when approaching
.ymap occlusion data conflict
Props missing or wrong model
.ymap, .ytyp, or .ydr conflict
Z-fighting / flickering textures
Overlapping .ymap entities
When you notice an issue in-game, note which map area it's in. Search for that resource name in the conflict list to find what it's conflicting with.