RedM documentation

Murphy's Rumors

Getting Started

Configuration

Rumors: Find the configuration file, use the supported option names and understand their units before changing settings.

Configuration file

Edit the existing murphy_rumors/cfg.lua file. Keep a backup and change individual settings; do not replace the complete Config table with an excerpt.

Timing and price

Setting Meaning Unit
Config.RumorPrice Amount charged for sharing a rumor through the normal interaction. Framework money amount
Config.DelayBeforeDisplay Delay before the accepted rumor is inserted for distribution. Seconds
Config.RefreshRumors Delay between client requests for the active rumor list. Milliseconds
Config.Rumorstime How long a stored rumor remains eligible for distribution, measured from its stored date. Minutes
Config.DisplayDistance Distance used when looking for nearby NPCs and displaying rumor text. Game world distance

Example timing values, not a full configuration or a promise of release defaults:

cfg.lua
Config.DelayBeforeDisplay = 20
Config.RefreshRumors = 10000
Config.Rumorstime = 20

Here the initial delay is 20 seconds, clients request updates every 10 seconds, and stored rumors remain eligible for 20 minutes. Distribution also depends on a client refresh and nearby eligible NPCs, so the initial delay is not an exact on-screen delivery time.

Sharing locations

Config.ShareRumorSpot contains the configured sharing locations. Preserve the structure of an existing entry: its position key, npc, npccoords, and npcheading. Use coordinates and models appropriate to your map. Changing an interaction location and changing the NPC spawn position are separate edits.

Forbidden words, from 1.2.0

The public 1.2.0 release adds Config.BlacklistedWords. Matching ignores letter case and searches for a substring, not a whole word. A matching rumor is rejected before it is stored or charged. An empty list disables this filter.

cfg.lua
Config.BlacklistedWords = {
    "exampleblockedterm",
}

Use a harmless test term first. Config.NotificationBlacklisted is the rejection message; Config.NotificationRumors is the normal sharing notification.

Replacing older examples

The previous Config.MaxRumors, Config.RumorLifetime, Config.RefreshInterval, Config.DisplayStyle, Config.TextColor, Config.IconEnabled, and Config.AllowedSources examples were not found in the resource inspected for this correction. They are not an established configuration reference. Do not invent a mapping between those names and the timing settings above.

Check the change

  1. Use the configuration shipped with your installed version and back it up.
  2. Change one setting.
  3. Restart the resource in a test or maintenance session.
  4. Share a harmless rumor through a configured interaction point.
  5. Check acceptance, the delay, nearby NPC display, and eventual expiry.

The blacklist behavior is documented in the Versions tab of the Rumors product page, release 1.2.0. Other reference entries were checked against the configuration and its consumers; no in-game test is claimed here.

Last updated: September 9, 2026