Is Apocalypse SP3 not suppose to do damage?
baskinrobbinsknows
Member Posts: 275 ★★★
Hi all. So I'm doing the EQ this month on the last chapter which is the mutant class one. I'm ready through all the stuff and I don't see special 3 not suppose to do damage. However it's a lot l, so I may have missed stuff or forget about abilities. Anyhow, Apoc SP3 damage has been doing 0 damage for all th paths I've tried him on. Everyone else's SP3 work just fine. Even his SP2 and 1 work fine. What am I missing?
I recorded a fight in case anyone needs it. Ignore the terrible gameplay
https://youtu.be/ZjY5oy3LWxk
I recorded a fight in case anyone needs it. Ignore the terrible gameplay
https://youtu.be/ZjY5oy3LWxk
Post edited by Kabam Zibiit on
8
Comments
But seems it's another bug
@Kabam Zibiit
Bishop vs Aegon ( EQ 3.2 No Hit Mercy path )
Experienced the same thing 3 different times using Apoc on EQ 3.2 easy path
I think it has something to do with Achilles Heal node ... Heard some people experiencing the same thing in Side Quest 1.1 ( Achilles Heal path ) too
Because every champ I've experienced this with had prowess ... And an alliance mate experienced the same in Story mode ( Mags against 6.3.5 Darkhawk ) so it's not limited to EQ only.
Cav EQ 3.2 .. top difficulty. Using Prof x
(full team was:
Prof X, Red Magneto, Bishop, Iceman, Ebony Maw)
I'd be using Prof X (and I'm still new to using him) .. would parry-heavy until 100 charges, then build to sp3 .. throw sp3 .. notice 0 dmg total .. following sp2 would usually 1 shot them .. or take off like 60% of their health, minimum ..
folowup sp1 would kill them 90% of the time .. almost any fight.
I just thought the sp3 was doing 0 dmg, but setting up for the sp2 dmg?
(still not sure :P )
Your known issues bug notes post says you are working on this problem for the Event Quest 3.2. It makes no mention of this problem being worked on for any other area. Myself and others have pointed out it was happening to us in the Side Quest. Are you working on a fix for both places separately, is your fix going to fix all instances of this problem regardless of where it is or are you not acknowledging and/or fixing this issue anywhere other than in EQ 3.2?