Stack 1 can have 1 target
Stack 2 can have 2
Stack 3 have 3
Stack 4 up to 6
Stack 5 goes to 12
1 + 2 + 3 + 6 + 12 = 24 total maximum target when no overlapping. 24 x 50dmg = 1200dmg.
Each stack has a separate selection, so if stack 1 with 1 target selected Unit-x. Stack 2, 3, 4, and/or 5 can all have a chance at Unit-x. And letâs say all 5 stacks DID select unit-x. Now the math becomes:
Unit-x x 50dmg x 5stack = 250dmg
AND
0 + 1 + 2 + 5 + 11 = 19 other targets with no overlap x 50dmg each = 950dmg total. In this case, total maximum damage of 1200 is still served but split between 1 x 250 and 19 x 50.
So the maximum Dmg only decreases if:
- Player doesnât attack at 5 stacks.
- Total targets is too few.
In the [2] case, if we take the above example. Unit-y is now selected by stack (which now selected unit-x and unit-y). However, you can see that stack 1 can no longer apply. So at most, if selection is âluckyâ, unit-y can receive at most 4 stacks or 50x4 = 200dmg.
So in a sea of >24 enemies, only 1 unit has a chance to receive 250dmg. Then 1 with chance at 200dmg. Then 1 at 150dmg. Followed by 3 at 100dmg, and finally rest at 50dmg.
For any non-stacks, the Dmg is simply split to 50 each to additionally selected units (upwards to 24 max, coming full circle).
So you actually end up dealing far more damage to enemy base or group, when P2 is controlled properly. And less so when your targets start to fall short of 5 or so enemies within range. However, if you do attack at 5 stacks as you should be, youâre dealing far more single target than before (in theory). Yet, the offset on attack speed on and off creep (ie. with and without buff) lends to less Leap Strike cast. This is where 1 on 1 type of situations P0 can appear to do better (because many P2 players arenât using full 5 stacks. So they wasted the time stacking say 3, dealing 150 stun Dmg + Leap Strike half Dmg 150, which only equates to 300dmg of P0 Leap strike Dmg, only without having to attack 3 times for the P0 player.)
Sorry for the long post but itâs hard to not when explaining in more details.