Skip to content

RPF archives

Place .rpf files under resources.pack.path. They are discovered recursively and mounted when the client loads the game world. Loose assets and archives can be included in the same resource bundle.

With resources.pack.path = "client", an archive can be placed here:

client/
└── assets/
└── street_props.rpf

The archive can have any filename with the .rpf extension. Keep the asset names and internal metadata references consistent with the exported pack. Publish it using the resource publishing workflow. For its first installation, restart GTA through the helper.

Archives are discovered without entries in GTA’s dlclist.xml or RPF_FILE declarations. Keep unused archives outside the client source folder.

Format Loading behavior
RPF7 with OPEN encryption mode Read directly by the client.
RPF7 with GTA archive encryption Opened through GTA’s archive loader. The archive must be compatible with the installed game build.

Files with an invalid RPF7 header are rejected. Nested archives are supported up to 32 levels deep. Their directory structure is preserved and their contents are read without extracting the archive to disk.

The resource encryption setting also applies to packaged RPF files. It is independent of the archive’s own encryption mode.

The outer archive’s root content.xml supplies metadata declarations for the pack. For example, street_props.rpf can contain another archive:

street_props.rpf
├── content.xml
└── stream/
└── props.rpf
├── street_bin.ydr
├── street_bin.ytd
└── street_props.ytyp

The outer content.xml registers the archetypes inside props.rpf:

<?xml version="1.0" encoding="UTF-8"?>
<CDataFileMgr__ContentsOfDataFileXml>
<dataFiles>
<Item>
<filename>stream/props.rpf/street_props.ytyp</filename>
<fileType>DLC_ITYP_REQUEST</fileType>
</Item>
</dataFiles>
</CDataFileMgr__ContentsOfDataFileXml>

Paths are relative to the outer archive root. Include the nested archive’s filename in the path, as shown above. The model and texture dictionary are discovered automatically.

A nested archive’s own content.xml is not processed automatically. Put the required declarations in the outer archive’s content.xml. A pack that only needs streaming registration can omit content.xml. Files that need metadata loading must have the appropriate declarations.

The same metadata types and XML structure described in Load custom assets apply inside archives. XML files referenced by includedDataFiles must be readable from the outer archive when its metadata is parsed. Keep those XML files in the outer archive. Paths inside them still resolve from its root.

Check the pack’s content.xml and its referenced files before publishing it. Loading supports streaming assets and the declared metadata files. Automatic DLC activation through setup2.xml and arbitrary content change sets is not supported. Packs that depend on those features need their required metadata expressed through the supported content.xml sections.

Each pack’s metadata paths resolve within its own mounted archive. References to another DLC device do not establish a dependency on that pack. Asset names still share GTA’s namespace, so renaming the outer RPF does not resolve model or texture name conflicts.

Check the client logs when an archive fails to load:

Message Check
invalid RPF7 header Verify the file is a complete RPF7 archive.
failed to validate OPEN RPF Check the archive’s entries and directory structure, then rebuild it with your asset tool.
GTA rejected RPF Check the encrypted archive’s format and game build compatibility.
missing included RPF data file Check that the referenced XML exists at the path inside the outer archive.
failed to load data file Check the metadata path, its fileType and the files it references.

Updating a bundle containing GTA-encrypted archives requires a GTA restart. For OPEN archives, some replacements of existing models or textures can apply on reconnect. Changes to the asset set or metadata require a restart. Follow the restart rules and any restart message from the client.