Armed vehicle spawn catalogue

Spawn weapon-equipped vehicles with the Vehicle.* records listed below. The catalogue covers Cyberpunk 2077 2.31 / build 23100, including Phantom Liberty.

The database declares weapon mounts on 172 vehicle records. This is not a count of supported armed vehicles: inherited lists may include unattached weapons. Quest, transport, broken and hologram variants can require additional assets or logic.

The spawn ID is the full Vehicle.* string, not an Items.* weapon record, a mount/slot ID, or the numeric network vehicle ID returned after creation. Use Network vehicles for the complete API and Game data reference for other model catalogues.

Armed model examples#

The records below provide native mounted weapons. Model appearance and attachments can change the available armament. See weapon replication and limitations before using a model in a gamemode.

Do not substitute Vehicle.v_sport1_herrera_outlaw_player for the armed Heist variant: it is not in this mounted-weapon catalogue. The same caution applies to the ordinary Shion, Type-66, Galena and Colby: use the exact variant ID, not just the family name or a freeroam alias.

Spawn a network vehicle#

Client HUDs can inspect a live vehicle through the vehicle weapon Lua API, including actual attached weapons, selection and available native ammunition counters.

With the system resource open77_vehicles running, enter this in the server console (replace 1 with the connected player's ID):

vehicle.create.player 1 Vehicle.v_militech_basilisk
vehicle.create.player 1 Vehicle.v_sport1_herrera_outlaw_heist_player
vehicle.create.player 1 Vehicle.v_sport2_mizutani_shion_nomad_player_missiles

Run one line for the vehicle you want. These commands create beside the player; they do not automatically seat the player. From chat, prefix the command with / and grant its exact command.vehicle.create.player ACL permission. Spawning is restricted, not an unrestricted player command.

A server-side Lua resource uses the same spawn ID:

-- open77.lua
permissions { "world.vehicles" }

-- server/main.lua; choose clear ground and the intended routing bucket.
local vehicleId, reason = Open77.vehicles.create({
    record = "Vehicle.v_militech_basilisk",
    position = { x = 405.0, y = -2415.0, z = 183.0 },
    yaw = 0.0,
    bucket = 0,
})
assert(vehicleId, reason)

Player variants at a glance#

These 18 _player variants declare weapon mounts. Except for the armed examples above, treat these records as experimental: a declared mount does not establish that its weapon can be deployed. The Basilisk is listed separately because its ID does not contain _player.

Complete record inventory#

All 172 unique source records are listed below, including inherited and special-purpose variants. Declared describes the TweakDB mount list, not a guarantee of functional armament. Refer to the armed model examples and inspect attached weapons with the Lua API.

Basilisk / Panzer — cannon, missiles and countermeasures (7)#

Four declared mounts: cannon, homing missile launcher, left and right countermeasure launchers.

Outlaw Heist — dedicated machine guns (2)#

Two declared Outlaw-specific power-weapon mounts: left and right.

Machine-gun mount records (27)#

Two declared standard power-weapon mounts: left A and right A. Actual attachment still depends on the model's configuration.

Shared machine-gun and missile mount records (136)#

Nine possible mounts: power weapons left/right A, B and C, plus missile launchers A, B and C. This is a shared list of alternatives, NOT nine weapons fitted to every vehicle. Entries such as Caliburn, Centurion and quest variants must not be treated as armed solely because they inherit this list.

Weapon and attachment IDs#

These are not vehicle spawn IDs. They identify the weapon item and its attachment slot when inspecting a vehicle or maintaining the synchronization adapter.

Sources and maintenance#

Machine-readable catalogue#

Download the website JSON catalogue for tooling and agents. It is the same extracted catalogue used by the server: gameBuild, a mounts array of 15 definitions and a vehicles object mapping each full spawn record to an ordered array of mount IDs. Its 172 keys are declarations, not 172 verified spawn/firing tests. Match each vehicle mount ID to mount.mountId; the array position plus one is the stable Lua mount index for that model.

For example, the Panzer cannon declares cycleTime=0.3; its homing launcher declares cycleTime=2 but emits multiple missiles in a salvo. Countermeasure mounts can declare one whole-burst projectile while emitting multiple projectiles. Do not infer network admission or ammunition from a single catalogue field; the multiplayer guide separates native behavior from the server's policy.

Provenance and regeneration#

• server/src/Open77.Server.Core/Vehicles/vehicle-weapons-2.31.json: 172 vehicle records and 15 mount definitions, extracted from the installed 2.31 base and expansion TweakDB data.
• scripts/research/vehicle-weapons-catalog/Program.cs: model/mount/item/slot bindings and native salvo metadata; it does not inspect each appearance's mounted entities.
• docs/research/vehicle-weapons-and-combat.md: live observations, validation boundaries and remaining work.
• docs/vehicle-models.md: broader model/template inventory, including unarmed vehicles.

After a game update, regenerate the source catalogue and reconcile this inventory. Promote a record to Mounted armament only after spawning that exact variant and observing its real attached weapon fire. Archive-dependent vehicles also require the corresponding game content to be installed.