As the title states the event is way harder than the first time around. Maybe you should fix the bug instead of saying it's not having a effect on anything. Anyone playing the game knows it's effecting the game.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
The level of difficulty increase shouldn't really be a factor in the argument. The fact that there is any increased difficulty at all means they messed up the event.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
From the wording in his kit, yes, he should have been countering.
The thing that changed wasnt his kit, it was a background "order of operations" of battle that changed what is happening, his kit is 100% the same as it has always been.
I'm not saying people shouldnt complain, but to blame it on a "bug" is not correct, he is not bugged, the event is not bugged.
That reads as a change or a bug, acknowledgement that there is a difference but nothing will be done..
@CG_SBCrumb can we have a comment on this please? Disadvantage coded into the game for people trying to unlock this time around? Is that an official policy now?
Thank you for posting the developer post where they acknowledged the behavior changed, never called it a bug, and then stated the change was due to fixing a bug.
Semantics. "Bugged", "Changed order of operations" call it whatever you like. The fact remains that the event has changed in an increased difficulty from last release to this one. If that was intended then they need to release a statement saying as much. If it was unintended then I'm going to consider the event broken.
I'm not really concerned with his kit, I'm concerned with the event. GAS isn't bugged, I get that. The event is more difficult due to corrections they made in regards to how his kit interacts with the game.
@Jaggedfel181 in which case the dev team need to address the change between iterations of the event. Perhaps everyone who has tried and failed p4 should be awarded the shards they are missing.
That solution seems a bit extreme. The issue is GAS getting 2-3 more attacks so I would think scaling back his damage a little to make things more on par with the previous release would be a good solution
@Jaggedfel181 it may be extreme, but as there will be no way that anything could be adjusted with light the event being down for weeks on end (see the malak fiasco) it would be simpler to just award them I think.
Semantics. "Bugged", "Changed order of operations" call it whatever you like. The fact remains that the event has changed in an increased difficulty from last release to this one. If that was intended then they need to release a statement saying as much. If it was unintended then I'm going to consider the event broken.
Lets all start discussing GAS being bugged or fixed instead of talking about the increase in difficulty caused by the change.
Anyway, i'm with @ZAP on this one.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
looool "exploited a bug"
he really isn't any harder to beat now that his counter is working as written
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
looool "exploited a bug"
he really isn't any harder to beat now that his counter is working as written
Yes it does. And the event is indeed harder due to the counter before cover. The extra move has a ripple effect throughout the rest of the battle where you need RNG to go perfectly to win.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
looool "exploited a bug"
he really isn't any harder to beat now that his counter is working as written
I’m struggling big time with P4, but it’s not because of that last GAS counter before kneeling, it’s no one targeting my DDK when he has DI and then echo dispelling and stunning him.
maybe your droideka is too fast? Slow it down so Echo dispels right before you put up your shield? Maybe? I don't know, I won't even get to try until next time.
So the bug was when he wasn't countering? It's a mechanic that has changed so it had to be bugged at some point. If it was bugged before then everyone who unlocked GAS exploited a bug. The event has changed significantly, I think this gives people a legitimate right to complain.
looool "exploited a bug"
he really isn't any harder to beat now that his counter is working as written
ah, in the title, ty. Thought he was saying they changed it. I remember seeing the title and thinking it was badly worded (from CG, I know right? lol) bc his kit didn't change, just it started working as written
I’m struggling big time with P4, but it’s not because of that last GAS counter before kneeling, it’s no one targeting my DDK when he has DI and then echo dispelling and stunning him.
maybe your droideka is too fast? Slow it down so Echo dispels right before you put up your shield? Maybe? I don't know, I won't even get to try until next time.
fast droideka is to get the shields up to allow his assists from his zeta (not sure if it's been said itt)
Replies
Can you explain how this is a bug according to his kit?
From the wording in his kit, yes, he should have been countering.
The thing that changed wasnt his kit, it was a background "order of operations" of battle that changed what is happening, his kit is 100% the same as it has always been.
I'm not saying people shouldnt complain, but to blame it on a "bug" is not correct, he is not bugged, the event is not bugged.
@CG_SBCrumb can we have a comment on this please? Disadvantage coded into the game for people trying to unlock this time around? Is that an official policy now?
Unless you whale hard, in which case your golden..
Thank you for posting the developer post where they acknowledged the behavior changed, never called it a bug, and then stated the change was due to fixing a bug.
Ok so you consider the event broken.
Now what?
Anyway, i'm with @ZAP on this one.
Welcome to software development.
And you more often create 2 more than just 1 if you're in a rush when correcting :-D
looool "exploited a bug"
he really isn't any harder to beat now that his counter is working as written
it literally doesn't
Yes it does. And the event is indeed harder due to the counter before cover. The extra move has a ripple effect throughout the rest of the battle where you need RNG to go perfectly to win.
it literally does ... right in the title
maybe your droideka is too fast? Slow it down so Echo dispels right before you put up your shield? Maybe? I don't know, I won't even get to try until next time.
ah, in the title, ty. Thought he was saying they changed it. I remember seeing the title and thinking it was badly worded (from CG, I know right? lol) bc his kit didn't change, just it started working as written
fast droideka is to get the shields up to allow his assists from his zeta (not sure if it's been said itt)
spam filter ate my reply so had to retype