How to install an MLO on a FiveM server

An MLO adds a real, walk-in interior to the map: a police station, a hospital, a shop or a house. Installing one is usually a five-minute job, but most problems (invisible walls, falling through floors, two interiors fighting over one spot) come from skipping the checks before you install. This guide covers both.

By the HighLeaks teamUpdated 8 November 20266 min read

What is inside an MLO

File	What it does	If it is missing
.ymap	Places the interior and props in the world	Nothing appears
.ytyp	Defines the interior and its archetypes	Interior does not load
.ybn	Collisions	Players fall through floors or walk through walls
.ydr / .ydd	Models	Missing objects
.ytd	Textures	Purple or blank surfaces

Check before installing

Location conflicts. Two MLOs at the same spot (for example two Mission Row police stations) will flicker or overlap. Remove or disable the old one first.
Game build. Many MLOs use props from newer GTA V updates and only work when the server enforces that build (see below).
Dependencies. Some maps need a shared prop pack or another resource; read the release notes.
Escrow. Paid MLOs sold through Tebex are often escrow-protected: they only run on servers whose license key belongs to the Cfx.re account that bought them.

Install step by step

Create a [maps] folder inside your server's resources folder, so maps stay grouped.
Copy the MLO folder into [maps] without renaming files inside stream.
Open its fxmanifest.lua and check that it declares itself as a map (example below).
Add ensure your_mlo_name to server.cfg, after your framework resources.
Restart the server (a full restart is safer than refresh and start for maps).

fx_version 'cerulean'
game 'gta5'

this_is_a_map 'yes'

files {
  'stream/**/*.ytyp'
}

data_file 'DLC_ITYP_REQUEST' 'stream/**/*.ytyp'

A minimal fxmanifest.lua for an MLO. Files in stream/ are streamed automatically.

Set the game build

If the release says it needs a specific game build, set it in server.cfg (or in txAdmin → Settings → FXServer). For example:

sv_enforceGameBuild 3095

Use the build the MLO asks for, or a newer one. Raising the build makes every player download that game version the next time they join, so change it during a quiet hour.

Test it in game

Teleport to the coordinates in the release notes (most admin menus and txAdmin's player menu can do this) and walk the whole interior. Check doors, stairs and every floor for collisions, look for flickering surfaces, and open the F8 console for streaming warnings.

In-game check of a newly installed MLO interior

Troubleshooting

Symptom	Likely cause	Fix
Interior does not appear	Resource not started, or no `this_is_a_map`	Check `ensure`, the manifest and the console.
Falling through the floor	Missing or mismatched .ybn	Re-copy the original stream files.
Flickering walls	Another map at the same location	Disable the other MLO or the base-game IPL.
Purple or missing textures	Texture dictionary missing or too large	Check the .ytd files and the oversized-asset warnings.
Works for you, not for others	Game build or escrow ownership	Match `sv_enforceGameBuild`; check the key owner.

Keep maps fast

Every MLO adds streaming work for players who walk past it. Install the interiors your roleplay actually uses, prefer releases with optimised textures, and remove maps you replaced instead of leaving them stopped in the folder. Doors usually need your door-lock resource configured separately.

Browse community MLO releases and feedback in the MLO hub. New to running a server? Start with how to set up a QBCore server.