Special Connoisseur 6.4.2 - sp3 not doing damage
Haji_Saab
Member Posts: 5,837 ★★★★★
My team was CapIW, Beast, Domino, Havok, Colossus... I worked my way up to Void playing normally with no boosts. The sp3 were hitting hard as they do for Havok, taking away 50% hp in each sp3.. . took a break, came back to the game and popped 20% champion boost, mutant power boost and mutant specials attack boost.
My sp3s stopped working! The sp2s were working fine but the node protection was not turning off on sp3. As you can see from the pic, I had all kinds of prowess effects but my sp3 only did 7500 damage which is only 10% of normal Havok damage!! Is it a known bug or something? I am not sure if the bug is linked to the boosts??
Such a wastes of time and boosts
P.S. i restarted the run and recorded the fights against Claire to take the picture.
My sp3s stopped working! The sp2s were working fine but the node protection was not turning off on sp3. As you can see from the pic, I had all kinds of prowess effects but my sp3 only did 7500 damage which is only 10% of normal Havok damage!! Is it a known bug or something? I am not sure if the bug is linked to the boosts??
Such a wastes of time and boosts
P.S. i restarted the run and recorded the fights against Claire to take the picture.
2
Comments
You will only get the prowess from the sp3 after using it. So sp3 will have the damage reduction due to that factor. You will need to use an heavy attack and convert 2x charges in to a prowess effect, before using the special
Magento - I threw an SP3 against Void while I had 37 Prowess buffs: 10% health damage!
Proxima - I threw an SP3 with all 3 missions completed: about 15% health damage!
This is costing me resources. Please fix it!
No big deal on a personal note, it was white mags in 7.2.2 I used a sp3 with Magik with 10 prowess and white Mags having 10 prowess also thinking big damage, nah not even 1%. Still got the solo, but its a bit annoying that you saw it was bugged 2 years ago and still put it out in the next batch of content a year on, and it still isn't fixed 2 years on.