Installation

Before installing

Murphy's Creator is a RedM resource. The public product overview lists VORP, RSG Core, and RedEM:RP 2023; its 1.41.1 release notes also announce QBR. You need the resource files for your purchase, a working supported framework, and the database integration required by the installed resource.

Record the Creator version in fxmanifest.lua and your framework version. The store's public release list was at 1.47.6 on 9 September 2026. A version label alone does not show which files have actually been updated on your server.

Prepare the resource

1. Back up your working server configuration and database before adding or replacing an appearance resource.
2. Extract the downloaded murphy_creator folder into your server's resources directory. Keep its manifest, Lua files, interface, and assets together.
3. Open murphy_creator/shared/config.lua and edit the existing settings.
4. Select your framework using the exact value in Framework support.
5. Configure the language and installed Clothing integration using Configuration.

Example settings for a VORP server with Clothing installed:

Config.framework = 'vorp'
Config.murphy_clothing = true
Config.LoadSkinCommand = "mc"
Config.Locale = "en"
Config.Debug = false
Config.DevMode = false

This is an excerpt. Do not replace the complete configuration with it.

Database setup

Creator uses oxmysql; its manifest loads @oxmysql/lib/MySQL.lua. Make sure the database connection works before starting Creator.

Use the SQL files supplied with your installed release. The resource layout reviewed for this guide contains:

Select the framework-appropriate files from your archive. Review the statements against the existing schema before importing. If your archive has different filenames or instructions, resolve that version difference before applying SQL.

The earlier generic instruction to import murphy_barber.sql did not match these filenames. Do not assume that every Creator table is created automatically, or import both framework variants as a troubleshooting attempt.

Connect the framework's character selection

Creator must be opened at the appropriate point in the framework's character-loading flow. These integration entry points are different contexts:

The existing framework determines where that handoff belongs. This guide does not provide a universal replacement for vorp:playerSpawn, rsg-appearance's ApplySkin, or a framework file at a fixed line number. Compare integration instructions with the exact core version before editing those functions. If they differ, request a version-specific integration from support.

In particular, preserve the framework's identity, routing, and character-loading logic. Do not copy a full replacement from another framework or release.

Start in the right order

Start the database connector and your framework before Creator. Install and start the resources required by your chosen integrations. Add Creator after those dependencies in server.cfg:

ensure murphy_creator

This line is an addition to the server configuration, not a complete dependency list. Keep the resource names used by your installed framework.

First verification

1. Start the server and resolve the first dependency, Lua, or database error.
2. Connect with a test character and confirm that character selection opens.
3. Create a test character and check appearance, identity, and entry into the world.
4. Reconnect and verify that the saved character and appearance return.
5. If using Barber or Clothing, test those integrations on the same character.

/mc, when configured through Config.LoadSkinCommand, reloads appearance. It is not a test that the new-character entry flow works.

Next steps

• Character creator: illustrated interface walkthrough.
• CharSelect, decor and cameras: scene and slot configuration.
• Known issues: fixes identified by public release notes.
• Troubleshooting: information to collect when a step fails.

For updates, merge your custom configuration with the delivered files and follow the Versions tab on the product page. Keep backups; a troubleshooting symptom is not a reason to delete existing character data.