One match: 100 base damage plus 134 damage for a total of 234.
1st cascade: 75% of 100 damage = 75 base plus 134 for a total of 209
2nd cascade 75% of 75 damage = 57 base plus 134 for a total of 191
Bringing your total to 634
Post update: same assumed statistics
One match: no change, 234 damage
1st cascade: 75% of 234 for 176
2nd cascade: 75% of 176 for 132
Total damage of 542.
3rd cascade differences in total damage is: 867 vs. 643
With 4 strike tiles and 3 cascades after the original match the damage difference is 1348 vs. 1006.
All these numbers are assuming only matches of 3.
Doesn’t appear to be overly dramatic whatsoever, and comes in line with the way cascades are intended. Now a freak 7 or 8 chain cascade won’t instakill someone.
It seems logical that if the damage of a tile match degrades in a cascade, that the attack bonus ought to degrade as well. It seems like a mistake that someone could make, misplacing the code that applies the damage bonus. It also seems like it would be something easy to miss in QA/QC.
348 seems pretty significant. I would be mad too. What would have been the damage without the bonus?
Edit: I see your other post was updated. It doesn’t seem much but it is significant.
Without any bonus, at 100 base damage, a chain of 3 would do 232 damage.
(Yes I realize 100 damage isn’t possible with a match 3, I just did it for simplicity)
And yes, I realize the difference can be extremely measurable with a decent amount of strike tiles. I’m arguing that the original bugged mechanics were too powerful and therefore exploitable and the bonuses now, while less, are still extremely useful and do not at all nullify the usefulness of strike tile generation, it just lessens it under certain extreme situations.
I agree with you. I sympathize with those who focused on Wolverine and Daken. I have a fully leveled Daken myself. I felt cheated when they nerfed Loki.