TEST SITE new.cfxadmin.com · database totala13_cfxanew · Square sandbox Go to the live site
MLOs that coexist

Find the conflict
before the world breaks.

Two MLOs claiming the same interior is the single most common way a map goes wrong. CFXMaps scans every map resource you have, shows you exactly where they collide, and merges the survivors into one resource.

$99.99/year if you pay annually (save $19.89) · Cancel any time

CFXMaps — Conflict report/assets/images/screens/apps/maps-conflicts.png
#1 Cause of broken FiveM maps
0 Files deleted — everything is backed up
1 Managed resource instead of dozens
RedM Supported alongside FiveM
The problem

Two MLOs, one interior, no error message.

When two map resources ship the same .ymap, the one that loads last wins. There is no warning — you just get a building with no interior, a door that opens into nothing, or props from two different MLOs occupying the same room.

  • Duplicate .ymap and .ybn files across resources are the single most common cause of a broken map
  • Nothing in the console tells you which two resources are fighting
  • Map resources end up scattered across the server instead of grouped, so load order is accidental
  • Fixing it by hand means deleting files from packs you paid for, with no way back if you're wrong
How it works

Four steps, start to finish.

01

Scan the server

Every resource flagged as a map is found, wherever it lives, and its .ymap and .ybn files indexed — including map resources sitting outside your map folder entirely.

02

See the collisions

Files claimed by more than one resource are grouped together, showing exactly which resources are fighting over which parts of the world.

03

Pick a winner

Choose which resource should own each contested file. Originals are backed up outside the server before anything is moved.

04

Combine and load

The chosen files are merged into one managed map resource with a correct manifest, so load order stops being a coin toss.

Inside the app

Built around the work
you actually do.

Conflict report

Every file claimed by more than one resource, grouped with the resources responsible.

CFXMaps — Conflict report/assets/images/screens/apps/maps-conflicts.png

Interior index

Search every interior on your server and see what provides it.

CFXMaps — Interior index/assets/images/screens/apps/maps-interiors.png

Merge output

Multiple map packs collapsed into one clean, correctly ordered resource.

CFXMaps — Merge output/assets/images/screens/apps/maps-merge.png
Everything included

What you get with
CFXMaps.

Conflict scanner

Indexes every .ymap and .ybn across every map resource on your server and reports the exact files claimed by more than one — which is what actually breaks a map.

Finds stray map resources

Detects resources flagged as maps that are sitting outside your map folder, where they load in an unpredictable order and are easy to forget about.

Automatic organisation

Moves loose map resources into a single grouped folder so load order becomes something you control rather than something that happens.

Managed merge resource

Winning files are combined into one generated resource with its own manifest, replacing an unpredictable pile of overlapping packs.

Originals backed up

Every file it takes over is copied outside the server first. Nothing is destroyed, and a bad decision is reversible.

Rebuild from backups

Restore every original file and start the merge again from scratch — so experimenting with load order carries no risk.

Clean MLO removal

Uninstalling a map pulls its files back out of the merged resource and restores anything it had displaced, instead of leaving a hole in the world.

Change tracking

A manifest records which file came from which resource, so months later you can still answer "why is this here?"

Collision handling

.ybn collision files are tracked alongside .ymap placement, so you don't fix the visuals and leave players walking through walls.

Interior index

A searchable list of every interior on your server and which resource provides it.

Occlusion awareness

Occlusion data is accounted for during merging, so combining maps doesn't wreck rendering performance in dense areas.

RedM support

The same scanning, merging and backup tooling applies to RedM map resources.

Under the hood

What it handles.

File types
.ymap placement, .ybn collision
Detection
Resources flagged as maps, anywhere on the server
Conflicts
Duplicate files grouped across every resource
Backups
Originals stored outside the server folder
Reversibility
Full rebuild from backups at any time
Output
One managed map resource with a generated manifest
Tracking
Manifest records the source of every merged file
Platforms
FiveM and RedM
Who it's for

You'll get the most from this if…

Something broke after an install

A new MLO went in and an old one stopped working. The scan tells you which two files collided in about ten seconds.

Running a lot of MLOs

Thirty map resources with no idea which overlap. Index them, merge them, and know what you actually have.

Cleaning up an inherited server

You took over a server with maps scattered everywhere. Organise them into one place without deleting anything you can't get back.

Pricing

Subscribe to just this,
or to everything.

CFXMaps monthly
$9.99/month
Billed monthly, cancel any time
  • Full access to CFXMaps
  • All updates while subscribed
  • Community support on Discord
  • Install on 2 computers, use on 1 at a time
Subscribe monthly
Full Suite
$49.99/month
Billed monthly, cancel any time
  • CFXMaps and all four other apps
  • Anything added to the suite later
  • Priority support
  • Install on 2 computers, use on 1 at a time
Get everything

CFXMaps questions

Will it delete files from packs I paid for?

No. Every original is copied to a backup outside the server folder before anything is moved, and you can rebuild everything from those backups at any point. Nothing is destroyed.

How does it decide which MLO wins?

It doesn't — you do. It finds and groups the collisions and shows you which resources are involved; choosing the winner is a decision about your server, not one a tool should make for you.

What if I remove an MLO later?

Removing it pulls its files back out of the merged resource and restores anything it had been overriding, so the map it displaced starts working again instead of leaving a gap.

Do I need CodeWalker?

Not for finding or resolving conflicts — that's all handled here. CodeWalker is still the tool for authoring map content; CFXMaps deals with what happens once you have several of them installed together.

The rest of the suite

Works alongside

Get CFXMaps.

$9.99 a month, cancel whenever you like. Installs and updates through the CFXAdmin Hub.