Skip to content

Synchronization

Revo sends networked entity state to the clients observing that entity. Streaming determines when a client receives it, and ownership determines which client simulates it.

Built-in synchronization covers these areas:

State Examples
Players and NPCs Position, movement, aiming, weapons, ragdolls and parachutes.
Vehicles Position, velocity, controls, damage, appearance and vehicle occupancy.
Objects Position, rotation, velocity and physics state.
Server entity properties Changes made through the server API, such as model, visibility, health and ped appearance.

Client-only entities, cameras and WebViews remain local. A native call is not automatically executed on other clients. Its effects replicate only when they are part of the synchronized state. For scripted NPC tasks, see Restoring NPC behavior.

Use synced metadata on the server for custom state attached to an object, such as a vehicle’s fuel level or a player’s display name. Clients in the object’s audience receive its current values and subsequent changes. Player metadata also goes to that player.

Metadata does not apply gameplay behavior by itself. Storing a fuel level of zero still requires your script to stop the engine if that is how your game mode works.

Use events for messages such as interaction requests or opening a menu. Use requests when the caller needs a response. These messages use reliable delivery while connected.

When an entity enters a client’s stream, the client receives its current entity state and metadata. Earlier script messages are not replayed. Use synchronized metadata for custom values needed by late joiners or returning observers, or have the client request their current values from the server.

A server API change is applied to server state and distributed to the affected clients. Older simulation updates cannot undo it. The change still takes time to reach each client, and a model change can require additional loading.

Normal movement comes from the simulation owner. Repeated server position assignments keep replacing that movement and can reset ped tasks. Use position assignments for deliberate repositioning, such as a teleport.

Direct native changes on a remote entity can be overwritten by incoming state. Other clients also smooth movement between received updates, so their rendered positions can differ slightly at the same moment.

Both settings are at the top level of the server configuration and use milliseconds.

Setting Effect Default
tick_interval Delay between server main-loop iterations. Work done in an iteration adds to its actual duration. 10
sync_interval Minimum interval between client synchronization passes. Accepts 25 to 45, or "auto". 25

At 25 ms, the nominal sync cadence is 40 times per second. Actual delivery depends on client frame rate, server load, transport capacity and which entities have changed. Stationary entities can send less often, and a packet can contain updates for several entities.

Increasing sync_interval reduces update frequency. In "auto" mode it starts at 25 ms, increases under sustained load up to 45 ms and decreases again after recovery. Script messages and server property changes use separate delivery paths from periodic simulation updates.