CREATE_VEHICLE_SERVER_SETTER · RedM

Property	Value
Native Name	`CREATE_VEHICLE_SERVER_SETTER`
Hash	`0x6AE51D4B`
Return Type	`Vehicle`
API Set	`server`
Parameters	`modelHash` (Hash), `type` (char*), `x` (float), `y` (float), `z` (float), `heading` (float)

Description: Equivalent to CREATE_VEHICLE, but it uses 'server setter' logic (like the former CREATE_AUTOMOBILE) as a workaround for reliability concerns regarding entity creation RPC.

Unlike CREATE_AUTOMOBILE, this supports other vehicle types as well.

Parameters

modelHash (Hash) — The model of vehicle to spawn.
type (char*) — The appropriate vehicle type for the model info. Can be one of automobile, bike, boat, heli, plane, submarine, trailer, and (potentially), train. This should be the same type as the type field in vehicles.meta.
x (float) — Spawn coordinate X component.
y (float) — Spawn coordinate Y component.
z (float) — Spawn coordinate Z component.
heading (float) — Heading to face towards, in degrees.

Examples

local heli = CreateVehicleServerSetter(`seasparrow`, 'heli', GetEntityCoords(GetPlayerPed(GetPlayers()[1])) + vector3(0, 0, 15), 0.0)
print(GetEntityCoords(heli)) -- should return correct coordinates

Before you call

Entity-creating native — the returned handle can come back 0, or as an exists-but-broken entity (e.g. an invisible ped), on failure, so validate it before use (check ~= 0 and/or DoesEntityExist); note CREATE_PED returns 0 silently when called with the wrong arg shape. (see findings: learning:44, learning:84 — fetch via get_document)

Spawned entities consume finite client-side pool slots shared with the game world and every other resource — pool exhaustion makes CREATE_* return 0 or crashes the client with a pool-full error. Budget spawns and delete what you create; a server owner can only raise a pool with `increase_pool_size` up to the Cfx-published cap — get_document({ path: "guides/pool_size_limits.md" }) lists the RedM pools and their limits. (see findings: learning:123 — fetch via get_document)