You installed a polished FiveM MLO, ensured the resource, and walked to the front door—only to find two lobbies, floating drywall, or a booking desk buried in Mission Row concrete. That is not a “broken map” in most cases. It is a replacement conflict: the new interior is loading *and* the vanilla shell (or another pack on the same footprint) is still there.
This operator guide explains FiveM MLO conflicts at a practical level—IPL leftovers, remove YMAPs, dual-MRPD mistakes, and a staging test order that keeps production safe. Pair it with our step-by-step How to Install a FiveM MLO guide so install hygiene and conflict hygiene stay in the same workflow.
Symptoms gallery (clipping walls, two lobbies, doors into concrete)
Use this as a quick field guide before you rewrite `server.cfg` at random.
| What you see in-game | What it usually means |
|---|---|
| Two lobbies, two reception desks, or “ghost” walls through the new shell | Vanilla interior (or a second MLO) still streaming in the same footprint |
| Doors that open into solid concrete / void | Portal or entrance still tied to the old shell; removal incomplete or wrong pack |
| Exterior looks new, interior is still Rockstar’s layout | Resource started, but IPL / remove steps for the interior were skipped |
| Exterior still vanilla, interior is the paid MLO (or the reverse) | Partial remove: exterior YMAPs and interior IPLs are not both handled |
| Players fall through floors only in one wing | Collision (ybn) issue *or* mixed old/new geometry—stage alone to separate causes |
| Fine alone, broken after you added a second PD/hospital | Load-order / dual-replacement conflict (two packs claiming one vanilla slot) |
| Script markers in the wrong room | Jobs still point at old coords—map may be fine; frameworks need a config pass |
If screenshots from the seller look clean and your city looks like a collage, assume double interiors until a staging test proves otherwise.
Replacement vs add-on interiors — decision tree
Not every MLO fights vanilla GTA the same way.
Add-on / greenfield New usable space where there was no competing shell (or it sits cleanly beside one). Conflicts are rarer: wrong nesting, missing `ensure`, or a neighbor map that edits the same block. Focus on collisions and script coords.
Replacement Rebuilds a known vanilla footprint—Mission Row PD, Pillbox-class hospitals, Benny’s-style shops, major banks, and similar landmarks. These almost always need an explicit story for what stops loading. If the listing never mentions IPL removals, remove YMAPs, or “disable the default interior,” budget staging time.
Decision tree (operators):
- Does this pack sit on a famous vanilla building players already know? → Treat as replacement.
- Does the product doc list remove resources, IPL names, or a “run this with the MLO” helper? → Follow that order on staging first.
- Are you already running another MLO on that same footprint? → Stop. Disable the old one before the new one.
- Still clipping after following the doc? → Isolate (one MLO, no other maps in district), then ticket the seller with screenshots and resource names.
When you shop hospital and PD categories, read every listing for replacement language—those shelves are where double-interior tickets concentrate.
What “remove” YMAPs do (high-level)
You do not need to reverse-engineer Rockstar’s map pipeline to run a clean city. You do need the right mental model.
- IPLs (Interior Proxy List / interior placement concepts operators meet in docs) control which vanilla interior pieces activate. Leftover IPLs are a common reason a “new” hospital still shows the old lobby furniture or shell.
- Remove YMAPs (often shipped as a small companion resource or folder the seller documents) tell the game *not* to keep streaming specific vanilla placements in that footprint—so your paid shell is the one that remains.
- Your MLO’s own YMAPs / YTYPs / YBNs place the new interior, props, and collisions.
High-level operator rules:
- Prefer the seller’s documented remove pack or disable list over random forum snippets for other products.
- Start remove helpers with the MLO (and in the order the readme states)—not “whenever.”
- Do not stack three different “universal remove everything” resources from unrelated packs; that is how you create new holes elsewhere in the city.
- This guide stays operational: follow licensed product docs. We do not publish exploit-style map dumps, leaked remove lists for unpaid assets, or weaponized conflict recipes.
If a listing says “just ensure it” for a Pillbox or MRPD-class rebuild and never mentions removals, ask support *before* production—or choose a pack with explicit conflict notes.
Common hotspots: Mission Row, Pillbox, Benny’s, banks
US RP cities hit the same conflict corridors repeatedly:
Mission Row / city PD Replacement PDs compete with the vanilla station and with *each other*. Dual-MRPD (two paid PDs ensured, or old + new) produces classic two-lobby clipping. See our Mission Row PD MLO buyer context, then browse the PD category for one station that matches your department size—not two.
Pillbox / central medical Hospital replacements are IPL-sensitive. EMS notices double triage desks immediately. Prefer clear docs; compare options via the Pillbox Hospital MLO lander and the broader hospital category.
Benny’s-style / busy mechanic footprints Tuner and garage rebuilds on well-known shop shells can leave old lifts, doors, or exterior props. Check remove notes the same way you would for PD. Explore mechanic MLOs with location and conflict text in mind—not only bay screenshots.
Banks and other landmarks High-traffic interiors with strong vanilla identities behave like mini-replacements. One landmark pack per footprint; stage before live heists or teller RP.
Pattern: famous vanilla slot → expect remove work → never dual-claim the slot.
Load-order & dual-MRPD mistakes
Most “my new PD is haunted” tickets are configuration, not destiny.
Frequent mistakes:
- Ensuring two replacements for one building — Old free MRPD + new paid MRPD, or two store packs both marketed as Mission Row. Disable one completely (folder out of `resources` or stop ensuring it), not “comment half the stream.”
- Remove resource never started — The MLO is ensured; the seller’s remove/IPL helper is not.
- Wrong ensure order — Dependency or remove helper must start as documented (often before or with the main MLO). Starting only the pretty folder is incomplete.
- Group `ensure [maps]` hiding a failure — A silent fail inside a big group looks like “vanilla won.” Prefer ensuring the specific resource names while diagnosing.
- Caching confusion — You fixed staging; players on production still have old streamed assets until a clean restart / cache refresh policy you already use for map updates.
- Script blame — Doorlocks and target zones in the old lobby do not cause clipping walls; they cause wrong markers. Fix map conflicts first, then move coords.
Load-order rule of thumb for diagnosis: dependencies → remove/IPL helpers → MLO → job scripts that teleport into the interior. Confirm the exact order on the product page when it differs.
Staging test protocol (one MLO at a time)
Do not debug clipping on a full production city with forty maps. Use a short, boring protocol:
- Clone or use a staging server with the same gamebuild you run live.
- Disable other maps in that district (other PDs, hospitals, or mega-packs nearby).
- Install only this MLO (+ documented remove/dependency resources) using the install guide: correct folder nesting, manifest at the resource root, explicit `ensure` lines.
- Restart and read the console — resource started, no missing stream spam.
- Walk the footprint cold — approach from the street, enter every public door, check stairs/elevators, booking/triage/bays, and one staff-only door.
- Screenshot failures — exterior, interior, and the exact resource names ensured.
- Re-enable maps one at a time — when clipping returns, you found the neighbor conflict.
- Only then update ESX / QBCore / QBox job coords, doorlocks, and targets.
One replacement per staging pass. If you change Pillbox and MRPD in the same window, you will not know which edit caused the ticket.
When to ticket the seller vs fix locally
Fix locally (your side) when:
- The resource was double-nested or never ensured
- A second pack still claims the same vanilla slot
- The remove helper was not started
- Job scripts still use old coordinates (markers wrong, shell looks fine)
- Another district map overlaps the same block and isolation fixed it
Ticket the seller when (after isolation):
- Docs were followed, only their pack + remove helper is running, and double interiors or doors-into-concrete remain
- Collision fails in rooms shown in the official gallery
- Required remove instructions are missing from the download but the listing promised a replacement
- Gamebuild notes on the page do not match what support later claims
Send with the ticket: resource folder names, ensure order, gamebuild, framework (for script questions only), and screenshots from the staging-only test. That cuts a day off back-and-forth.
Skip leak archives and “cracked” remove packs as a “fix”—they are a security and compliance risk for US server brands, and they often ship the wrong removals for the SKU you actually bought. Buy licensed, follow that product’s docs, use Discord/store support.
Soft CTA: hospital + PD categories + install guide
Replacement-heavy interiors are where this article earns its keep. Shop with conflict notes open:
- FiveM Hospital & Pillbox MLOs — medical replacements; read IPL / remove notes per listing
- Pillbox Hospital MLO guide — buyer context for the classic central hospital slot
- FiveM PD MLOs — stations; avoid dual-MRPD
- Mission Row PD MLO guide — footprint planning for city PD
- FiveM Mechanic Shop MLOs — shop shells that may touch known vanilla garages
- How to Install a FiveM MLO — ensure, nest, and first-boot testing
- Full shop — licensed maps across the rest of the city stack
FiveM MLOs is built for US English RP operators who want clear product pages, instant licensed downloads, and support when a replacement does not match the listing. Stage first, run one footprint at a time, and only then wire jobs into the new shell.
FAQ
Why does my new MLO clip through the old building? Usually the vanilla interior (or another MLO on the same footprint) is still loading. Confirm remove/IPL steps, disable dual replacements, and retest on staging with only that pack.
What is a remove YMAP in plain language? A map placement file (often shipped as a small helper resource) that stops specific vanilla pieces from streaming so your replacement interior can occupy the space cleanly. Use the one documented for *your* product.
Can I run two Mission Row PD MLOs if they look different? No. Two packs claiming one vanilla slot is the classic dual-MRPD failure mode. Pick one, remove the other fully, then test.
Does install order fix all FiveM MLO conflicts? It fixes many—especially missing remove helpers and failed ensures—but it will not merge two incompatible replacements. Isolation testing tells you which case you have.
Is this different for ESX vs QBCore? The map conflict is the same. Frameworks only change how you update job coords and doorlocks *after* the interior stands alone without clipping.