Getting Started

Before installing

You need access to your FiveM server's resource directory, server.cfg, and console or txAdmin interface. Keep a backup of the server configuration and any existing resource you intend to replace.

Confirm that the package has been fully extracted. A resource folder should contain its fxmanifest.lua at the top level of that resource, not inside an extra nested directory created by the ZIP extraction tool.

Most Riven resources covered here are designed for standalone or vMenu-based environments. That does not mean every resource has the same dependencies. Some require additional libraries or voice integrations. Always check the individual guide first.

Standard installation process

Stop the resource being replaced, or schedule maintenance if the server is in active use.
Download the authorized release through the applicable official distribution channel.
Extract the archive and locate the folder containing fxmanifest.lua.
Copy that complete folder into the server's resources/ directory. Category folders such as [riven] are optional organizational containers.
Install any declared dependencies and ensure they start before the Riven resource.
Add the resource's exact folder name to server.cfg with ensure.
Review its configuration file before enabling the product for regular players.
Start or restart the server and check the server console for errors.
Join the server and run the product-specific test listed in its guide.

The following is an illustrative structure. It is not a universal server.cfg that every customer should paste unchanged.

text

resources/
  [riven]/
    riven_hud/
      fxmanifest.lua
    Riven_Vehicle_HUD/
      fxmanifest.lua
    riven-impact-dynamics/
      fxmanifest.lua

cfg

ensure chat
ensure riven_hud
ensure Riven_Vehicle_HUD
ensure riven-impact-dynamics

Only enable resources you have installed. For medical and PA resources, install and start their dependencies first, as shown on those pages.

Understanding resource names

The ensure command uses the installed resource folder name, not the marketing product title. Do not replace hyphens with underscores or assume every resource begins with riven_. Examples from the reviewed packages:

Product	Resource folder
Riven HUD	`riven_hud`
Riven Vehicle HUD	`Riven_Vehicle_HUD`
Riven Impact Dynamics	`riven-impact-dynamics`
Riven PA Dynamics	`riven_pa_dynamics`
Riven Shield Dynamics	`riven_shield_dynamics`
Riven TraumaCore	`riven_trauma_core`
Riven Scene Dynamics	`Riven_Scene_Dynamics`
Riven Spike Dynamics	Not verified from a package

Confirm a successful installation

A resource being listed as started is the first check, not the final test. Check that its required dependencies are running, its interface or interaction opens, settings load, and its controls operate without colliding with another installed resource. Test with at least one additional player when the relevant feature involves synchronization or shared state.

Important compatibility rules

Run one authoritative fuel system. The reviewed Riven Vehicle HUD package includes fuel behavior; it should not be installed alongside another system that also controls the same tank state.
Avoid running multiple vehicle damage, seatbelt, or vehicle-failure controllers without reviewing their interactions. Riven Impact Dynamics specifically warns about competing resources.
Review overlapping keys, especially F7 and F9, before using the products together.
Do not assume every voice resource supports PA audio processing. Confirm the voice backend used by the server.

Troubleshooting Request support