CREATE_AUTOMOBILE-like natives for other vehicle types

[Linden]

CreateAutoMoblie native does not sync landing gears

This native will always create a CNetObjAutomobile, which inherently can not sync data exclusive to other vehicle types like planes or helicopters. This is also why the native isn’t documented or even added by name: it’s not finished and if it could know what the vehicle type is, it’d just replace CREATE_VEHICLE, this unfinished version was added for testing purposes mostly. Making specific functions for each type was seen as undesirable at the time, but the server also doesn’t have any means …

Post above states making specific functions for each type (i.e. CREATE_PLANE, CREATE_TRAILER, etc.) was undesirable, but seems like the only reasonable option as far as I can tell.

I guess spawning incorrect types could lead to odd behaviour, but that seems better than the current case where you need to use CreateVehicle in most cases, which has been stated to be flawed and shouldn’t be used.

[nta]

@Linden

but seems like the only reasonable option as far as I can tell.

There was a todo item for a CREATE_VEHICLE_SERVER_SETTER call that’d take a string argument with a vehicle type, as a compromise until there’d be vehicle metadata parsing (see Vehicle metadata indexing on server · Issue #840 · citizenfx/fivem · GitHub for how that could work), and this one could then also be added to native-decls without risking misuse.

However, since each vehicle type has some different creation nodes as well, this is still a relatively complex task.

[Linden]

feat(gamestate/server): CREATE_VEHICLE_SERVER_SETTER command

Several types do seem to be missing, though they may function okay under existing types.

• AMPHIBIOUS_AUTOMOBILE (3)
• AMPHIBIOUS_QUADBIKE (1)
• BICYCLE (7)
• BLIMP (3)
• QUADBIKE (9)
• SUBMARINECAR (2)

Thanks for your time, this will be very useful.

[nta]

@Linden

Several types do seem to be missing, though they may function okay under existing types.

I guess these don’t have their own netObject type, so they’re related to their parent type:

@Linden

• AMPHIBIOUS_AUTOMOBILE (3)

Automobile.

@Linden

• AMPHIBIOUS_QUADBIKE (1)
• BICYCLE (7)

Bike, I believe.

@Linden

• QUADBIKE (9)

Also Bike.

@Linden

• BLIMP (3)

Heli.

@Linden

• SUBMARINECAR (2)

Again, Automobile, but maybe Submarine if that derives from Automobile.

I guess the documentation could do with a mapping table of vehicle types to network object types, then, yes, as I forgot there were derived types at all.

[Orel65]

A JSON file that translates models to types, generated with GetAllVehicleModels on b2699, using the server-sided native GetVehicleType.
https://pastebin.com/raw/uzUe667R

You can use this table like that:

local modelsToTypes = json.decode(--[[ Load the JSON file here, with LoadResourceFile or whatever ]])
function SpawnVehicleServerSetter(model, x, y, z, heading)
	local modelType = modelsToTypes[model]
	if not modelType then
		error("This model does not exist on the list")
	end
	CreateVehicleServerSetter(model, modelType, x, y, z, heading)
end

Note that some models do not appear in the table that GetAllVehicleModels returns, and as a result, it doesn’t appear in the JSON table: such as BMX, etc… (which is a different problem)