gameplay.json
Top-level gameplay rules that shape salary timing, disconnect cleanup, spawn defaults, survival systems, and base movement.
Overview
Sections in this file include:
- Salary interval and job salary timing.
- Player-owned setup cleanup after a disconnect.
- Spawn defaults such as default job id.
- Hunger and survival rules.
- Death behavior.
- AFK behavior.
- Jail behavior.
- RP name validation.
- Movement speed values.
Player-owned setups after disconnect
ownedObjects.disconnectGraceSeconds controls how long LitheraRP keeps eligible player-owned objects after their owner disconnects. The default is 60 seconds and the accepted range is 0 to 3600.
| Field | Type | Default | Description |
|---|---|---|---|
| ownedObjects.disconnectGraceSeconds | number | 60 | Seconds before eligible owned objects are removed after disconnect. 0 removes them on the next host update. Accepted range: 0 to 3600. |
This covers objects using LitheraRP ownership, including printers, weed pots and grow lights, meth equipment, shop-spawned pickups, Toolgun props, duplicator pastes, compatible addon objects, and runtime vehicles created with despawnWithOwner: true. Detached wheels, doors, and hatches belonging to those vehicles are removed with the chassis. Map objects and objects tagged world or player are not part of this cleanup.
- If the player rejoins before the deadline, cleanup is cancelled and the retained setup is linked to the new connection.
- Taxis use their own job lifecycle and are returned immediately.
- Changing job, being demoted, or dying does not start the disconnect timer.
- AFK cleanup is separate and can remove owned objects immediately when
afk.removeOwnedObjectsis enabled.
After litherarp.gameplay_reload, the new grace period also applies to disconnects already waiting. Lowering it can make an existing timer expire on the next host update; increasing it extends the deadline.
Movement values
Movement-related values must be consumed by live controller code to have an effect. Base walk and sprint speed are applied during player updates, but always test feel in game after changing them.
Reload
Use litherarp.gameplay_reload from the server console after editing the file outside the /config workspace.