Core itemweapons

PP19 Bttstck

Weapon attachment

The uploaded DayZ configuration defines this classname as an item that weighs 720 g.

DayZ classname

PP19_Bttstck

Game configuration facts

These values and relationships are extracted from the supplied DayZ config definitions rather than guessed from the economy XML.

Weight

720 g

Inventory size

3 × 1

Absorbency

Inventory slots

weaponButtstockPP19

Where it spawns and where to look

The location guidance below combines your supplied types.xml tags with a small curated knowledge layer. The central-economy values remain the authoritative data for this website build.

Chernarus

Enabled

Military-tagged loot points such as barracks, tents, checkpoints and military compounds.

Usage tags

Military

Livonia

Disabled

Present in the file but disabled from ordinary central-economy spawning with nominal and minimum set to zero.

Usage tags

Military

Sakhal

Enabled

Military-tagged loot points such as barracks, tents, checkpoints and military compounds. The supplied economy limits this entry to Tier3 loot value tag.

Usage tags

Military

Loot tiers / values

Tier3

Central economy comparison

Map	Nominal	Min	Lifetime	Restock	Quant min	Quant max	Cost	Usage	Values
Chernarus	4	2	14400	3600	-1	-1	100	Military	—
Livonia	0	0	14400	3600	-1	-1	100	Military	—
Sakhal	8	4	14400	3600	-1	-1	100	Military	Tier3

Attachments, compatibility and spawn loadouts

Config-derived

Mechanical compatibility is extracted from the supplied DayZ config definitions. “May spawn with” groups come from the supplied official cfgspawnabletypes.xml files and describe possible generated attachments or cargo, which is separate from everything the item can accept during play.

Compatible weapons

PP19PP19

Map-specific types.xml entries

Chernarus XML

<type name="PP19_Bttstck">
  <nominal>4</nominal>
  <lifetime>14400</lifetime>
  <restock>3600</restock>
  <min>2</min>
  <quantmin>-1</quantmin>
  <quantmax>-1</quantmax>
  <cost>100</cost>
  <flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0" />
  <category name="weapons" />
  <usage name="Military" />
</type>

Livonia XML

<type name="PP19_Bttstck">
  <nominal>0</nominal>
  <lifetime>14400</lifetime>
  <restock>3600</restock>
  <min>0</min>
  <quantmin>-1</quantmin>
  <quantmax>-1</quantmax>
  <cost>100</cost>
  <flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0" />
  <category name="weapons" />
  <usage name="Military" />
</type>

Sakhal XML

<type name="PP19_Bttstck">
  <nominal>8</nominal>
  <lifetime>14400</lifetime>
  <restock>3600</restock>
  <min>4</min>
  <quantmin>-1</quantmin>
  <quantmax>-1</quantmax>
  <cost>100</cost>
  <flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0" />
  <category name="weapons" />
  <usage name="Military" />
  <value name="Tier3" />
</type>

Related DayZ items

PP19PP19ATOG 6×48 ScopeACOGOptic_6xAK BayonetAK_BayonetAK Folding BttstckAK_FoldingBttstckAK Plastic BttstckAK_PlasticBttstckAK Plastic HndgrdAK_PlasticHndgrdAK Rail HndgrdAK_RailHndgrdAK Wood BttstckAK_WoodBttstckAK Wood HndgrdAK_WoodHndgrdKA-101AK101KA-74AK74AK74 HndgrdAK74_Hndgrd

Need this configured across a full server?

Use the data as a reference, then let CustomDayZServices handle the complete economy, balancing and deployment workflow.

Get a quote