Common Issues

First checks

Rumors does not start on VORP

Check the framework value in cfg.lua. The VORP adapter uses the exact string "vorp"; a display name such as "VORP Core" is not interchangeable. This configuration mismatch was identified in support. Resolve the first startup error and check the downloaded resource's dependencies using Installation.

A rumor is accepted but not immediately visible everywhere

The system uses configured locations, distances and timing. Compare the expected result with Rumors System and Configuration. Test a harmless message at a configured location and distinguish a delayed display from a rejected submission. Do not lower every timer or disable validation before identifying the failing step.

Known issues by release

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

A rumor is rejected because it contains a forbidden term

Release reference: 1.2.0. The filter added in 1.2.0 matches substrings without regard to letter case. A listed term may therefore also match part of a longer word. The documented rejection occurs before saving and charging. Review Config.BlacklistedWords in cfg.lua and test with a harmless term. An empty list disables this filter.

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