Common Issues

Before changing character data

Record the versions of Creator, Clothing and Barber that are actually installed in their respective fxmanifest.lua files. If you update, merge your configuration into a complete download, including the UI, translations and editable adapters listed in the release notes. Updating only the protected files can leave incompatible files running together.

Use Troubleshooting to collect the first error. Keep character and appearance records intact while finding the cause.

Setup and configuration

F3 opens a development menu during normal play

Set Config.DevMode = false in shared/config.lua. Development shortcuts are not the normal character-selection or appearance-editing workflow. For an existing character, use the configured Second Chance workflow and its permissions. Reconnect to test normal character selection with development mode disabled.

Another creator opens, or the player gets stuck between two selectors

Follow the instructions for your exact framework in Framework support. Creator includes its own character selector; connecting a different multicharacter system is an integration task, not a configuration switch.

Keep dependencies required by that framework's installation. In particular, do not remove vorp_character or rsg-appearance just because their names contain “character” or “appearance”. The documented adapter flow determines which resource handles each step. Capture which interface opens first, the first F8 error, and whether the problem happens on creation, selection or reconnect.

Creator is installed without Murphy's Clothing

Check Config.murphy_clothing in shared/config.lua. Enable the integration only when murphy_clothing is installed and started. Installing Creator does not install Clothing. If the clothing stage fails, verify the integration flag and the Clothing startup error before changing Creator's save code.

Existing framework characters appear in the selector, but Second Chance does not reproduce their old look

Continuing to play an existing framework character and editing it with Creator are separate paths. An older character can remain selectable without its framework appearance being a complete Creator appearance record. Do not promise a lossless conversion between different appearance formats. Back up data and try Second Chance on a test character before offering a conversion to players. See Second Chance.

The language is configured, but some labels remain in English

Check Config.Locale and distinguish the interface files in ui/locales/ from Lua labels in client/settings/lang.lua. A custom locale needs the files and loader entries required by the installed release; changing the locale name alone does not translate strings. Update the matching interface files together, then reopen the menu. Follow Localization instead of copying a historical shared/locales.lua patch from a ticket.

A custom selection scene has missing peds or a misplaced camera

Compare one position, heading and camera with CharSelect / Decor / Camera Configuration. Check the configured interior is loaded, and whether another map resource manages the same interior. Some scenarios need a particular seat or game environment; a valid scenario name alone does not guarantee it will play at arbitrary coordinates. Restore one supplied scene in a test setup before changing multiple waits or animations.

Appearance, loading and saving

The character is correct after a manual reload, but wrong on reconnect or revive

This has appeared in several different loading and adapter bugs. It does not by itself prove that the saved data is corrupt. Record whether the model, body, clothes, hair or colours change, and which resource performs the spawn or revive.

1. Update the affected resources using the release notes below.
2. Test creation, reconnect and revive separately on a test character.
3. If a reload helps, report that result using your configured Config.LoadSkinCommand; it is diagnostic information, not a permanent fix.
4. If you use a custom spawn, revive or appearance script, compare its integration with the documented framework flow. Avoid adding repeated skin reloads or arbitrary delays to every spawn.

VORP stays on a black screen with “invalid table argument”

Support identified malformed framework appearance values as a cause of the reported d3a7b003ed343fd9 “invalid table argument” failure. Compare the affected adapter with the complete current download and preserve the configuration and character data. If a player still blocks, collect the first F8 error and identify the failing step; a black screen with a different error is a separate case. Do not change arbitrary saved components to zero to hide a native error.

RSG changes a female character to a male model on entry

The support fix in Creator 1.46.9 corrected the sex convention written to rsg-appearance data and included a startup repair for affected records. Use the official update path and review its startup output; do not manually change every player's sex in SQL. Test a new character and an affected existing character. A separate makeup or appearance resource may still require its own integration to persist its changes through Creator.

Health or stamina is low after loading

Report the installed version and the framework or HUD that restores saved vitals. Historical tickets include several distinct timing bugs and later corrections, so advice that Creator “never touches health” is not a reliable diagnosis. Compare the values before disconnect and after reconnect on a test character, and capture the debug output around loading. Do not globally heal players, reset database values or disable persistence as a generic repair.

My body sliders look correct to me but different to another player

Test with two clients observing the same character, and record both views and versions. The public 1.46.9 notes address body shapes being lost on observers' screens after clothing rebuilds and specify pairing that correction with Clothing 3.45.3. A local reload alone is not a multiplayer verification. Keep the distributed expression ranges while testing; do not extend slider limits or invent a synchronization event as a workaround.

An NPC ped has missing body parts or does not fit some clothing

The NPC preview removes its original clothes and hair so that it can be customized. Some NPC models do not contain complete underlying body meshes, and their proportions can differ from multiplayer models. Compare with mp_male or mp_female and identify the exact model and garment. A missing torso on a standard multiplayer character also needs investigation; do not dismiss every invisible body as an NPC limitation.

A transformation script becomes invisible or is changed back

A script temporarily changing the player to an animal or another model must coordinate appearance ownership. Use the documented Appearance Pause System, including resuming and restoring the character at the right point. Older ticket suggestions using a custom state bag are superseded by this API; setting an invented state bag alone does not pause the resources.

A starter-kit or character-background script does not run for new characters

Creator 1.47.5 added the VORP vorp:initNewCharacter notification and the framework-independent client event murphy_creator:client:characterCreated at the end of character creation. Check the receiving script's event and execution context. A new-character event is not a general login event; do not fire it on every character selection just to open a spawn selector, because it could repeat first-character rewards.

Known issues by release

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

Menus freeze after interacting with controls

Release reference: 1.47.6. The public release notes identify unanswered interface callbacks as a cause of menus becoming unresponsive. Creator 1.47.6 includes the fix. If Barber or Clothing are installed, their corresponding menu fixes are in Barber 1.22.3 and Clothing 3.45.6. Check all installed versions before retesting the same sequence of clicks.

Character previews show another character’s clothes or hair

Release reference: 1.47.5. The release notes describe asynchronous appearance replies reaching the wrong preview ped. The correction in 1.47.5 applies the appearance to the intended preview after that ped exists. Check this release before editing or deleting saved outfits.

A character is missing from its selection spot

Release reference: 1.47.4. The 1.47.4 notes identify selection-room streaming and off-screen pins as causes on slower machines. The fix waits for the room with a bound and provides a fallback pin. Record any remaining F8 message and the machine/framework combination.

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