Installation

Prepare the installed release

Use the murphy_rumors folder from your download. Check its version in fxmanifest.lua before merging configuration from another release. The store's public version history lists 1.2.0, including the forbidden-word filter.

Back up the working server configuration and database before installing or updating.

Check the actual dependencies

Open the downloaded resource's fxmanifest.lua. External script imports and dependency declarations identify which resources that archive expects.

For example, @oxmysql/lib/MySQL.lua requires oxmysql, and @ox_lib/init.lua requires ox_lib. Start the referenced resources before Rumors. Check the interaction dependency in your archive as well; it must match that version's interaction implementation.

Do not use the old mysql-async start-order example simply because it appeared in this article. It does not satisfy a manifest that imports @oxmysql/lib/MySQL.lua.

Resource and database setup

1. Extract the complete murphy_rumors resource into your server's resources directory.
2. Configure the framework in its existing cfg.lua, using the exact supported value from the downloaded configuration and adapter.
3. Configure the database connection through the database connector used by your server.
4. Review and apply the SQL schema supplied with that release. The inspected resource contains rumors.sql; check your archive before importing and preserve existing rumor data.
5. Start the dependencies, followed by the resource:

ensure murphy_rumors

This line is not a complete server configuration. The previous murphys_rumors spelling and Config.DatabaseName example are not the resource name and database-connection setting established here.

Configure and verify

Edit the existing cfg.lua using Configuration. Keep the complete table and change individual values.

1. Resolve the first startup error before testing interactions.
2. Visit one configured sharing location.
3. Share a harmless rumor and observe acceptance and nearby display after the configured delays.
4. On 1.2.0, test a harmless blacklist entry and verify that a rejection is not charged.

See Rumors system for the sequence and Known issues for the documented filter behavior. These are verification steps to run on your server, not a claim that every framework combination has been tested for this article.