A FiveM MLO is a streamed map resource and works on ESX, QBCore, QBox, and standalone stacks. Frameworks still control duty markers, beds, lockers, target zones, garages, housing entrances, and doorlocks.
Use this with the install guide and buyer’s checklist.
Map layer vs framework layer
The map contains geometry, collisions, portals, props, and its stream resource. The framework contains jobs, coordinates, zones, inventories, targets, blips, and lock IDs. Installing an interior does not update those numbers.
- Ensure the map and check that vanilla shells are not double-loading.
- Point interactions to rooms that exist in your shell.
- Stage the shell before copying job coordinates.
After-install checklist
- Entrance, duty, cloakroom, lockers, and boss desks.
- Beds, evidence, stash, crafting, and lifts.
- Garages, vehicle spawns, doorlocks, targets, and blips.
Measure coordinates in-game or use seller docs. Do not copy vectors from another server.
Jobs and targets
Hospitals need reception, beds, pharmacy, and ambulance points. PD needs lobby, cells, evidence, and garage points. Mechanics need intake, bays, lifts, storage, and delivery spawns. Housing needs entrance, stash, wardrobe, and lock rules.
Re-create zones with ox_target or qb-target. Fix conflicts first using the IPL guide.
FAQ
Different MLO for ESX and QBCore?
No. The map streams the same; job scripts and coordinates differ.
