RedM documentation
Murphy's Rumors
Reference
Events
Rumors: Follow the existing client/server rumor events and distinguish internal distribution from a supported external API.
Existing event flow
These events describe the resource's existing rumor distribution. They are not a new server-side API for creating, charging, or moderating rumors.
| Event | Receiver | Existing purpose |
|---|---|---|
dust_rumors:server:askRumor |
Server | A client asks for the active rumor list. |
dust_rumors:client:getRumor |
Client | The server returns a rumor table to that client. |
rumors:DrawText3D |
Client | The resource draws a rumor for an eligible nearby NPC. |
The event names retain their dust_rumors prefix even though the resource is named murphy_rumors. Do not rename one side of an event connection.
Request and response
The resource's client periodically requests rumors after waiting Config.RefreshRumors milliseconds. This is the existing client-to-server call:
The corresponding dust_rumors:client:getRumor handler receives the list. The drawing flow then uses nearby NPCs and the display conditions in the client resource.
Do not register another drawing handler from this reference or paste a second polling thread into the resource. Duplicate handlers can perform the same work more than once.
Boundaries
Sending an event is not a substitute for the resource's sharing workflow, payment check, or blacklist. This page does not document a supported external rumor-creation export.
See Configuration for timing units and Rumors system for a testable player workflow.
Last updated: September 9, 2026