Trip3 Docs
FiveM

Trip3 Rumors

A lightweight ambient RP system that lets players gather and spread street rumors through NPC interactions.

Ambient, immersive NPC rumor system for FiveM — players can ask nearby pedestrians what they've heard, or share a rumor of their own for other players to discover later.

Overview

Players can walk up to eligible NPCs and either ask around for a rumor or, on certain NPCs, share a rumor of their own. Shared rumors are stored and can later be heard by other players, letting the community build its own evolving pool of gossip alongside the base rumors you write. Everything is tunable from config.lua — no code edits required.

Features

  • Category-based, weighted random rumor selection (fully customizable categories)
  • Player-submitted rumors, with age/count limits so the pool stays fresh
  • Configurable NPC "rejection" chance for a more natural feel
  • Built-in profanity filter for player-submitted text
  • Adjustable ambient NPC density (how many NPCs are interaction-eligible)
  • One-time-per-NPC interaction to prevent farming
  • Admin commands for stats, manual rumor management, and cooldown resets
  • Optional UI provider toggle (ox_lib by default)

Dependencies

  • ox_target
  • ox_lib
  • oxmysql

No manual database setup required — the resource creates its own table on first start.

Installation

For general installation steps that apply to every resource, see Installing a Purchase.

  1. Drop the trip3_rumors folder into your server's resources directory.
  2. Make sure ox_target, ox_lib, and oxmysql are installed and started first.
  3. Add to your server.cfg, after those dependencies:
ensure trip3_rumors
  1. Restart the resource and confirm the console shows a "storage ready" message.

Ambient NPCs will start offering the "Ask Around" interaction immediately based on your configured density settings.

Configuration

All configuration lives in config.lua, which is excluded from escrow — fully readable and editable after purchase.

SettingDescription
Config.CooldownSeconds a player must wait between rumor interactions.
Config.InteractDistanceInteraction distance for the NPC prompt.
Config.HearRejection.ChanceOdds an NPC brushes the player off instead of sharing anything.
Config.PlayerRumorsControls the "Share Rumor" feature — submission cooldown, min/max length, storage caps, profanity filter, and all of the notification text used throughout the flow.
Config.PedDensityMode Config.PedSelectionMethodHow many ambient NPCs are eligible for interaction, and how that's decided (random chance vs. every Nth NPC).
Config.RumorCategoriesYour list of categories — each with a name, weight, and its own rumor pool. Add, remove, or reweight freely.

Every player-facing notification title and message is also editable as plain text in config.lua.

Admin Commands

Require the trip3_rumors.admin ACE permission (server console is always authorized). Disable the whole set with Config.AdminCommandsEnabled = false.

CommandDescription
/rumorhelpLists all admin commands.
/rumorstatsShows stored rumor counts, total and per category.
/rumorcategoriesLists configured category names.
/rumoradd <category> <text>Manually adds a rumor.
/rumorclear [category]Clears stored rumors, optionally scoped to one category.
/rumorpruneRuns the cleanup pass immediately.
/rumorcooldown [id|all|me]Clears interaction cooldowns.

Roadmap

Planned for future updates:

  • Optional category-specific cooldowns
  • Optional zone-restricted categories
  • Optional weighted rumor tuning by zone and/or time of day

On this page