It should really only kill players that fail it, since it should have no bearing on being able to use the mandatory LB3 unless all tanks are taken out. However currently it causes a wipe for some reason.
Printable View
It should really only kill players that fail it, since it should have no bearing on being able to use the mandatory LB3 unless all tanks are taken out. However currently it causes a wipe for some reason.
How can you even tell who fails the mechanic? If one fails then everyone fails and I didn't spot any visual effect of chains breaking or not breaking.
In the Battle Log there's no mention of it either.
You can tell who failed, just vote kick if it happens again.
A couple of weeks ago, I configured my keybinds and made R my reply key for chat. During the ATE, I randomly pressed keys in the center like I used to. I forgot about R. Chat box opened, became filled with gibberish, hit enter to close the box, everyone sees gibberish, we wipe.
I apologize profusely and we continue. And then I accidentally did it again.
I reset my PC and hid under my blanket for an hour. I’m 41 years old.
Should we tell the OP about the Nald'Thal fight and how close you can fail that? I want to say their chains don't break. Though a lot of the times the person who fails makes a comment about messing up.
This is an actual issue. I had 2 runs in the past where someone trolls in this fight. It's failed twice, people leave, it's failed again, we disband. There's no way to tell who's doing it, and kicking the underperforming sprout who's doing it for the first time is not going to help because it probably isn't them.
It usually is someone whose first time it is. It usually doesn't happen the next time, especially because everyone types in the chat and explains what to do.
Usually, maybe. But those 2 fights I talked about had no underperforming sprouts. Just a first-timer who wants to get through the story and said that they didn't fail, and someone who wants to waste people's time. Either way, the fact that we can't tell who's failing it is an issue. It should be like Hades where only the people who fail die.
Active time events are such a useless gimmick. Hate the darned things.
Every single time I've run this fight and we fail more than one time in a row:
"Just fyi.. you can push ALL the buttons and they count. Controller or keyboard as long as it's not "chat""
next time: Pass.
Instead of votekicking, maybe explain to that person how it works?
A lot of PC players assume the button in the middle of the screen must be mouse clicked and despite having the seen active time manuevers a few times before this, they don't understand that's incorrect unless someone tells them. That leads to failure because depending on the mouse or joint problems in your hand you won't be able to click that fast.
So if someone fails, ask if they're using mouse/keyboard and let them know the button doesn't have to be clicked. Instead, they can just rapidly mash keyboard buttons. They'll learn something new and they'll have a better experience for it while the group will hopefully stop wiping.
Also agreed. I don't know why the developers think they're an engaging mechanic.
But we're stuck with them so have to make the best of the situation.
So... the way to find out who wasn't clicking fast enough, is to use a third party mod, and then arbitrarally blame the person with the lowest number, even if there's no sign that it was them?
I mean, that's patently not true. MOST active battle fights are properly coded, and things like the key bound to "reply" don't open the chat window and force you into it, but for some reason this fight still causes all your hotkeys to various things to still work, and that can lead to some VERY strange things instead. We've even HAD a post in this topic about that happening.
THIS time it has to be keys that arn't bound to... well, a LOT of things. I stick to just wasd, and the mouse buttons. I could probably also hammer the number pad, or run down 1 to 9, but that's a bit overkill. Problem is this one is a marathon, not a sprint, so people hammer quickly at the start, too quickly, and cramp up or get tired. I mean, we ALL know this here, because we've passed but... yhaknow, find a spot that matches a pace your comfortable with, the 50% spot is okay, 33% is actually pretty easy, just be ready to put on a sprint at the end at the sound effect.
Agreed.
Mindlessly mashing random buttons to fill a bar has nothing to do with combat, skill, the chosen class and the fight itself. It doesn't give off a sense of urgency or danger, if anything it breaks the immersion of a big fight even more. Enrage bars filling is a much better way to create a sense of urgency and coming doom.
yes remove this boring mechanic
These active time events are just silly.
The true test of the Warrior of Light is spamming the same button quickly for 10 seconds.
That proves something, I guess?
I get the sentiment but at least if it only killed the folks who failed it you'd know who failed it so you could kick them.. they can't get there clear if they get kicked.. if its going to wipe everyone then it really needs to highlight who failed so they can be removed if they fail repeatedly instead of continuing to waste everyone else's time...
The failing players will kick off no matter what happens. If they git kicked for failing they'll complain. If the group falls apart because they're failing. they'll complain. And blame anything except themselves... game needs a giant flashing arrow that says "you fkd up!"
Even if it means it'd pop over my head a few times because I can make some dumb mistakes.
They'd never do that for the same reason they don't want parsing, cause it can be used to bully players.
The obvious solution is just to make it so it's like Shinryu or Hades, where if you fail, you die, and everyone else is fine. Which honestly is kinda what you're asking for, except the giant flashing arrow is instead just death.
I imagine the reason it isn't like that is for some kind of story/thematic element, which I'm sure sounded great in theory, but in reality just turns every 10th run into an exercise in frustration.
While I agree that it should be changed to just a single player kill rather than a group wipe, your reasoning is bad logic.
Otherwise, they'd never make any mechanic where you can quite clearly see a player killing you with. You think a party isn't going to put a person on speaker if someone brings that AoE into a stack marker? Or even later in the fight, when the GA-100 marker goes out along with the stack marker and its extremely evident who its on? Or the party bullying the tanks if one of them presses the LB3 incorrectly and wipe to the following attack? In all those situations you don't even need a giant flashing arrow to know exactly who screwed up and can put the lights on for wiping the group. Highlighting who messed up would be no different than any other mechanic that causes a person to kill the whole party with.
All fair points, but I think the difference comes down to how visible it is. Logically speaking, if they have no issue with you idenitfying the "problem player" then they should have no issue with parsing. Yet they do.
Giving it some thought, I reckon it might be to do with how visible it is, or rather, how easy it is to hide.
Someone bringing an AoE into a stack marker, there really isn't any way to hide that without compromising the integrity of the fight itself.
Something less visually obvious, such as who is not doing enough damage, or who didn't faceroll their keyboard enough during an ATM, is much easier to mask.
Ah QTEs are poorly implemented imo, they show you a big button and I think to anyone they expect to click it (I know I did when I was new) as opposed to just facerolling your keyboard. SoS QTE is rough in the case of 'if you don't break your keyboard you'll die'.
5.3 was a fun time to run trial roulette....
I disagree kind of. In this particular instance, one person failing should not wipe the party, it's a stupid gimmick and shouldn't be in the game anyway (roll your face over the keyboard events), but I'd like to see more punishing mechanics that can wipe the party in normal mode. Actual mechanics though, not Starcraft APM simulator for 5 seconds, they're not interesting, or particularly challenging, just worthless. Also kind of cruel if you have carpal or RSI.
Also factor in this ATB works completely different from all the others in the past (well, in terms of normal mode content)
Before it was just hit the button until you fill and success.
This one is "randomly smash buttons for 15 seconds, even if you managed to fill the bar, don't stop!"
Y'all forget some folks have hand problems when it comes to button mash as fast as you can. I recall people bringing this issue up.
love how friendly community of critically aclaimed MMO goes on "hehe kick underperformers" rampage when it benefits them. LOL
Why would they know by the time they get to SoS when failing it in the other duties with it doesn't wipe the party? Most trial parties I'm in shrug when the sprouts die, finish the trial and leave while the sprout is still watching the Duty Complete cutscene. Unless there was a wipe (extremely rare in other normal trials with the event), it's not likely anyone is going to stop to explain.
You can't assume someone is trolling just because they fail the same mechanic a couple of times in a row. What if the player is a non-English speaker and so can't understand the explanation given for the mechanic? How many party members would be willing to sort through the auto-translate trying to find phrases that would explain it sufficiently?
It's actually not that demanding on the player. The rapid drop at the start is a fake out to add a sense of panic and urgency. Tapping just as rapidly as you would in any other encounter is sufficient.
Aaaah, right. So using the magic toolbox that Yoshi P says we're not supposed to have we kick out those with the lowest scores and then...
Oh my! It's still happening! You know why? Because people troll! Somehow the person dealing the most damage is failing. How could we have ever predicted this?
And for anyone wondering, yes I've been in runs where the first time everyone passed the QTE and then after an unfortunate wipe we suddenly ended up failing repeatedly, again and again. One specific run I remember was where both tanks were new and didn't pop LB3. People were very spiteful and we failed about 5-6 times before I left(after half the original party had already left as well).
Honestly I don't get why this is something the community defend. It's like they don't really care if it's a bad feature or not, they just see another opportunity to disagree with someone else and spout "git gud" and "kick the bads" (when they're probably quite bad at the game themselves anyway).
There is no point in the ATE. It's not a skill check. It's not a mechanic to figure out. It's not an interesting part of the fight. Just mash random buttons. There is zero reason failing it should result in a group wipe. Fairly simple.
Yet here we all are arguing about it anyway, just for the sake of arguing.
Sos ate event sucks period. I can do every other ate event in this game with just my space bar. Sos ate NOPE need to hit space bar and at least two other keys to avoid failing, and even that is barely enough.
press any key or faceroll keyboard... works in EX too.
At least you realized you needed to do the event. At least you read the chat. I had an instance where, after the first wipe people asked in chat who didn't click. People were told EVERYONE needs to click. We wipe again. I'm pretty sure we wiped a third time, I'm not sure, I had blocked it from my memory until I saw your story but the person finally responded in chat that they didn't know everyone needed to do the event. Which brings up so many questions, were they just not doing all the active time events up until now or something?
Extend 10 seconds to 5-15 minutes and sprinkle in a couple other buttons at random intervals and you'd be playing a healer.
Yeah it should be removed and lel at the edgy kids that want to kick people as soon as they make one mistake, I wish upon you the same treatment in any new online game you’ll play