Damage Formula & Effect Stacking
Attribute arithmetic, duplicate artifact buffs, critical multipliers and conditional damage calculations from shipped build 1.1.1.0.
Reviewed local game tables and selected native instructions from Windows build 1.1.1.0. Original-instruction tests use synthetic actors and engine services. They are not gameplay measurements; online overrides have not been observed.
Group modifiers by the attribute they change
The native aggregator separates AddBase, MultiplyAdditive, DivideAdditive, MultiplyCompound, AddFinal and Override. Within one applicable channel, without an Override: V = ((B + sum(AddBase)) × (1 + sum(MultiplyAdditive − 1)) / (1 + sum(DivideAdditive − 1))) × product(MultiplyCompound) + sum(AddFinal). Override handling is a separate branch.
Two +30% Sharpness contributions add to MeleeDamageSourceMultiplier: a neutral base of 1 becomes 1.6. They do not independently multiply to 1.69. Healthy Strike supplies 1 + DamageBoost as MultiplyAdditive on that same attribute when Health / HealthMax meets its threshold. A 0.4 DamageBoost contributes a 1.4 multiplier to that attribute's additive-multiplier group.
After aggregation, the game can apply an instance curve, a class limit or adjustment, and then configured rounding, in that order. Different attributes and damage conditions remain separate. The Build Lab's nominal totals are not a finished health-damage simulation.
Evidence for this section
- The within-attribute stacking formula is recovered
direct native code, qualified modifiers within one evaluation channel. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a - Healthy Strike sends 1 + DamageBoost
direct native code plus authored item data. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/3.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a - Attribute curves precede attribute limits and configured rounding
direct native call chain. Record:
reference/local-native-followup-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
0a391d24d99bb4820a2e87030f360387bd895e6d1fef4b6e5289a1db0dc95714 - Simple passive effect instances use additive attribute contributions
Native effect construction, stack lookup and previously recovered attribute aggregation. Record:
reference/local-equipped-effect-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
d456f3287ed00f3ca3e95e6def73c88b383823fb41a55127d7a21eca3517aadf
Two recovered damage paths
MMC_Damage starts from the Health set-by-caller input, adds the source's BaseDamageBonus when the effect qualifies as an attack, then multiplies captured values from all qualifying rules. The constructor defines one additive rule and 29 multiplicative rules, containing 47 attribute captures. An effect coefficient is applied separately; a coefficient is not automatically literal HP damage.
The separate SWDamageData packet path converts percentage input to input × targetMaxHealth / 100 when required. It then adds flat source damage, applies attack-source, general, damage-type and condition factors, applies target resistance and armor factors, applies an eligible survival limit, and returns a nonnegative result. These recovered paths must not be collapsed into one unconditional product of every tooltip bonus.
A single swing can produce a primary packet, elemental packets, splash and later status ticks. Fire Aspect, Poison Fog and Shockwave use separate blast abilities. One hit, one button press, a whole combo and all subsequent damage are different totals.
Evidence for this section
- Flat damage is added before the qualifying damage factors
direct native code; MMC_Damage calculation stage. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a - The native damage-packet arithmetic is recovered and independently emulated
direct native code plus 57 synthetic-input CPU-emulation cases. Record:
reference/local-native-followup-evidence-1.1.1.0.json/findings/2.Reviewed record SHA-256:
0a391d24d99bb4820a2e87030f360387bd895e6d1fef4b6e5289a1db0dc95714 - One swing can produce several damage packets
data-chain. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/9.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8
Critical chance and critical damage are separate
The shipped player general critical multiplier is 1.5, overriding the attribute class constructor's 2. Melee and ranged critical attributes start at 1. A qualifying melee critical uses general critical multiplier × melee critical multiplier; ranged uses the ranged counterpart.
Shadow Form adds 1 to critical chance. Critical Precision status overrides chance to 1. Critical Strength status adds 2 to the general critical multiplier, producing 3.5 from the shipped player baseline in isolation. A guaranteed critical does not itself create a second critical-damage multiplier.
The gear effect named Strength internally modifies the melee critical multiplier. Strengthened status modifies general outgoing damage by AddBase +1. These are different effects despite similar names; their values cannot be substituted for one another.
Evidence for this section
- The shipped player critical baseline is 1.5, overriding the class default of 2
Native constructor, type attribute import/inheritance/assignment path and DefaultPlayer table. Record:
reference/local-equipped-effect-evidence-1.1.1.0.json/findings/2.Reviewed record SHA-256:
d456f3287ed00f3ca3e95e6def73c88b383823fb41a55127d7a21eca3517aadf - General and attack-specific critical multipliers multiply
direct native code; conditional critical damage factors. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/2.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a - Shadow Form, the flute and the drums use different critical operations
data-chain. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8 - The gear effect Strength is different from Strength status
direct-data. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/10.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8
Dynamo and Power Amplifier share empowerment
Dynamo and Power Amplifier feed AttackEmpowerment. The native attribute starts at 1 and has a default maximum of 2. The authored adjustment curve's endpoint of 8 does not establish an attainable 8× or 9× damage bonus: the maximum adjustment runs after the curve.
Under unchanged native defaults and independent additive increments, the conditional result is min(2, curve(1 + sum(increments))). These are defaults and arithmetic, not verified activation counts. Refresh behavior, multiple copies and online overrides still matter.
A traced post-target callback removes effects matching CriticalFlurry, Dynamo and LingeringPower when the context is first processed, the source is a player and the attack-source bit test qualifies. That predicate does not settle every miss, proc, splash, multi-target or consumption-order case.
Evidence for this section
- Dynamo and Power Amplifier feed a shared attribute
data-chain. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8 - Empowerment starts at 1 and has a separate native maximum of 2
direct native initialization and clamp path; live override selection unverified. Record:
reference/local-native-followup-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
0a391d24d99bb4820a2e87030f360387bd895e6d1fef4b6e5289a1db0dc95714 - The post-hit path removes empowerment effects once per eligible attack context
direct native cleanup predicate; some practical source eligibility remains unresolved. Record:
reference/local-native-followup-evidence-1.1.1.0.json/findings/6.Reviewed record SHA-256:
0a391d24d99bb4820a2e87030f360387bd895e6d1fef4b6e5289a1db0dc95714
Outgoing buffs, incoming vulnerability and speed
Strengthened contributes +1 and Weakened contributes −0.5 to BaseDamageMultiplier. Starting at 1, both together yield 1.5 before further adjustments. Multiplying 2 by 0.5 would give the wrong attribute result.
Weakened and Zapped/Conductive use MultiplyAdditive on BaseDamageResistanceMultiplier with values 1.5 and 1.25. From a neutral base of 1, their combined value is 1.75 before target adjustments, rather than 1.875. Immunity and other defenses can change the final result.
Melee and ranged attack speed use an authored piecewise linear curve through (1,1), (2,2), (5,3), with constant extrapolation. From input 2 to 5, output is 2 + (input − 2) / 3. This is an attribute curve, not a complete animation or attack-frequency model.
The emerald damage magnitude is 1 + clamp(emeralds / cap, 0, 1) × (maximumMultiplier − 1), bounded between 1 and that maximum. The configured cap and maximum come from the owning ability; this is not an unlimited currency-to-damage conversion.
Evidence for this section
- Strength and Weakness add on the outgoing-damage attribute
data-and-engine-model. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/3.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8 - Weakness and Conductive share an incoming-damage attribute
data-and-engine-model. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/4.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8 - Attack speed has an explicit diminishing-return curve
data-and-engine-model. Record:
reference/local-combat-formula-evidence-1.1.1.0.json/findings/8.Reviewed record SHA-256:
3c2eb87416ae4f2b217b79ddd453ed9d65fe98aaee226c2cfa7c69e623cd03d8 - The emerald damage bonus is linear and capped
direct native code plus authored item data. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/4.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a
Recovered passive-effect wiring
The following 18 families forward their stored item value to an AddBase modifier in Channel0. Their damage condition must still qualify. Fixed template values are not proof that every tier can roll on every item.
| Effect | Attribute | Operation | Tier I / II / III stored values |
|---|---|---|---|
| Sharpness | MeleeDamageSourceMultiplier | AddBase · Channel0 | 0.1 / 0.2 / 0.3 |
| Impact | RangedDamageSourceMultiplier | AddBase · Channel0 | 0.1 / 0.2 / 0.3 |
| Finesse | MovementDamageMultiplier | AddBase · Channel0 | 0.15 / 0.25 / 0.35 |
| Pyromancer | FireDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Sorcerer | ArtifactDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Electromancer | LightningDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Soulmancer | SoulDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Venomancer | PoisonDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Critical Edge | CriticalHitMultiplier | AddBase · Channel0 | 0.1 / 0.2 / 0.3 |
| Strength | CriticalHitMultiplierMelee | AddBase · Channel0 | 0.15 / 0.2 / 0.25 |
| Marksman | CriticalHitMultiplierRanged | AddBase · Channel0 | 0.15 / 0.2 / 0.25 |
| Sharpshooter | RangedChargedAttackMultiplier | AddBase · Channel0 | 0.3 / 0.35 / 0.4 |
| Bully | OpportunityMultiplier | AddBase · Channel0 | 0.25 / 0.35 / 0.5 |
| Cryomancer | IceDamageMultiplier | AddBase · Channel0 | 0.1 / 0.15 / 0.2 |
| Point Blank | RangedPointBlankAttackMultiplier | AddBase · Channel0 | 0.25 / 0.5 / 0.75 |
| Duelist | PrimaryTargetDamageMultiplier | AddBase · Channel0 | 0.2 / 0.25 / 0.3 |
| Bounty Hunter | HurtTargetDamageMultiplier | AddBase · Channel0 | 0.2 / 0.25 / 0.3 |
| Vanguard | FullHealthTargetDamageMultiplier | AddBase · Channel0 | 0.2 / 0.35 / 0.5 |
Evidence for this section
- Equipped effect values feed their modifier tags directly
Native equip chain and 24 synthetic value-forwarding scenarios. Record:
reference/local-equipped-effect-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
d456f3287ed00f3ca3e95e6def73c88b383823fb41a55127d7a21eca3517aadf - Simple passive effect instances use additive attribute contributions
Native effect construction, stack lookup and previously recovered attribute aggregation. Record:
reference/local-equipped-effect-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
d456f3287ed00f3ca3e95e6def73c88b383823fb41a55127d7a21eca3517aadf
Do three Warrior Drums buff more than one?
The recovered shipped configuration says no. Warrior Drums supplies one Critical Strength status per recipient. It adds 2 to the general critical multiplier, so the shipped 1.5 baseline becomes 3.5 before other bonuses and the separate melee/ranged critical factor. Two or three accepted applications retain the same strength; this is not a separate final-damage x2 multiplier per drum.
The status inherits AggregateByTarget with a stack limit of one. Selected original-instruction tests retain one active entry after repeated same-source, different-source and simultaneous applications. Registry identity uses the named definition rather than an inventory slot. These are controlled offline checks, not a live multiplayer demonstration.
Accepted repeats refresh the stored duration and reset its start time. They do not bank several full durations. For a four-second status starting at time 0, accepted repeats at times 1 and 2 move its calculated expiry to 5 and 6, not 8 and 12. A shorter incoming duration can replace a longer stored one. Duplicate-slot cooldown sharing and sustainable rotations are not yet established.
Evidence for this section
- Repeated Warrior Drums does not increase the recovered status strength
Authored artifact/prop/status chain, native registry lookup, scalar inheritance and selected stack updates. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe - Accepted repeats refresh duration rather than banking multiple full durations
Native accepted-spec replacement, original duration-start helper and eight status-builder scenarios. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe - Drums adds two to the general critical multiplier rather than doubling the completed critical hit
Shipped player/status values plus sixteen native packet evaluations with explicit resolved attributes. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/2.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe
Different buffs affect different stages
Fighter’s Flute supplies Critical Precision, which overrides the general critical-chance attribute to 1. Drums adds 2 to the general critical multiplier. Strengthened adds 1 to BaseDamageMultiplier. Grindstone adds 15 to BaseDamageBonus. These are distinct definitions; each selected status refuses duplicate stacks. Chance does not itself increase a hit that has already been specified as critical.
With otherwise neutral factors, a supplied base of 10, Grindstone +15, Strengthened multiplier 2 and Drums critical factor 3.5 combine as (10 + 15) x 2 x 3.5 = 175 internal packet units. This is a conditional arithmetic example, not a measured health loss or proof of an obtainable full loadout. Other bonuses that change the same attribute combine by their modifier operations before the damage factors multiply.
Research Lab now lets you select these four buffs as already active on the chosen hit. Repeated named selections contribute once. Flute does not automatically select the Critical condition. The calculator exposes flat bonuses and each applied operation; activation timing, uptime, final Health loss and full-build legality remain outside its scope.
Evidence for this section
- Different named buffs may coexist even when each refuses duplicate stacks
Authored modifier/definition differences, native same-definition lookup controls and conditional packet combinations. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/3.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe - Drums adds two to the general critical multiplier rather than doubling the completed critical hit
Shipped player/status values plus sixteen native packet evaluations with explicit resolved attributes. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/2.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe - The within-attribute stacking formula is recovered
direct native code, qualified modifiers within one evaluation channel. Record:
reference/local-native-executable-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
98cb4f335426b463fb7713b434cdb380b843cf7c58cc6bfc1ba233fe37bf4e6a
Base duration, origin actor and overlap delivery
The authored base durations are 4 seconds for Critical Strength, Critical Precision and Strengthened, and 6 seconds for Grindstone. Positive-duration bonuses can change them. The selected native status builder uses base duration x source GivePositiveStatusDurationMultiplier x recipient ReceivePositiveStatusDurationMultiplier x event magnitude, unless an override or hook changes that result.
The traced Drums and Flute overlap paths send the named status with event magnitude 1. The builder checks SWOriginActorInterface: a valid origin actor supplies the source ability-system component and duration attribute; absent or invalid origin data leaves the prop as source. The actual prop origin assignment is still untraced, so this is not a claim that every prop always uses its summoner.
Twelve new controlled cases cover two overlap configurations, four begin-overlap wrapper controls and six origin/fallback duration cases. The broader duplicate-buff investigation contains 46 scenarios. Engine services, actor identities and some gate decisions are supplied fixtures; full activation, modifier installation and online overrides remain unverified.
Evidence for this section
- Drums and Flute overlap events supply a duration factor of one
Authored overlap settings and selected original-instruction dispatch. Record:
reference/local-buff-dispatch-evidence-1.1.1.0.json/findings/0.Reviewed record SHA-256:
806c6051b7b8a41ccd9ab5194ce248e319d5d0dbd1e1fa7862ffdef2c6fb06a8 - A valid origin actor supplies the positive-duration source attribute
Native status-builder source selection with six controlled origin-interface fixtures. Record:
reference/local-buff-dispatch-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
806c6051b7b8a41ccd9ab5194ce248e319d5d0dbd1e1fa7862ffdef2c6fb06a8 - Accepted repeats refresh duration rather than banking multiple full durations
Native accepted-spec replacement, original duration-start helper and eight status-builder scenarios. Record:
reference/local-buff-stacking-evidence-1.1.1.0.json/findings/1.Reviewed record SHA-256:
cc887f9c0a4c3d3cf1f010e9c1bec3d56749ac9d2448c66cfceca706e92a1dbe
Sources & data coverage
Reviewed local game tables and selected native instructions from Windows build 1.1.1.0. Original-instruction tests use synthetic actors and engine services. They are not gameplay measurements; online overrides have not been observed.