Vehicle-life controls add driver and passenger presentation beyond the ownership core. This guide remains a draft while keybinds, driver swaps, helmets, windows, doors, locks, and rematerialization resets await real-client verification.
Understand control roles
Drivers control the engine, supported lights, indicators, all windows, and their own door. Passengers control their own supported window and door and can toggle their own seatbelt or helmet state.
On foot, a character can operate the nearest supported unlocked door without a key. Lock control requires vehicle access, while trunk and hood interaction also follow their current access, lock, position, and model rules. Do not assume every body supports every panel.
Use indicators and keybinds
Use /blinkers or the corresponding action under /v for left, right, hazards, or off. While driving, Y and N can toggle left and right when the character’s blinker keybind preference is enabled.
The preference persists per character. Active indicator state is runtime presentation, can remain through a driver swap, and does not require the engine.
Use seatbelts or helmets
Use /seatbelt in an occupied seat. Supported bikes present the same roleplay state as a helmet.
This is currently cosmetic roleplay state and does not provide crash protection. It clears when leaving the vehicle or entering an incompatible character state.
Control windows and doors
Drivers can toggle all supported windows or select one. Passengers may control only the window beside their seat. The door action under /v controls the occupant’s own door or the nearest supported door while on foot.
A refusal is authoritative; unsupported vehicle bodies do not pretend a control worked.
Use locks, trunk, storage, and hood
Use /lock near an authorized vehicle. Lock state is durable and parking does not silently secure an unlocked vehicle. A lock change can occasionally report that it could not be applied just now; the lock is left unchanged, so repeat the action.
Open the physical trunk from the rear before using /storage, and close it explicitly afterward. Closing the storage dialog does not currently close the physical trunk despite its secondary-button wording. Use /hood at the front independently.
Understand persistence
Saved location, condition, fuel, colors, mileage, and lock state are durable through established persistence. Engine, lights, indicators, windows, doors, trunk, and hood are runtime presentation and reset when the vehicle rematerializes.
Recover from controls that fail
- Wrong seat or unsupported panel: use the specific refusal and correct the position.
- Locked or no access: obtain proper access and unlock before panel or storage use.
- A lock change is refused as temporary: nothing changed; wait a moment and use the lock action again.
- Keybind does nothing: review the persistent blinker-key setting and current driver state.
- Trunk remains open after closing storage: close the physical trunk explicitly.
- State after parking or retrieval is unclear: check
/v,/keys, and lock feedback before another mutation.
Exact control ranges, model capabilities, key constants, and internal reset hooks are intentionally omitted.