**KNOWN AW ISSUE**
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
**KNOWN BG ISSUE**
We are aware of an issue with the seeding for the beginning of the BG season.
We are adding rewards to higher progression brackets to offset the additional grind.
More information here.
We are aware of an issue with the seeding for the beginning of the BG season.
We are adding rewards to higher progression brackets to offset the additional grind.
More information here.
**Arcade is being extra tricky with his Murder Box...**
It appears Arcade has been non-cooperative in his approach to this month's side quest and presented his clues in a nonsensical order. Lucky you, Summoners, we have our best and brightest on the case and those clues should now be a lot more straightforward. While messing around in Arcade's files we came across a phrase, highlighted and bolded, with sparkles and pointy arrows: "the abode for the dead" ... Maybe that will help you along the way!
It appears Arcade has been non-cooperative in his approach to this month's side quest and presented his clues in a nonsensical order. Lucky you, Summoners, we have our best and brightest on the case and those clues should now be a lot more straightforward. While messing around in Arcade's files we came across a phrase, highlighted and bolded, with sparkles and pointy arrows: "the abode for the dead" ... Maybe that will help you along the way!
Options
Comments
Just like if there's going to be a fix is Kabam's choice.
Just like it's your choice to respond to me when I was answering someone else about what choices we have.
Obviously you don't find it irrelevant or you would have just ignored it.
I'm not saying don't ask here for updates either. I'd like to know if they are going to actually fix the nodes, or if they are going to ignore it till the quest expires.
I've also made my choice, which is not to do level 5 noded path.
If Kabam fixes it, then I'll reevaluate my choice.
Also keeping posts going here is helping prevent it from falling off the main bugs and known issues page.
Yeah the description of the node is terrible..
It doesnt work as described...
But u can figure it out and do it with any champ...
Heavy, intercept, heavy...
There is people all over the place calling it a bug, asking even for compensation🤣
It's the fact the node is a complete lie, the moral of the story It's wrong they have admitted it is wrong, but nothing's done. kabams 🤷♂️ oh well. Compensation is irrelevant, correction is what we want, either drop protection when knocked down or node description say knock down twice for protection.
Poor showing by Kabam. What’s the point of a bug forum if they do zip even about issues they acknowledge?
I still think kabam should fix this tho
I just went through Threat level 4 and no issues with Havok. Solo with Warlock - several times I did Heavy to shut off protection, then intercepts (easier said than done, mind you...) to transfer the Unstoppable. No subsequent Heavy required to turn the Protection off again.
So it seems to be okay, now.
Same as it has always been
- when you knock the def down, unstop kicks in first, protection removal second
- protection removal checks if unstop is active, and only removes itself, if not unstoppable
- this incorrect order/logic causes the protection removal to fail
How to reproduce:
- use She Hulk, parry+heavy. Slow will disable unstoppable effects, and the protection will go away on first knockdown
- use Falcon, lock-on and knock down. AAR will prevent unstoppable to activate and the protection will go away on first knockdown.
If you use anyone without AAR or slow, protection will stay on first knockdown due to the incorrect order in the removal logic checks.
The big question is, if we can reverse engineer the logic from playing the game, why can’t those fix it, who created the logic in the first place? It’s just swapping the order of checks, or adding a threshold in the check of when the unstop activated.
——————
For a good team to work around the bug:
- use Gio99 without knockdowns for all mutants, ending with an sp3 to start with a 100 combo.
- use She Hulk, Crossbones (high sig), Falcon (lock-on) for the other fights
- Torch, Spidy 2099 for Mojo
My concern is this is exactly what Kabam wants… the players who are able drowning out the players not in that position so they can justify not doing what they said they would do.
Again I ask… why have a bug forum?
This is kind of weird as I went through with no trouble earlier today and it was genuinely working fine for me.
I've gone in again after your posts and I'm having the same trouble again. Very strange.
Hope they get a fix out soon.
A feature is just a bug with seniority and acceptable documentation, a bug is just a poorly documented feature...
Its not thaaat hard...
U guys gonna wait for the fix till tuesday and then complain u didnt have enough time to finish it and ask for compensation...
Yes the description is TERRIBLE, the node is not working as described.. but there are ways around it.