Problem with Aq Season 5 GG mini boss!!
Sunny2847
Member Posts: 125 ★
Kabam please look into this...Green goblin hitting through block.lost two champs to the very first mini boss..hope this will be addressed
https://youtu.be/Q0xHJEmZjC0
https://youtu.be/Q0xHJEmZjC0 0
Comments
He didn't hit through your block. You tried to swipe back and evade his SP2 but got the timing wrong, hence got clipped and died.
I used to be able to evade all parts of Green Goblin's L2 without fail. I'd push him to it to avoid the block damage from the L1.
After the update, I fought him on 2 different nodes in a single war (usually an easy fight) and 3 different times I got clipped by the last glider hit of the L2, just before the bomb. I tested it out again in a few more arenas and something similar was happening. I could only seem to evade the L2 1 out of every 5 times or so.
I never brought it up because I don't have a way to prove that it wasn't just me. I never had a problem with his L2 before over countless fights and now I can't seem to evade it with any level of consistency. Any more, I evade the first hit and block the next 2 just to be safe.
It kind of reminds me of the Domino "block break" issue where it was really a timing issue that was a factor of how fast the two hits connect (like hits 2 and 3 for GG's L2). That looks to be what's happening in the video. But from my own experience coupled with this video, it seems that the timing of Green Goblin's L2 has changed in the last month or so.
It could be just me, but it just seems weird that I'd lose the skill to evade so suddenly right as an update occurs. It seems worth looking into.
Try not to take it personally. I think people are still sensitive to this thanks to Domino. So many people were getting clipped by this very issue that it was reported and later confirmed by Kabam as an unintentional block break. Kabam later walked that statement back and said it's a function of the timing of the hits. Turns out, people were instinctively attempting to swipe back after an initial block to avoid damage. This technique has a chance of working with no real risk against most other champs. However, the timing of Domino's hits were such that attempting to evade after a block would drop your block and result in a hit. This all happened so fast that it appeared to be a block break.
People swore up and down that they weren't trying to swipe back against Domino whenever they "had their block broken" but a true block break couldn't be replicated when no dodge was attempted (i.e. just holding block and nothing else...see Dorky Dave's video). I think that might be happening here with you against Green Goblin. You may think that you only held block, but it's possible you may have instinctively tried to evade at some point during the animation.
Given the Domino issue, I'd say a true block break is possible, but unlikely in this case. The two look too similar and the Domino issue was explained and tested. However, it does seem like with the number of people reporting issues, something has changed with Green Goblin's L2 and I think it's worth testing and investigating.
Edit: Read another thread and figured it out. The minis now have 400% attack and 200% health vs 450% health last season. I’m all for boosting the difficulty, but 400% attack isn’t boosting difficulty, it’s nerfing survivability. Garbage.
i blocked the first part... i never moved at alll and got hit by the second hit
3 fights in a row
If you'll look at my post earlier, you'll see your question is answered, but here is the summary:
People think he may have tried to evade thanks to the recent Domino issue that's still fresh in people's heads. If you'll remember, those videos gave no in-game indication that an evade was attempted either, which led people to believe there was a block-break mechanic going on. It was so subtle that it was even confirmed by Kabam as a block break, only to be walked back later. Since this issue looks similar and we know Kabam has been adjusting animation timing the last few months (Drax, Domino), people think it's possible that this is going on here as well.
But we agree that this should be looked into. So many people are having problems that didn't have problems before that it's clear that SOMETHING is different now and it's worth finding out what that is.