Buy a FiveM MLO,interiors you can actually walk into.

An MLO (Map Load Object) is a walk-in custom interior for GTA V and FiveM. Unlike an ordinary building, which is empty inside, an MLO has an interior of its own that streams in dynamically as you enter, with no loading screen. A portal system makes that possible: doors and windows are defined as portals, and the engine uses them to decide which rooms need rendering. On top of that come room definitions, occlusion data, custom lighting, authored collision and navigation data for NPCs. Technically an MLO consists of a .ytyp file defining rooms and portals, the model and collision files (.ydr, .ybn, .ytd), and a .ymap that anchors the interior at its position in the game world. For players it simply means: open the door, you are inside, no waiting.

Put simply: the .ymap decides where something stands in the world, the MLO decides what it looks like inside and that you can walk into it. A .ymap is a placement file. It defines which objects appear at which position, rotation and scale: building shells, props, fences, vegetation, light sources. A pure mapping often consists solely of .ymap files and changes only the exterior. An MLO, by contrast, is an archetype with an interior. It describes rooms, portals between those rooms, occlusion and timecycle data, including which room has to be visible when. That is why an MLO works without a loading screen and still performs. In practice the two belong together: the .ymap puts the MLO at its coordinate in Los Santos, and the MLO supplies the walk-in interior behind it.

Prices for finished interiors, exteriors, mappings and bundles are shown live in the shop, that is where you see the binding final prices including all charges. For commissioned work the price depends on five things: floor area and number of rooms, number of portals, the share of custom-modelled props versus vanilla assets, whether an exterior is included, and how many review rounds you want to plan for. You get a fixed quote in the portal before work starts, not a timesheet afterwards.

You create a resource with fxmanifest.lua and a stream folder, copy the MLO files (.ytyp, .ymap, .ydr, .ybn, .ytd) into the stream folder, register the .ytyp in the manifest and start the resource in server.cfg. Then reconnect once so the assets stream cleanly. Our MLOs arrive streaming-ready, the resource is already assembled, you only upload it over SFTP into your resources folder. If something is not visible straight away, it is almost always an unregistered .ytyp or a second resource overriding the same building. We help with installation.

Yes. Our MLOs are built framework-independent and run under ESX, QBCore and standalone. The MLO itself is a stream asset and knows no framework, the integration only appears where you place jobs, door locks or interaction points. Where we ship such coordinates and zones, they are documented so they carry over into either framework.

An MLO contains no script code and therefore creates no server load in the resmon sense, it shows 0.00 ms there. That is true of every streamed asset, though, and on its own is not a quality marker. The real cost of an MLO lands on the client side: polycount, texture memory, draw calls, the number and quality of LOD stages, and the size of the streaming budget. That is exactly where we optimise: textures at a sensible resolution rather than 4K across the board, several LOD stages per object, occlusion set so only the room you stand in gets rendered.

No, the standard licence covers a single server setup. That may well be a connected infrastructure you run yourself throughout. If you run several logically or organisationally separate setups, such as multiple communities or brands, each setup needs its own licence unless the product description says otherwise. Extended forms such as multi-server, reseller or whitelabel licences exist by separate written agreement. Our EULA is what governs.

Buying from the catalogue gets you the ready-to-run resource, exactly what you need to operate it. Source files such as Blender or 3ds Max projects and texture projects are not part of the standard licence. If you need them for a commissioned project, we put that in writing before work starts, because it requires a separate agreement. Either way: complete source files must not be published in a form that lets third parties download or reuse them.

You start the enquiry in the customer portal: title, project type MLO/interior, complexity, budget range and target date. Targeted questions follow, location on the map, style and mood, adjacent maps, particular requirements for performance, collision or sightlines. You upload reference images and mood boards directly. From the brief we cut a fixed quote, which you accept in the portal or send back for changes. After that you see every phase live: in progress, milestones with a test-server link, review, handover. Files and invoice end up on the commission. Note that we currently accept commissions selectively only.

On any FiveM server where you have file access, an MLO needs no more than that. If you do not have one yet, or want to move to a host with full SFTP access: with us you get both from one place, and on performance questions the same contact sees the asset and the machine it runs on.