tagMissing GTX Label

Intro

You can ignore these warnings. Our resources still work, we are just creating a warning that the labels may look botched in the menus because they are missing, and we are forced to use a fallback.

Vehicle Labels

Every vehicle has a display name (e.g. SULTAN2) and a GXT label (e.g. Sultán RS). We use the GXT label to show a clean, human-readable name throughout our resources.

Why this warning appears

[WARNING] Invalid label for model 1234567890 using display name "MYADDON", using fallback "Myaddon"

Your addon vehicle has a display name in its vehicles.meta, but no GXT label has been registered for it. We fall back to title-casing the raw display name, which usually doesn't look great.

How to fix it

Register a GXT label using AddTextEntry in a client-side script in your addon vehicle resource. The first argument must match the <gameName> from your vehicles.meta:

AddTextEntry("MYADDON", "My Addon Car")

Once registered, the label will be picked up automatically and the warning will disappear.

circle-check

Creating a label file

If your addon vehicle doesn't already have labels set up, you can create one yourself. Here's a typical addon vehicle resource structure:

1. Create labels.lua

Create a new file called labels.lua in the root of your vehicle resource. Add an AddTextEntry call for each vehicle, where the first argument matches the <gameName> in your vehicles.meta:

2. Register it in fxmanifest.lua

Make sure the file is included as a client script:

3. Find the display name

If you're not sure what display name to use, check the <gameName> field in your vehicles.meta:

The <gameName> value is what you pass as the first argument to AddTextEntry.

Last updated