Appearance
Uniforms and optional custom skins
The default framework uses stock character skins. Stock faction uniforms remain configurable while custom uploads are disabled. Enable custom models only when you plan to supply, distribute and maintain your own DFF/TXD assets.
Stock faction uniforms
- As the faction’s owner character, use
/fskinadd [skin] [tier] [squad] [locker type]in-game to create a stock uniform. For example,/fskinadd 280 3 0 0adds a stock police skin to that character’s faction. - Open Factions → Faction Skins (
/acp/faction-skins) as Manager or above. - Choose the faction and its usable-uniform list. Refresh the web page after the in-game addition.
- Edit squad and locker-type metadata, then save. With custom uploads disabled, ACP manages these existing rows; it does not show a general stock-skin creation form.
- Use
/reloadfskinsin-game to refresh uniform rows after web edits. - Test
/uniformor/fskinsat the intended locker.
Use normal stock skin IDs; model 74 is not a valid normal stock choice. A locker-type value of 0 offers a uniform at every locker for that faction. A positive value is the armory type ID, not a physical locker ID.
Uniform metadata is not equipment permission
The current uniform browser filters by faction, locker type and its squad logic. Although the database/UI store a uniform tier field, the browser does not enforce it as an equipment-style tier limit. Do not rely on that field alone to protect a rank-specific appearance. Test the actual selector or extend its checks. Armory weapon tier checks are separate and enforced at selection.
Enable optional model uploads
Configure both applications:
pawn
// gamemodes/config/header.pwn
#define FEATURE_CUSTOM_SKINS (1)dotenv
# web-platform/web/.env.local
CUSTOM_SKINS_ENABLED=trueChange the existing guarded define rather than defining it twice. Compile the gamemode, restart the web app, configure the agent and ensure artwork downloads work for your target clients. No external model pack is supplied.
Upload a faction model
Open the faction model-upload section, choose the owning faction and a valid stock base skin, then upload matching .dff and .txd files. Each file is capped at 16 MiB by the web upload path. The file pair and metadata must both be accepted.
The model must also be added to the faction’s usable uniforms; registration alone does not add a uniform menu entry. Set its squad/locker type as needed.
Fully restart the game after adding, deleting, enabling, disabling or changing custom model registrations. /reloadfskins reloads uniform rows; it does not replace already registered DFF/TXD models.
Upload a personal model
Open Operations → Custom Skins (/acp/skins). Select the owning character and the requested base/asset pair. The record ID determines the personal custom model ID; it is not the character ID.
After a successful upload and full game restart, the owning character uses:
text
/customskin [personal skin record ID]/customskin 0 restores stock skin 0. That command exists only in a custom-skin-enabled build. A model assigned to another character is not available through the owner-checked personal command.
Registration ranges and limits
| Family | Custom model range | Startup limit |
|---|---|---|
| Faction | 20000–24999 | 500 enabled models |
| Personal | 25000 + record ID, where record ID is 1–4999 | 500 enabled models |
The loader validates bases, IDs, paths and ownership, and reports models it cannot register. Keep the files below the game’s models/ tree and transfer them through the private agent. Do not use a custom ID as though it were a stock skin.
Diagnose a failed model
Check both feature flags, database metadata, file existence/case, base/model range, ownership, agent permissions and artwork access. Inspect [Custom skins] startup lines. A successful file upload does not prove a model is valid in GTA or that the client downloaded it; playtest your assets.