RedM documentation

Murphy's Creator

Advanced

Appearance Pause System

Creator: Use the client appearance-pause exports, understand their scope and manage cleanup in a custom integration.

Pause appearance while another resource owns the player model

The appearance pause exports run on the client. They let a custom integration pause Murphy appearance application while it temporarily uses another player model.

The public release notes introduce this integration in Creator 1.35.13, alongside Clothing 3.37.1 and Barber 1.18.11. Use versions that implement the pause checks in every installed appearance resource.

Exports

Export Argument Result
SetAppearancePaused(paused) Boolean; pass true to pause or false to resume. Sets the local appearance-pause state; no return value is documented.
IsAppearancePaused() None. Reports whether the local pause state is true.

Pause before the custom integration changes the model:

lua
exports.murphy_creator:SetAppearancePaused(true)

Read the current state:

lua
local paused = exports.murphy_creator:IsAppearancePaused()

When the integration is ready to return control to the normal appearance flow:

lua
exports.murphy_creator:SetAppearancePaused(false)

Resuming clears the pause flag. It does not itself call an appearance reload. If the integration requires an immediate reload, the existing client event is:

lua
TriggerEvent("murphy_creator:loadskin")

These are client-side integration excerpts, not a complete transformation resource.

Scope and cleanup

The exports use LocalPlayer.state.murphy_appearance_paused. The setter writes a local, non-replicated state value. This controls the local player's appearance flow, not all peds on the server.

The custom integration must handle completion, cancellation, and failure so the player is not left paused. Do not rely on a resource restart as an automatic cleanup guarantee; verify the lifecycle of the installed resources.

Verify the integration

  1. Check that Creator is running before calling its exports.
  2. Pause, perform the custom model operation, and verify that the intended model remains active.
  3. Resume and run the appropriate normal appearance flow.
  4. Test cancellation and resource failure as separate cases.
  5. Check Clothing and Barber when those integrations are installed.

This guide does not establish that every third-party transformation script follows the pause flag. Check the public 1.35.13 notes on the Creator product page and the corresponding installed resource versions.

Last updated: September 9, 2026