Installation

Prepare the resource

Download the complete murphy_barber resource from your customer assets. Check the installed version in fxmanifest.lua. Back up your working configuration and database before updating. Keep the resource folder name unchanged and place the manifest directly inside it, rather than nesting the extracted resource inside an extra download folder.

Dependencies and configuration

Start the framework and inventory, oxmysql, then the resources needed by your chosen interaction mode. The murphy_interact mode requires a RedM-compatible ox_lib followed by murphy_interact. Start Barber afterwards.

Set Config.framework to the exact value supplied for your framework. Set Config.murphy_creator according to whether Creator is installed; it is an optional integration, not a reason to buy Creator to make Barber work. Configure Config.NativePrompt, Config.MenuCommand, shops and prices in the same file.

Register the item named by Config.OverlayItem in your inventory if you use makeup items. Check the SQL schema supplied with your release, preserve existing appearance records, and resolve any startup error before testing.

Start and verify

After the dependencies and configuration in shared/config.lua are ready, add the resource line:

ensure murphy_barber

This is the resource's start line, not a complete server configuration. Check the first client/server error, then test one normal action with a test character. Verify the result after reconnecting where data should persist. Use Common Issues for the relevant symptom.

When merging an update, retain your settings while adding new required keys. Include UI, translation and adapter files listed in its release notes; changing only fxmanifest.lua does not update the implementation.