-
Notifications
You must be signed in to change notification settings - Fork 7
Weapon Structure Definition
zeroKilo edited this page Apr 19, 2020
·
16 revisions
- For the 3 classes up to 3 weapons are defined over the packet
GetAllDefaultLoadoutKits
inInventoryService
- Weapons in game are defined over the packet
GetTemplateWeaponMaps
inWeaponService
- in the packet for the weapon definitions are 4 std::maps, where the key is the weaponID
-
TemplateWeaponList
containing information about the weapon itself -
WeaponCompatibilityBridge
containing list of DWORD ids -
TemplateComponentLists
containing list of DWORD ids -
Components
containing information about components of a weapon
- so for each weapon these 4 things have to be defined
- templatecomponentlists should contain 1 item with key of weapon and value of 2 component map keys
- from the components the modefierlistid is used to select a modefierlist
- 2 skill modefiers should exist there with modtype 2 and proptype 105 & 106 for grip and barrel
- their methodvalue selects components again by mapkey
- from these components the key member is used th load the GAOs