Common Issues

Common setup questions

The board is present but I cannot select it

Check that the murphy_interact dependency and its RedM-compatible ox_lib have started successfully. Use the interaction key from your installed configuration. Place a test board with space in front of it: support identified a board placed too close to a wall as a possible obstacle to selecting the interaction.

If the server also reports an adapter or character-identifier error, capture that first error separately. A working prop does not prove the callback that supplies jobs is working. See Installation and Callbacks.

An accepted job returns after reconnecting

Job persistence is intended behavior, as confirmed by support. Reconnecting is not a documented cancellation or reset mechanism. Distinguish a resumed job from an unwanted new reward or duplicate assignment, and report the exact steps if the latter occurs. Do not clear player progression tables to disable persistence.

Can I create a new mission without defining its logic?

Use Create a Job - Beginner Guide, then the Advanced Guide for custom behavior. Start from one working example and change one part at a time. Features found in a different development build are not automatically part of the published Job Board package.

Another resource breaks board interactions

Record whether the issue starts when that resource is enabled. Compare its use of murphy_interact with the board integration in an isolated test setup. A report about a custom bridge did not establish a confirmed fix; do not remove every interaction globally or change shared identifiers to hide the collision.

Investigate a Job Board issue

The store’s public 1.0.0 entry does not include detailed fixes. No release-specific repair is established here. Use these checks to collect a reproducible case.

1. Record the installed plugin and framework versions.
2. Identify whether the problem is creating a job, displaying a board, choosing a job, or calling a custom callback.
3. Compare one affected job with the Beginner Guide.
4. Record the first client and server error, not only the later symptoms.
5. If an external interface is involved, check its arguments and execution context against Callbacks.

Do not delete job or player records as a generic reset.

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