Skip to content

Text labels and file overrides

Place binary .gxt2 files anywhere in the packaged client resources. With resources.pack.path = "client", a vehicle pack could include:

client/
└── assets/
└── harbor/
└── text/
└── labels.gxt2

GXT2 files are discovered automatically, including inside RPF archives. Labels load before asset metadata. No content.xml declaration is needed for them.

Export the file from a GXT2 editor. Each entry contains a label hash and its text, encoded as UTF-8. Each file can be up to 16 MiB.

For example, add these labels for a custom vehicle:

Label Text Reference in vehicles.meta
HARBOR_GT Harbor GT <gameName>HARBOR_GT</gameName>
HARBOR_MAKE Harbor <vehicleMakeName>HARBOR_MAKE</vehicleMakeName>

Use the same label names in the editor and metadata. The displayed name comes from the label’s text.

All custom GXT2 files share one label table. A custom label takes precedence over a stock GTA label with the same hash. The client’s built-in pause-menu labels use their own localization and take precedence over resource labels.

A duplicate hash within one GXT2 file rejects that file. Across separate files, the first loaded value is retained. A later, different value produces a duplicate text hash warning. Keep one definition for each custom label.

Put the replacement under a top-level folder named after the GTA virtual mount. The remaining path must match the file GTA opens:

File under the client resource root GTA virtual path
common/data/gameconfig.xml common:/data/gameconfig.xml
commoncrc/data/gameconfig.xml commoncrc:/data/gameconfig.xml

With resources.pack.path = "client", the first replacement uses:

client/
└── common/
└── data/
└── gameconfig.xml

The first folder becomes the virtual mount name. Putting this file under client/assets/common/ would target assets:/common/data/gameconfig.xml. Use the exact virtual path requested by GTA. common:/ and commoncrc:/ are separate paths.

Matching ignores letter case and treats / and \ as equivalent separators. Only matching files are replaced. Other paths continue to use GTA’s files. The aliases are prepared during startup, so configuration files can be replaced before GTA reads them.

Supply the complete replacement file, compatible with the supported game build. XML entries are not merged into the original file. For gameconfig.xml, start with a complete compatible configuration and edit the required values. A fragment containing only changed entries cannot serve as the replacement.

For metadata that adds vehicles, peds or other assets, use the declarations shown in Load custom assets.

Publish the resources, restart the server to select the release, then restart GTA through the helper. Changes to GXT2 labels and configuration overrides require a GTA restart.

In the client logs, TextContent: loaded confirms that a GXT2 file was parsed. If a label is missing, look for failed to load GXT2 and check the reported file and reason. Malformed headers, invalid string offsets, unterminated strings and duplicate hashes within a file cause it to be rejected.

If an override has no effect, check its path relative to the client resource root and the exact virtual path GTA reads. Check the contents against the supported game build if GTA fails to load after replacing a configuration.