Bug while summon the hulkling in week 3 side quest

Hey kabam,
I don't know what is happening in side quest week 3. Node says i will get the unblockable buff when i summon the hulkling but sometime it gets unblockable buff or sometimes not. Even i tried on the opponent block. It not breaking the opponent block. I don't what is issue but in week1 it was working very fine when i played it. But now I checked week1 same issue is happening now. It was not before in week 1. I always got the unblockable buff in week 1. It is very annoying. Or just remove the button if it buggy we can play without using hulkling and kill the opponent.

Comments

Avnish

Guys pls comment here if anybody having the same issue.

Deder80

Yes… I am experiencing that to plus the game is not letting letting me use the summons button. This game is so broken.

Crine60

Hey kabam,
I don't know what is happening in side quest week 3. Node says i will get the unblockable buff when i summon the hulkling but sometime it gets unblockable buff or sometimes not. Even i tried on the opponent block. It not breaking the opponent block. I don't what is issue but in week1 it was working very fine when i played it. But now I checked week1 same issue is happening now. It was not before in week 1. I always got the unblockable buff in week 1. It is very annoying. Or just remove the button if it buggy we can play without using hulkling and kill the opponent.

Are you using a champion that applies ability accuracy reduction to the opponent? Kabam chose to make it so that you don't get the benefits of the striker if you use AAR, except for I believe the stun effect. We brought up the strikers not working with AAR champs last time and some people posted that was the way the game worked and we should just not use them if we wanted the strikers to work but with this new striker Kabam has shown they do have the ability to make effects happen with strikers regardless of AAR if they choose (also is showing up on other nodes and in some champion kits) so it is an intentional thing to restrict us from getting the benefits of some more optimal champs who have AAR.

Also, regarding the striker button, many people have also commented on how it doesn't work/trigger some of the time the same way the special button doesn't which leaves your champ open to being attacked by the opponent when they are just standing there doing nothing. I don't believe Kabam have acknowledged any of those reports but I could have missed it. This has been happening since they were introduced so not just this time.

They also were usable when you were being attacked last time if I recall correctly so you could rescue your champ if they were being hit with a combo but this time they do not seem to activate if you are being hit which is a change they did not bother to notify us of. If they are going to change the functioning of a feature from one time to another it would be nice to communicate that to us when it comes out again.

Avnish

Yes Carine60, I am using kingpin and he apply AAR after sp1. I think this is the issue when i am not throwing sp1 ke am getting unblockable buff. But thi should be mentioned in node description. Thanks buddy for clearification.