Maps and MLO interiors
Keep the complete exported map pack, including its placements, archetypes, collision and dependency manifest.
Place the map files
Section titled “Place the map files”With resources.pack.path = "client", an interior pack can use this layout:
client/└── assets/ └── harbor_shop/ ├── content.xml └── stream/ ├── _manifest.ymf ├── harbor_shop.ymap ├── harbor_shop.ytyp ├── harbor_shop.ybn ├── harbor_shop.ydr └── harbor_shop.ytd| File | Purpose |
|---|---|
.ymap |
Places entities in the world and records their transforms. |
.ytyp |
Defines archetypes, including MLO interior definitions. |
.ybn |
Supplies collision data. |
.ymf |
Records map and archetype dependencies used by GTA. |
.ydr, .ydd, .ytd |
Supply models and texture dictionaries. |
Use the pack’s actual names and full file set. A map can contain several files of each type, nested folders and replacements for existing world assets. Preserve the internal references and relative organization from the export. For archived packs, see RPF archives.
Register the interior definitions
Section titled “Register the interior definitions”Add this content.xml to register the example’s YTYP:
<?xml version="1.0" encoding="UTF-8"?><CDataFileMgr__ContentsOfDataFileXml> <dataFiles> <Item> <filename>stream/harbor_shop.ytyp</filename> <fileType>DLC_ITYP_REQUEST</fileType> </Item> </dataFiles></CDataFileMgr__ContentsOfDataFileXml>Declare every YTYP required by the pack using its exact resource-relative path. YMAP, YBN, model and texture files are discovered automatically.
YMF manifests are also discovered and processed automatically. They supply map and type dependencies used for interior loading and room tracking. Keep the manifest supplied with the export, including when the interior’s shell is already visible.
The content.xml location establishes the resource root. In this example,
stream/harbor_shop.ytyp resolves within assets/harbor_shop/. See
Load custom assets for split declarations
and naming rules.
Activate and visit the map
Section titled “Activate and visit the map”Publish the resources, restart the server to select the release, then restart GTA through the helper. Visit the coordinates authored in the YMAP or provided by the map author.
If the map requires explicit IPL activation, request its authored IPL name
from a client script. For a map named harbor_shop:
// @ts-check/// <reference types="@revomp/types-natives" />import * as natives from 'natives';
natives.requestIpl('harbor_shop');Run this from a configured client entry point. Use the IPL name supplied with the map, which can differ from the resource folder name. Request each required IPL when the pack contains several.
IPL requests are asynchronous. natives.isIplActive(name) reports IPL activation.
When entering an MLO, also check that its interior and destination collision
have loaded.
For a scripted teleport, preload the destination scene and collision before
moving the player inside. natives.requestCollisionAtCoord(x, y, z) requests
collision at the destination. After the interior is registered,
natives.getInteriorAtCoords(x, y, z) returns its ID for a point inside it.
Wait for a nonzero ID and natives.isInteriorReady(interior) before completing
the transition. Use coordinates inside the intended interior when checking it.
Map behavior and dimensions
Section titled “Map behavior and dimensions”Door controls, interior entity sets and required IPL removals from a community map need to be integrated into your scripts. The asset loader processes map files and metadata. It does not run another platform’s scripts or manifests.
The multiplayer session uses GTA’s MP map hierarchy. Use replacements made for
the active map variant. Calling natives.onEnterSp() switches the hierarchy
and can undo that setup. If a stock building or collision blocks the new
entrance, check the pack’s required replacements and IPL removals.
Each client has one GTA map. Dimensions separate players and scripted entities while the native map geometry remains part of the same world. Coordinate any local IPL changes in client scripts. See Dimensions and visibility.
Check the interior
Section titled “Check the interior”Approach from outside, walk through the entrance and visit each room. Check floors, walls, stairs and doorways for collision, then look through the portals between rooms. Test leaving and returning after the area streams out.
With two clients, check that both see the same geometry and can use the same entrances. Test any scripted doors, entity sets and IPL changes on both clients.
| Symptom | Check |
|---|---|
| The map does not appear | Check the authored coordinates, YMAP files, required IPLs and archetype declarations. |
| The shell appears but the interior is incomplete or room tracking fails | Check the YTYP, YMF dependency manifest and referenced models. |
| An invisible wall blocks the entrance | Check remaining stock collision, required replacements and conflicts with other map packs. |
| The floor is visible but the player falls through | Check the collision files and destination loading before teleporting. |
| Rooms or objects disappear from particular viewpoints | Check room and portal definitions, dependencies, bounds and LOD data in the export. |
| Doors or optional furnishings do not work | Check the door or entity-set setup required by the map’s scripts. |
In the client logs,
look for failed to load data file, failed to load map manifest and
raw streaming registration failed. Use the reported path to find the failing
asset or declaration.
Changes to YMAP, YTYP, YBN or YMF files require a GTA restart. Follow the restart rules when publishing map updates.