Damage model

This page reads the damage model for game build 25937608. The file holds 20 hit-location profiles, 6 ammo types, 11 vehicle-seat entries, and 1060 modification rules. Projectile damage, on the ammunition pages, is the hit damage before distance falloff, armor, and hit location. Falloff lives on the weapon. These layers are stored apart. This page does not multiply them into the damage of a shot. The files do not publish the order in which a base damage, a falloff curve, a hit-location multiplier, an ammo-type modifier, and a rule amount combine.

Each hit-location profile is named by a class token. Universal is its own profile. It is not an average of the weapon classes, and the page does not use it to fill a class the file omitted. Every profile stores a multiplier per body region. The regions in this build are the keys on those objects: head, neck, three torso bands, pelvis, and the arm and leg segments. A cell is the stored multiplier. If a profile omitted a region, that cell would be marked missing. The page does not choose which profile a weapon uses.

The ammo-type table is one row per stored type. The modifier column is the number stored on that type. It is not a result after armor, and this page does not turn it into a percentage. Types that store a by-arms-class map in this build: ArmorPiercing, ArmorPiercing.Tracer. Types whose map is empty: FMJ, Tracer, HollowPoint, HollowPoint.Tracer. An empty map is not zero, and it is not a copy of the modifier. Those cells are marked missing. The class tokens use the same words as the projectile damage-context tags, such as Meta.Damage.Arms.Small. The files do not say that the map is applied to that tag, so this page does not apply it.

Armor is stored in two places. The by-arms-class map is one. The other is every rule whose category is Armor (135 rows in this build). A rule names an entity, a source list, a target list, an instigator list, hit locations, a category, an operation, and an amount. custom is null on 1048 of 1060 rules. alignment is null on 1058. Null is marked missing. It is not shown as zero. Target is an empty list on 1025 rules, source is empty on 4, instigator is empty on 1060, and hit location is empty on 928. An empty list is the word None. It is a stored empty list, not a null. Operations in this build: Percentage_Ongoing, Add. 1047 rules use Percentage_Ongoing and 13 use Add. The amount is the number stored beside the operation. The token Percentage_Ongoing contains the word Percentage, but Add shares the same amount column. The file does not put a unit on the amount, so the table does not add a percent sign.

Past the modifier column, ammo type also appears as rules with category AmmoModifier (127 rows). Those rows keep the source tags the file stored. They are not folded into the modifier column, and they are not multiplied by a caliber's base damage here. Vehicle seats are 11 entries. Each lists damage-source groups and a reduction. The reduction is the stored number, sign included. The file does not name a unit, so none is added.

The full rule table keeps every category, in the order the file stores the rows. One category is spelled Calibre, and another is CaliberEffectiveness. Both spellings are kept. Categories in this build: Armor, AmmoModifier, Penetration, Bone, Calibre, Friendly, Tracer, Weapon, PenetrationEffectiveness, Ricochet, Melee, CaliberEffectiveness, None. Where alignment is present, the stored values are Friendly. Listing a category is not a claim that it applies to every rifle shot. This page does not estimate a number the file left out.

Korean and English carry this explanation. Every other language falls back to English until a translation is added. This site is not affiliated with Bulkhead or Team17. The numbers come from warpuppies/wardogs-data under the Unlicense. When you cite a figure, cite game build 25937608.