Bridge is in a state of development and is not stable.
RAGE:MP to FiveM Bridge
Plugins

vehicle-sync

vehicle-sync

vehicle-sync keeps cosmetic vehicle state consistent for late joiners and players who stream a vehicle in later.

Side

Server and client

State owner

Server-authoritative

Manual setup

No API calls required

Disable name

vehicle-sync

Why it exists

Many cosmetic vehicle changes are applied per client. Without replaying state, a player who streams the vehicle later may see default colours, neon, mods, livery, extras, or window tint.

Use vehicle setters normally

server/vehicles.js
const veh = mp.vehicles.new('adder', new mp.Vector3(-45.4, -1097.1, 26.4));

veh.setColorRGB(0, 200, 255, 10, 10, 10);
veh.setNeonColor(0, 150, 255);
veh.neonEnabled = true;
server/vehicles.js
veh.setMod(11, 3); // engine
veh.setMod(12, 2); // brakes
veh.setMod(18, 0); // turbo
veh.livery = 1;
what-happens.js
// 1. Server stores the authoritative cosmetic state on the VehicleMp entity.
// 2. A client streams the vehicle in later.
// 3. The client requests a snapshot.
// 4. The plugin repaints the vehicle to match server state.

What it syncs

Common replicated cosmetic state includes vehicle colour, neon, mods, livery, window tint, extras, and similar appearance values.

Create the vehicle on the server.

Set cosmetic properties through normal VehicleMp APIs.

Let vehicle-sync replay snapshots as clients stream vehicles in.

Disable it

fxmanifest.lua
disable_plugin 'vehicle-sync'

On this page