CREATE_VEHICLE · RedM · Native Atlas

Property	Value
Native Name	`CREATE_VEHICLE`
Hash	`0xDD75460A`
Return Type	`Entity`
API Set	`server`
Parameters	`modelHash` (Hash), `x` (float), `y` (float), `z` (float), `heading` (float), `isNetwork` (BOOL), `netMissionEntity` (BOOL)

Description: Creates a vehicle with the specified model at the specified position. This vehicle will initially be owned by the creating script as a mission entity, and the model should be loaded already (e.g. using REQUEST_MODEL).

NativeDB Added Parameter 8: BOOL p7

This is the server-side RPC native equivalent of the client native CREATE_VEHICLE.

Parameters

modelHash (Hash) — The model of vehicle to spawn.
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.
isNetwork (BOOL) — Whether to create a network object for the vehicle. If false, the vehicle exists only locally.
netMissionEntity (BOOL) — Whether to register the vehicle as pinned to the script host in the R* network model.

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)