Skip to content

setVehiclePhysicalProofs

Client-side

Available in Neon, not standard MTA

Sets and persists GTA's five independent physical-proof flags on a vehicle.

Syntax

bool setVehiclePhysicalProofs(vehicle theVehicle, bool bullet, bool fire, bool explosion, bool collision, bool melee)

GTA task mapping

NATIVE GTA BEHAVIOR 02AC
No CTask is created

SCM equivalent: SET_CAR_PROOFS

This does not create a CTask. Neon writes GTA's bullet, fire, explosion, collision, and melee proof bits independently instead of using MTA's all-or-nothing damage-proof abstraction.

Arguments

theVehiclevehicle

Vehicle whose local native proof tuple should change.

bulletbool

Bullet-proof flag.

firebool

Fire-proof flag.

explosionbool

Explosion-proof flag.

collisionbool

Collision-proof flag.

meleebool

Melee-weapon-proof flag.

Returns

true when a valid vehicle accepted the complete tuple; invalid arguments or an invalid element fail.

Ownership and lifecycle

Door-lock, tyre-burst, physical-proof, and load-collision policies live on the MTA vehicle, apply immediately when its GTA instance is streamed, and are reapplied after local native recreation. They are client-local, last-writer-wins policies rather than resource-owned leases.

Important behavior
  • The complete tuple survives stream-out and native vehicle recreation on this client.
  • There is no getter or automatic resource-stop restoration. Pass five false values to clear every proof bit when the scene ends.

Example

-- Make a mission vehicle fireproof without changing its other proof flags.
setVehiclePhysicalProofs(missionVehicle, false, true, false, false, false)

Where this comes from

RELATED NEON APIS

Continue exploring

Read the system guide →