RedM documentation

Murphy's Safe

Support

Common Issues

Diagnose Safe placement, code menus, inventory integration, persistence and logging issues.


Placement, inventory and access

A safe item appears but the code menu never opens

Check that the inventory item name matches the safe configuration and that the downloaded version's dependencies are started. Support specifically identified murphy_menu as necessary for the code-entry menu and uiprompt for the prompt workflow. Having an item in the inventory only proves the item is registered.

Test with one safe on a test character. Record whether you can use the item, position the preview, confirm placement, enter a code and reopen the placed safe. These are separate steps; report the first one that fails. See Installation.

Does every player need the admin safecode permission to place a safe?

The administrative code-inspection command and ordinary safe placement are different actions. Do not give everyone an administrator group as a placement fix. Follow Interactions for players and Admin Commands for staff.

RSG creates a prop but no usable persistent safe

Historical support threads covered both missing dependencies and RSG inventory/database compatibility bugs. Check the actual RSG inventory version, the complete Safe update and the first SQL error. Use the official 1.3.0 release guidance below where applicable. Deleting and re-creating the database did not solve one reported case; keep existing safe and storage records intact.

Safe actions work, but Discord logs are missing

When your version uses murphy_discordlogs, the name in Safe's Config.DiscordLogs must exist in the logging resource's Config.Logs table. Support confirmed a mismatch where Safe used safe and only stash had been configured. Add the intended named destination privately, restart the logging resource and test one action. Never place the webhook URL in a public screenshot or documentation example.

Known issues by release

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

VORP safes do not work and GetCharIdentifier is unavailable

Release reference: 1.3.2. The 1.3.2 notes identify a VORP adapter initialization failure involving the former inventory API. The update changes core resolution and inventory calls. Inspect the first server-console error and the installed adapter version rather than defining a replacement helper to suppress the error.

A new safe fails to initialize its database on RSG

Release reference: 1.3.0. The 1.3.0 notes introduce automatic SQL initialization and an RSG safe-creation SQL fix. Check whether the installed version includes that change and inspect the database error. Do not drop existing safe tables to recreate them.

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


Last updated: September 10, 2026