**BANQUET EVENT PSA**
To fully participate in the upcoming Banquet's Alliance Event you will need to be in your alliance for 14 days prior to the event's start date on December 20th. That means, stay in your alliance from December 6th onwards to enjoy all there is to offer in the Banquet event.
To fully participate in the upcoming Banquet's Alliance Event you will need to be in your alliance for 14 days prior to the event's start date on December 20th. That means, stay in your alliance from December 6th onwards to enjoy all there is to offer in the Banquet event.
**Not Another Anime Reference Solo Event Returning**
This solo event has been fixed and will appear in game again on December 10th and will run through the 17th.
Reminder: This event is available to Paragon+ Summoners
This solo event has been fixed and will appear in game again on December 10th and will run through the 17th.
Reminder: This event is available to Paragon+ Summoners
INCOMING BUG FIX:
We'll fixing an issue with the Side Quests where all difficulties had the same Selector rewards.
We've fixed the Selectors in Threat Levels 4, 3, 2 and 1 to no longer contain rewards for Progression levels above the target audience.
Threat Level 4 rewards cap out at Thronebreaker
Threat Level 3 caps out at Cavalier
Threat Level 2 caps out at Uncollected
And Threat Level 1 has rewards for Proven
We'll fixing an issue with the Side Quests where all difficulties had the same Selector rewards.
We've fixed the Selectors in Threat Levels 4, 3, 2 and 1 to no longer contain rewards for Progression levels above the target audience.
Threat Level 4 rewards cap out at Thronebreaker
Threat Level 3 caps out at Cavalier
Threat Level 2 caps out at Uncollected
And Threat Level 1 has rewards for Proven
Hitting into block being countered by specials. [Merged Threads]
This discussion has been closed.
Comments
"...previous update provided an improvement but not a 100% fix." = Indicates this is a bug.
" It has always technically been possible and will continue to be so." = Indicates this is not a bug.
I hope you can see how this response can be seen as confusing. Could you provide some more clarity? I have been affected by this bug and/or intentional mechanic for two months now. The above official response doesn't help me, as a customer, determine if this issue will either persist as a permanent game mechanic or be treated as a bug and fixed.
For the record, it happened to me yet again this morning with OR facing Medusa in the T4B arena. Anticipating a concise, transparent explanation from the game team. Thanks.
Something changed, and you know it. You have two options: 1) it's a bug you didn't intend; 2) it's not a bug, and you did intend it.
If it isn't a bug, then I'm left with the only other option: it's an intentional change that Kabam intends to keep. If that's so, just say that, Kabam, so the community can adapt. This is not rocket science; it's economics. Since Kabam is the one raking in the $$. Hence the secret changes and then public ***** responses a month later. SMDH.
Unlike some bugs affect specifiable charcters or nodes，this affect all players, so maybe we shouldn't move on so soon .
And on this subject , I'm not so sure it's a bug , more like a intended change :
First , guard/block stun is a common concept in FTG , basicly means the period time you stuck in (unable to move) when block an attack.
What I think happened is , they reduced AI''s block stun, so the AI can react faster after blocking attack , thus they can :
fire SP mid blocking，catch you up backdrafting ，back step mid blocking...
When we call them out on this , kabam tweaked block stun length back a little ,so it don't look so obvious，but still as long as it's before .
Though we have no solid prove , concidering rencent events change , the AI tweaks , it adds up...
This change ( as i said ,not sure it's a bug) present us players 3 problems imo：
- 1 Backdraft as an effective way to attack , is no longer useful. But hey, with the AI constantly being tweaked , what's new?
- 2 When blocking attack you can't move , this is/was one of the fundamental mechanics of the game. When it's not reliable , what can we players count on？ I think broken maybe quite fit to decribe the game.
- 3 By shorten the block stun , they gave AI quite an advantage , because even if players' and AI's block stun length are same , we can never react as fast as machine to utilize it . We are not supposed to compete reaction with micro computers .It's simply unfair . And if we allow them keep giving AI unfair advantages , what's next? where it end？
The 1st problem we can adapt and deal with it. But i think we really should take the 2nd & 3rd problem seriously.I was using red hulk, hitting on guard, when yondu dexed away and countered me once,
Launched sp once
If you're still seeing this, I need exact Matchups. Which Champion you Used, and against who. We're continuing to investigate this.
No, you cannot say "it happens to everyone", because that is not going to help us narrow this down. Any posts that do not contain that information will be removed.
From what i read on the forums and myself's experience , this happened to a lot people with a lot different champions against a lot different opponents . So it may not be "everyone", but isn't limited to a few specific champions either.
It should be easy to test , just find anyone with large health pool , preferably stun immue and have some power gain — on top of my head , that hyperion in 5.4.6 fits , but really anyone fits above requirements should do. Just pick any champ you want to test to fight that guy , see what's gonna happen .
@Kabam Miike this was in uncollected EQ. 3.3 R4 Aegon vs. Medusa top left path.