Riven Scene Dynamics

Overview

Riven Scene Dynamics is a scene management resource for roleplay servers. The reviewed package includes perimeter tape, portable posts, placement of scene equipment, scene records, responder assignments, evidence markers and records, a tactical board, and scene vehicle/tow tracking.

Naming note: The 0.25.5 notes describe a product rebrand from Scene Control to Scene Dynamics. Some internal code identifiers intentionally retain riven:scenecontrol:* for compatibility. Use the storefront name that matches the actual downloadable product.

Access model

The README for the reviewed 0.25.6 archive explicitly labels the build open access: no department, role, or rank gate is required for the documented scene tools. The server still validates interaction data.

Installation

1. Extract the resource and preserve the folder Riven_Scene_Dynamics.
2. Confirm its fxmanifest.lua, shared/config.lua, client/, server/, stream/, and ui/ components are present.
3. Add the resource to server.cfg:

ensure Riven_Scene_Dynamics

4. Review tape, evidence, equipment, trunk, scene access, and persistence configuration.
5. Test placement, cleanup, and state synchronization with another connected player.

Main menu

Tape controls

During tape placement, the README lists E to confirm and Backspace to finish/cancel; arrow keys rotate where the active mode supports them. Available tape types are defined by the installed configuration.

Equipment and perimeters

The package documents portable posts and automatic perimeter creation:

/rivenscene post
/rivenscene post place
/rivenscene post remove
/rivenscene auto small
/rivenscene auto medium
/rivenscene auto large

Supported equipment commands include /rivenscene equip types, /rivenscene equip cone, /rivenscene equip barricade, /rivenscene equip flare, /rivenscene equip road_closed, /rivenscene equip arrow_left, /rivenscene equip arrow_right, /rivenscene equip scene_light, and /rivenscene equip remove.

Scene coordination

The README also documents scene assignment, scene command, scene clearance, role/job access lists within a scene, and command post placement. These are in-world scene rules, not proof of global restrictions on who can use the resource.

Evidence records

Evidence interactions are provided through /rivenevidence and the scene interface. The reviewed package documents placement, collection, record notes, photo references, and custody history for in-game evidence records. It can store an external image URL/reference, but the README explicitly states that an independent screenshot hosting service is not required for the core record system and is not supplied by the core resource.

Version 0.25.6 includes a ground-level drawn evidence-marker fallback when a compiled custom marker model is unavailable. The model source files in the archive are not equivalent to an already compiled GTA .ydr resource.

Scene vehicle tracking

The package includes /rivenvehicle commands for registering a nearby vehicle with a scene and recording scene-specific status, notes, and recovery activity. This is an in-game scene register; it should not be described as a real-world vehicle record system.

Vehicle trunk interaction

The reviewed README describes a trunk interface for collecting scene equipment from eligible vehicles. The /riventrunk command is listed, with eligibility and available equipment controlled by Config.Trunk.

Troubleshooting

F6 or scene menu does not open: Confirm the complete UI files exist and review client console errors.

Evidence marker appears as a drawn tent: This may be the intended fallback when the custom GTA prop is not compiled and streamed.

Equipment cannot be placed: Check distance rules, placement state, selected equipment type, and server console logs.

Expected staff restrictions do not apply: The reviewed 0.25.6 build is explicitly open access. Configure a different permission model only after implementing and validating it.