Common Issues

Check the installation first

Use the actual Barber version in fxmanifest.lua, not only the date of your last download. Preserve configuration and appearance data when updating. Copy the complete set of files listed in the release notes, including editable adapters, UI files and translations.

The shop exists, but there is no interaction

Check Config.Shops, Config.framework and Config.NativePrompt in shared/config.lua. With the interaction-menu mode, start the RedM-compatible ox_lib used by murphy_interact, then murphy_interact, then Barber. Resolve their first startup error. Use the key configured in the installed interaction resource; an old video showing Alt is not proof of your current bind.

If Config.MenuCommand is enabled, try that command as a diagnostic. A working command with a missing shop interaction narrows the problem to location or interaction setup. See Installation.

The console mentions a nil field named “Prompt”

Read the file and expression in the error. Barber reads Lang.Prompt from shared/lang.lua; an outdated or incomplete translation file can therefore stop it before interactions are created. Compare that file with the same release's download and preserve the required table keys. Do not infer that every error containing “Prompt” means the uiprompt resource is missing.

Barber is used without Creator

Set Config.murphy_creator to match the resources you actually run. With Creator absent, use false; otherwise Barber may wait for an integration that is not present. With Creator enabled, verify both resources start successfully and use compatible asset data. You do not need to purchase Creator simply to resolve an incorrect integration flag.

Hairstyles, makeup and persistence

Hair looks right in the shop but is lost after reconnecting

Confirm the shop's save or purchase action completed. Previewing a hairstyle and closing the interface is not evidence of a successful save. Then distinguish a missing save from a failure to apply saved data: does reopening Barber or reloading the character restore the chosen look?

Reported RSG and VORP cases have included adapter loading order, missing skin-tone data on older characters and historical tint formats. Use the official updates, preserve saved appearance records, and test a reconnect and a revive separately. Do not re-create every character or apply an old adapter patch to a different framework.

Hair or beard becomes white, black, or loses its tint

Record the exact hairstyle, variation, colour settings, character model and trigger. Check whether the problem affects everyone, only older characters, or only one asset. Historical tint fixes changed the handling of older saves; forcing all tint values to zero is not a general repair. Check the installed version against the product's release notes, then reproduce with the same character and colour.

“Waiting for albedo” or “ped components not loaded” repeats

These messages concern character or skin loading; the text alone does not identify the cause. Check whether the appearance eventually loads, whether the first server error is in an adapter, and whether Config.murphy_creator matches your setup. A timeout with missing hair or a menu that never opens needs a support report. Do not suppress all errors or replace a skin lookup with an arbitrary constant.

The makeup item is missing from the inventory

The name is configured in Config.OverlayItem. Register that exact item in your framework's item definitions and check the registration warnings on startup. Older tickets refer to toilet; that is not a mandatory name for every server. Use an item definition appropriate to your inventory version, and avoid assigning the same usable item to unrelated scripts.

Can the makeup item save a haircut or beard?

The overlay item is for makeup overlays. Adding hair categories to Config.Overlayitems does not turn it into a hairstyle preset item. Use the barber workflow for hair and beards. This distinction was confirmed in several support replies.

Hair clips through a hat, or an NPC face looks different

Identify the exact hat, hairstyle and ped model. Some asset combinations do not fit each other. Barber 1.22.0 also stopped applying multiplayer head-texture overlays to custom ped-model characters because they could corrupt the face. Hair handling and makeup-overlay compatibility are different questions; do not promise that every NPC model supports all multiplayer makeup or hats.

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 hairstyle or colour menu stops responding

Release reference: 1.22.3. Barber 1.22.3 fixes interface callbacks that did not answer the browser. Check the installed version, update the affected resource using the release instructions, and repeat the selection that previously froze. A reconnect alone does not establish that the cause has been fixed.

VORP reports a missing GetCharIdentifier helper

Release reference: 1.22.2. The 1.22.2 notes describe a VORP adapter startup failure involving the former inventory API. This could leave framework helpers unavailable. Check the first server startup error and the installed adapter version; do not add a dummy GetCharIdentifier function to hide the failure.

Source: Versions on the Murphy's Barber 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.