Common Issues

Start with the exact setup

Record the Clothing version in fxmanifest.lua, the framework and inventory versions, and whether Creator, Barber or another appearance resource is running. When updating, merge your configuration into a complete download including UI and translation files. Keep the asset catalogue and saved outfits backed up.

Shops and configuration

The clothing shop does not open

Check the first resource startup error, Config.Shops and Config.NativePrompt in shared/config.lua. When using murphy_interact, start its RedM-compatible ox_lib dependency, then murphy_interact, before Clothing. Use the interaction key configured on your server. If the optional Config.MenuCommand opens the shop, investigate the interaction or location rather than deleting outfit data. See Installation.

“attempt to index a nil value (field 'Prompt')”

If the error is at an expression such as Lang.Prompt.open, compare shared/lang.lua with the file distributed in your Clothing release. It must contain the prompt translation table expected by the client. Restoring the complete translation structure fixes that missing-table cause; installing a prompt library does not create Lang.Prompt.

Face customization or development categories appear in a clothing shop

Set Config.DevMode = false in shared/config.lua. Reopen the shop and check the normal customer categories. Development mode should not be used as a workaround for shop access or missing items.

Some clothes are absent from the catalogue

Check the selected multiplayer/NPC asset mode and the filters present in your installed configuration. Identify the gender, category and model number of the missing item. A trailer can show a different release or a server's custom streamed assets. Do not assume every item in an old video is present in the current catalogue. For hiding current items without shifting saved indices, see the 3.46.0 release guidance below.

A translation, camera slider or button breaks after an update

Verify that Lua, shared/lang.lua, ui/script.js, ui/lang.js and any UI files listed in that release's notes were updated together. Retain translated values while merging newly required keys. If only one control still fails, report that control, the installed version and the first F8 error; a historical camera workaround is not a universal fix.

Outfit items and saved looks

“item clothes was added as usable but does not exist”

Check Config.OutfitItem in shared/config.lua and register that exact item in your framework's item registry. Use your inventory version's required fields. A generic SQL insert from another server can use the wrong schema. Verify startup registration, buy one test outfit and use the resulting item.

Different RSG outfits stack into the same slot

Configure the outfit item as unique = true in RSG's item definitions so separate outfit metadata is kept in separate slots. Merge that property into the existing definition rather than replacing it with an incomplete example. Test two newly obtained outfits; changing the item definition is not a promise to reconstruct metadata already lost in an old stack.

I want saved outfits without inventory items

From Clothing 3.35.0, Config.OutfitItem = nil disables the outfit item while keeping the shop purchase, saved outfit and application workflow. Use a release that supports the option. Do not remove the outfits table to disable inventory items.

An outfit item says “Clothes are torn”

The item can refer to an outfit that no longer exists in the outfit data. Support confirmed this case, and the inventory adapters check the referenced outfit before applying it. Compare a newly saved outfit item with the affected old one. Preserve the item metadata and relevant record for diagnosis; repeatedly granting the same broken item or recreating the entire database is not a repair.

Clothes work in the shop but disappear after reconnecting

First complete the shop's save or purchase action. Then check whether saved data exists and whether a later framework or appearance script overwrites the look. Test a reconnect, revive and wardrobe change separately. Keep dependencies required by Creator's framework integration; do not disable rsg-appearance or vorp_character blindly.

A successful manual reload narrows the issue to loading or application but does not prove it is fixed. Use the current official adapters before trying historical Wait(5000) patches. Include all appearance resource versions and the first F8/server error in the report.

Colours or shirts change when switching outfits or toggling an outer layer

Several releases corrected wearable state and tint handling. Clothing 3.45.0 fixed incorrect pieces being applied and then saved into later outfits. Outfits already saved with an incorrect garment can retain that garment after the update; edit an affected outfit once after updating and verify it on reconnect. Do not clear every player's wardrobe.

Framework commands such as /hat or /mask give different results

Those commands can belong to another appearance system. Test the Clothing management menu or the documented Clothing API first. An external command must call the correct integration to update Clothing's state; changing the ped directly can leave its saved state inconsistent. See Commands, API Documentation and the free Radial Menu.

I need a free wardrobe, not a shop purchase

Use the client event murphy_clothes:OpenWardrobe documented in API Documentation. Wardrobe mode was added in 3.39.0 and its unwanted creation buttons were corrected in 3.40.0. Verify the installed version and open it with a test character that already owns an outfit. A standard shop-opening event is a different workflow.

A lamp stays attached to the character after leaving the tailor

This was a reported cleanup bug, including a case corrected in 3.40.8. Check the release notes and update the affected client files together. Record whether it happens on ordinary exit, death, disconnect or a rapid close. Do not run a global world-object deletion command to remove one orphaned light.

Known issues by release

Check the installed version in fxmanifest.lua before applying a release-specific fix. Back up configuration and data before updating.

The clothing or outfit menu stops responding

Release reference: 3.45.6. The 3.45.6 notes identify unanswered interface callbacks and include the menu fix. Check the installed Clothing version and, when applicable, Creator 1.47.6 and Barber 1.22.3. Retest the original sequence after updating.

Hiding clothes changes existing saved outfits

Release reference: 3.46.0. The 3.46.0 notes introduce Config.HiddenClothes to hide selected models without removing entries from shared/murphy_assets.lua. Deleting catalog entries shifts later saved indices. Use the configuration supplied with 3.46.0 for this feature; do not paste its options into an older release and assume support.

Source: Versions on the Murphy's Clothing product page, consulted 9 September 2026. These are release-note findings, not a claim that the scenarios were reproduced in-game for this documentation.

If the issue remains

Report the installed version, framework, first console error, reproduction steps, and expected versus actual result through support. Remove credentials and unrelated player information from attachments.