DayZ modder config.cpp knowledge base

Where to look

• Open or list the PBO with a PBO opener.
• Find the config.cpp file.

• Main item classes are usually under CfgVehicles.
• Check parent class, scope, displayName, model, ClothingTypes, inventorySlot[] and attachments[].
• Protection is controlled by DamageSystem, GlobalHealth and GlobalArmor damage multipliers.
• Inventory size, quickbar, weight, heatIsolation, wetness and repair values are safe customer-config targets.

Config example

class CfgVehicles
{
    class Clothing;
    class MyVest: Clothing
    {
        scope = 2;
        inventorySlot[] = {"Vest"};
        class DamageSystem {};
    };
};

• Weapon classes are usually under CfgWeapons.
• Magazine compatibility uses magazines[] and chamberableFrom[].
• Projectile damage is often in CfgAmmo, not directly in the weapon class.
• Fire modes, dispersion, recoil, zeroing, sound sets and muzzle attachments should be compared with a vanilla weapon.

Config example

class CfgWeapons
{
    class Rifle_Base;
    class MyRifle: Rifle_Base
    {
        magazines[] = {"MyMagazine"};
        chamberableFrom[] = {"MyAmmo"};
        modes[] = {"SemiAuto", "FullAuto"};
    };
};

• Creature and AI classes are usually under CfgVehicles.
• Attack damage can be connected through CfgAmmo or melee ammo classes.
• HP, hitzones, armor and movement speed must be balanced together.
• Start from a similar vanilla creature because AI, animation, hitzone and attack behavior often depends on the parent class.

Config example

class CfgVehicles
{
    class ZombieBase;
    class MyMutant: ZombieBase
    {
        class DamageSystem {};
        class Cargo {};
    };
};

• itemSize[], itemsCargoSize[], attachments[] and quickBarBonus.
• weight, heatIsolation, varWetMax and repair values.
• DamageSystem hitpoints and GlobalArmor damage multipliers.
• requiredAddons[] should point to the core addon so classes load after the original mod.

Config example

class CfgPatches
{
    class MyMod_Config
    {
        requiredAddons[] = {"MyMod_Core"};
    };
};

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Basic DayZ armor class structure. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Scope, name and description. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Model and ClothingTypes. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Inventory slots. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Attachment proxies and memory points. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Inventory size: itemSize and itemsCargoSize. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Quickbar bonus. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Weight. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers HeatIsolation. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Wetness and varWetMax. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Visibility modifier. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Repair settings. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Hidden selections, textures and materials. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers DamageSystem basics. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Hitpoints. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Armor damage multipliers - the most important rule. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Projectile, Melee, Infected and FragGrenade. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Meaning of Health, Blood and Shock. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Helmet-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Mask-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Shoe and boot-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Glove-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Pants-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Vest and armor-specific fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Recommended customer-editable armor fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Openable config PBO example. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Quick armor protection balance table. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Common armor mistakes. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers TitanGuard protected armor release advice. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Short modder checklist before release. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers Quick armor balance sample. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Armor, clothing, helmet, pants, boots, gloves and vest classes are usually under CfgVehicles.
• After opening the PBO, search config.cpp for the class name, parent class, inventorySlot[], attachments[] and DamageSystem fields.
• Keep the original parent class in a customer config PBO so inheritance does not break.

What to check

• This entry covers The most important armor rule in one sentence. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include itemSize[], itemsCargoSize[], quickBarBonus, weight, heatIsolation, varWetMax, repair values and DamageSystem balance.
• Be careful with model, ClothingTypes, skeleton, hiddenSelections, simulation and script class changes because they can break the worn item.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers DayZ weapon config basics. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon base classes. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon inventory fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon inventorySlot. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon attachment slots. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers chamberableFrom and magazines. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons, CfgMagazines consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers chamberSize, chamberedRound and reloadAction. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Fire modes: modes, SemiAuto and FullAuto. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Dispersion and accuracy. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Recoil. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Sway, initSpeedMultiplier and zeroing. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Optic and ironsight fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Suppressor and muzzle attachment. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Magazines - magazine config basics. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons, CfgMagazines consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Ammo - most weapon damage is here. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon damage vs armor damage. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon durability and DamageSystem. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons, CfgAmmo, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Jam, reliability and wear. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers SoundSet fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Muzzle flash, particles and casing. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon hiddenSelections. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Recommended customer-editable weapon fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Quick weapon balance table. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Common weapon mistakes. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers Weapon modder checklist. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Weapon classes are usually under CfgWeapons; magazines and ammo often connect through CfgMagazines and CfgAmmo.
• After opening the PBO, search config.cpp for the weapon class, chamberableFrom[], magazines[], modes[], dispersion, recoil and damage links.
• When balancing, verify that weapon, magazine and ammo classes point to each other correctly.

What to check

• This entry covers The most important weapon rule in one sentence. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgWeapons consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include recoil, dispersion, magazine compatibility, durability and selected balance values.
• Be careful with weapon, magazine and ammo relationships because damage often comes from CfgAmmo rather than the weapon class itself.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature, AI, zombie and animal config basics. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature HP - GlobalHealth and hitpoints. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Hitzones - head, body, leg and arm. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature protection - GlobalArmor and damage multipliers. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, CfgAmmo, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Damage types for creatures. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature damage - attack damage. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Melee ammo - creature damage on the CfgAmmo side. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature movement and speed. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature loot and inventory. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature armor zones - concrete protection example. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature damage balance example. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, CfgAmmo consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Quick creature protection table. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles, DamageSystem consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Common creature mistakes. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Recommended customer-editable creature fields. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers Creature modder checklist. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.

Config location

• Mutant, creature, infected, animal and custom AI classes are usually under CfgVehicles.
• Attack damage is often connected through CfgAmmo or melee ammo classes.
• Balance HP, hitzones, armor, movement, loot and damage together instead of tuning one field alone.

What to check

• This entry covers The most important creature rule in one sentence. Compare the values with a similar vanilla DayZ class before changing them.
• Check the original class, parent class and requiredAddons[] load order first.
• Keep technical fields such as config.cpp, CfgVehicles consistent across the related classes.
• Test the result in both client and server logs after packing the edited PBO.

Customer config safety

• Good customer-editable fields include HP, armor multipliers, attack damage, speed and loot values.
• Be careful with AI parent classes, animations, hitzones and attack logic because creature behavior is strongly inheritance-dependent.

PBO opener relation

• Open the PBO with the PboViewer / PBO opener entry linked from the modder tools knowledge base.
• The values described here are found in the opened or unpacked PBO config.cpp file.