EquipParameters

This page documents the weapon parameter tables inside EquipParameters.lua. When the game equips a weapon it resolves the equip ID to a weapon ID, reads that weapon’s part IDs, follows each part ID into its parameter buffer, and folds everything into a single GunInfo struct that gameplay reads from. All stats a weapon has - fire rate, spread, damage, range, ammo, sounds - live in these tables.

All addresses on this page are for EN 1.0.15.4 (tpp_steam_mst_en_day3800).

The pipeline

equipId
  -> weaponId            (equip table object, vtable call)
  -> gunBasic row        (11 part ids + grade)
  -> part rows           (receiver, barrel, magazine, bullet, ...)
  -> pool rows           (receiver base/wobbling/system/sound, falloff curves)
  -> GunInfo             (0x90-byte struct gameplay reads)

The assembly happens in tpp::gm::impl::equip::EquipSystemImpl::SetUpGunInfoFromGunPartsDesc (0x140DC3850). Its input is a GunPartsDesc: 11 bytes, one part ID per byte, in exactly the same order as a gunBasic row (see below). For a normal weapon the desc is copied from the gunBasic table; for the six custom-weapon slots it comes from ChimeraPartsSetWork instead.

The tables are (re)built from the game’s Lua parameter files by ReloadEquipParameterTables2 (0x140A41AE0).

The buffer directory

0x142A711F0 holds the parameter-tables instance. It is a directory of pointers - each offset below holds a pointer to one buffer.

Two indexing conventions apply. Part buffers are 1-based: row for id N sits at base + (N - 1) * stride, and id 0 means “no part”. Pool buffers are 0-based: row for index N sits at base + N * stride.

The gunBasic buffer is a static block at 0x142C25C50.

equipId to weaponId

Weapon equip IDs do not carry their weapon ID in the equip-ID table’s type words. The mapping lives in a separate equip table object reached through the quark system table:

obj = *( *( *(GetQuarkSystemTable() + 0x98) + 0x1E8 ) + 8 )
type     = obj->vtbl[0](obj, equipId)     // 1..8 = gun categories
weaponId = obj->vtbl[2](obj, equipId)     // vtbl offset 0x10

GetQuarkSystemTable = 0x140BFF050. A reference consumer of this exact chain is EquipParameterTablesImpl::GetAttackIdByEquipId (0x140A3BCD0), which resolves equipId -> weaponId -> receiver -> attackId.

Weapon IDs are effectively capped at 0x3FF because the equip-ID table packs them into a 10-bit field (see below).

gunBasic row (stride 12)

One row per weaponId. Each part ID is a single byte, which is why every part ID space is capped at 255.

The 11-byte GunPartsDesc used at realize time is bytes 0-10 of this row.

Receiver row (stride 6)

The receiver is the weapon’s core: it selects the attack (damage row) and points at four pool rows that carry the actual numbers.

A separate byte table (0x142349A90, one byte per receiverId, read through 0x140DB6CB0) selects the receiver’s motion/animation family - which set of handling animations (draw, reload, idle pose) the weapon plays.

receiverParamSetsBase pool row (stride 12)

receiverParamSetsWobbling pool row (stride 14)

Seven consecutive u16 values, each stored as value x 1000:

receiverParamSetsSystem pool row (stride 3)

Bit-packed:

plusOneChamber is the only flag here with a gameplay effect: during GunInfo assembly it adds +1 to the magazine capacity. The rest drive model meshes, HUD reticle choice and trigger behavior. eqpType also picks the fire-sound template (below).

receiverParamSetsSound pool row (stride 8)

An inline char[8] string: the weapon’s fire-sound name root, up to 7 characters plus a terminator ("ar01", "hg00", …). Not a hash - the raw text lives in the row.

Fire-sound name construction

DefineWeaponFireSound (0x140DC03A0) wraps the root into full Wwise event names at weapon-init time:

sfx_w_p_<root>[_m][_sup]_(active|nonact)    player-fired
sfx_w_e_<root>[_m][_sup]_(active|nonact)    NPC-fired

Whether the _m segment is inserted - and whether a sound is produced at all - follows the receiver’s eqpType:

The finished names are hashed through the sound system’s own hasher and the 32-bit hashes are stored into the weapon work slots, so anything resolvable by the loaded soundbanks can be produced by pointing the root (and family) at it.

Barrel row (stride 2)

barrelParamSetsBase pool row (stride 7)

Seven u8 multipliers, each stored as value x 100 (100 = 1.0 = neutral):

Magazine row (stride 8)

A magazine’s parameter set is ammoId, equipAmmoId, capacity, totalCarry, bulletId - but ammoId is the row index, not a stored field. The row holds the remaining four:

The same convention holds for every part buffer on this page: the part’s own id (receiverId, barrelId, stockId, …) selects the row and is never stored inside it.

Bullet row (stride 14)

Both falloff indices matter: the player curve drives the player’s damage model, the NPC curve drives soldiers firing the same weapon. NPC ballistics ignore dropRate entirely - NPC rounds have zero drop.

bulletType spread (buckshot) is engine-handled: the fire routine spawns a hardcoded 8 pellets in a 2-degree cone for that type.

bulletParamSetsBase (falloff) pool row (stride 22)

Three damage channels, each “full strength until near, fades to far, then a residual floor”, plus penetration:

Stock row (stride 2)

Muzzle option row (stride 3)

The HUD suppressor gauge derives its segment count from durability: 255 = 4 segments (infinite), under 16 = 1, up to 30 = 2, above = 3.

Sight row (stride 5)

Option row (stride 1)

Underbarrel row (stride 3)

An underbarrel is a sub-weapon: it borrows a receiver for firing behavior and a magazine for ammunition. During GunInfo assembly the underbarrel’s receiver and pools are re-read into a secondary block of the same GunInfo.

Custom-weapon slots (Chimera)

The six saveable custom-weapon builds occupy fixed equip IDs 0x367-0x36C. Their parts do not come from gunBasic - each slot stores its own GunPartsDesc in the ChimeraPartsSetWork block at 0x142C934A0 (returned by tpp::gm::GetChimeraPartsSetWork, 0x141E03790):

Weapon-init and GetAttackIdByEquipId both special-case this equip ID range and read the desc from here instead of resolving a weaponId.

Damage parameter table

Damage rows live in a separate table, keyed by attackId (the u16 in the receiver row). Instance pointer at 0x142BDCFF0; the row array starts at instance + 8. Rows are 0-based: row for attackId N at base + N * 0x1A. 489 rows. Rebuilt by ReloadDamageParameter (0x1405CE160), read through GetDamageParameter (0x1405C9E30).

Row layout (stride 0x1A):

Flag bits at +0x14:

Equip-ID table (model and package)

Separate from the parameter tables: every equipId maps to its model and package through a compressed-index table. The equipId is first compressed to a slot index (649 slots), then:

• Info list (0x142C20FD0, stride 0x18): +0x00 u64 .parts path hash, +0x08 u64 .fpk path hash, +0x10 block byte.
• Type words (0x142A70928, u16 per slot): (equipType & 0x3F) | (subId << 6). The 10-bit subId field is what caps weapon IDs at 0x3FF. For gun equips the subId here is not used for parameter resolution - the equip table object above is authoritative.

Address summary (EN 1.0.15.4)