How the reviewed JSON outfit selector works
The pinned menu.lua reads an array from outfits.json and constructs labels from Gender and Name. Clothing values such as Top and Pants are colon-separated numeric pairs; the implementation uses them as drawable and texture arguments for component changes. Those indices must match the assets available to the selected ped in your environment.
The implementation applies outfits only when Male matches mp_m_freemode_01 or Female matches mp_f_freemode_01. For its supported props, a drawable value of -1 clears the prop. Do not assume that clearing convention belongs in every clothing field or that another selector uses this format.
Some example fields do not drive behavior in this code: the sample contains Ear and category labels, but the reviewed application function does not apply an ear prop or build category navigation from those labels. A field appearing in an example file is not proof of a corresponding UI or gameplay feature.
Why a selected uniform can look wrong
Start with the exact resource revision, player model and installed clothing set. If the intended model differs, check that before changing every drawable. If only one piece is wrong, compare that component and texture with the working record rather than replacing the whole character appearance.
Use a disposable staging character and record its appearance before switching uniforms. Test the intended model and an unsupported model separately. A menu should not be judged only by whether it opens; observe what actually changes and how the appearance system restores state afterward.
Permissions and saved outfits need their own integration
The reviewed ScrachStack menu registers a client command and applies clothing locally. That file does not establish a job-based authorization system or database-backed outfit persistence. Do not treat an agency name in JSON as an access rule.
If uniforms are restricted, choose an integration that enforces your intended roles and test an ordinary character as well as an authorized one. Coordinate with the server’s appearance resource so a uniform change does not conflict with saved outfits. A successful local change is different from the desired appearance after reconnect or duty changes.
A small staging acceptance checklist
Follow the original package instructions, preserve the existing configuration and validate one outfit before importing a large list. This is a proposed test plan, not a record of gameplay results.
- Confirm the correct menu library starts and the manifest is at the resource root.
- Validate outfits.json syntax and keep numeric pairs consistent with the reviewed format.
- Select one outfit on the intended freemode model and inspect each component.
- Check supported props and intentional clearing independently.
- Test restricted access using an ordinary and an authorized character.
- Reconnect and change duty state to verify the intended saved-appearance behavior.
- Record conflicts with other clothing resources before expanding the list.
Choose the next customization guide
Use the clothing-packs guide for asset and menu separation, the outfit-code guide for implementation-specific sharing formats, and the Illenium appearance guide for that system’s integration requirements. These are related tasks, not interchangeable configuration recipes.
For installation failures, use the scripts guide to inspect folders and manifests. Check current platform entitlements and edition support through the creator and Cfx documentation rather than copying old subscription claims from forum replies. The reviewed resources concern GTA V/FiveM and do not establish GTA VI uniform support.
Questions, answered.
What command opens the EUP menu in FiveM?
Both reviewed examples document /eup, but your server may use another implementation or restrict access. Follow the community’s instructions.
Does every EUP menu require NativeUI?
No. The reviewed ScrachStack example imports ox_lib, while the BackwardsUser release lists NativeUI. Check your actual manifest and README.
Does outfits.json automatically save uniforms after reconnect?
Not by itself. The reviewed selector applies clothing, while persistent appearance behavior requires the appropriate server integration.
Sources & editorial notes
Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- ScrachStack — EUP UI README Pinned source reviewed November 7, 2026; no FiveM runtime test performed.
- ScrachStack — EUP UI manifest Pinned source reviewed November 7, 2026; no FiveM runtime test performed.
- ScrachStack — EUP UI client implementation Pinned source reviewed November 7, 2026; no FiveM runtime test performed.
- ScrachStack — EUP UI outfit example Pinned source reviewed November 7, 2026; no FiveM runtime test performed.
- BackwardsUser — EUP-Menu release Author-described NativeUI implementation; not gameplay tested.
Published by an independent editorial brand. Read our editorial standards.