Riven SystemsCompatibility
Compatibility and Integrations
Keybind conflicts
The reviewed packages include the following overlapping defaults:
| Key | Product 1 | Product 2 | Action required |
|---|---|---|---|
| F7 | PA Dynamics — PA menu | TraumaCore — medical panel | Rebind one of the controls before combined use |
| F9 | Riven HUD — chat display mode | Impact Dynamics — global debris cleanup | Rebind one of the controls before combined use |
| Left/Right arrows | Vehicle HUD — turn indicators | Scene Dynamics — rotation during placement | Test context-specific handling; remap if needed |
Shield Dynamics additionally uses Q, Left Ctrl, and H for equipped-shield controls. PA uses G, X, and J. Vehicle HUD uses Y and arrow keys. Any other script using the same key must be considered in deployment planning.
FiveM key mappings can normally be changed in Settings → Key Bindings → FiveM when they are registered through the supported key mapping interface. Settings defined only in a product config must be changed according to that product's implementation. Do not assume every keybind is changed from one universal Riven menu.
Voice and PA
Riven PA Dynamics depends on a working supported voice route. The reviewed package documents pma-voice as its primary integration but also describes native Mumble and custom adapter options. Server owners should identify the voice resource they actually use, verify the adapter, and test how PA audio is heard by a second player.
HUD and vehicle systems
Riven HUD handles on-foot/location, area-of-play, and chat presentation; Riven Vehicle HUD manages the vehicle dashboard and fuel in the reviewed packages. Riven Impact Dynamics has its own optional vehicle warning display. When all are enabled, keep each display in a separate visual area or disable redundant indicators using the appropriate configuration.
Do not install two systems that both take ownership of fuel, seatbelt state, parking brake state, or other vehicle conditions without an explicit tested integration.
Standalone is not dependency-free
A resource can be standalone with respect to ESX and QBCore while still requiring FiveM infrastructure or other libraries. The reviewed TraumaCore and PA builds require ox_lib and ox_target; the HUD build requires stock chat.
OneSync
Several Riven packages explicitly reference OneSync, and the PA manifest declares a /onesync runtime constraint. Multiplayer synchronization features should be tested with the server's actual OneSync configuration. Do not claim OneSync compatibility from single-player screenshots alone.