Please reconsider phase changes that heavily disadvantage players

[Kimikryo]

There simply isn't a "doing too well"

Example Twintania. If you know, your damage output is that high, that a phase change can happen during conflags there are three solutions.
1) Slow down dps a nodge
2) Push out more damage that the phase change even hits earlier
3) Cope with it

I did 1 and 3 several times. 1 goes against the nature of a lot of players because they want to hit faster and harder without thinking.
Solution 3 damands a group without rage quitters and "you so bad /point" people, and the luck that the target of the dangerous ability isn't someone important for the next phase.

[SeraviEdalborez]

Let's say a BLM engage the fight with a triple Flare, thus doing his maximum DPS, getting aggro from the tank immediately and dying as a result.

Would you say he's doing "well" and that "artificially limiting his DPS" is a bad thing ?

Awful example because triple flare on (I assume you mean literally) engage is wasteful of Raging Strikes and screws over all of the other DPS, because the default reaction to "mob out of control" is to stop hitting it. It's not even explicitly a DPS gain on single target. Nobody opens with triple flare on a single target boss.

Artificially limiting your DPS is when you literally have to have 6 players AFK for a minute while Ifrit EX gets far enough in his rotation to spawn final nails. Otherwise you enrage him and kill yourselves. This is terrible design and you can't argue that it isn't.

Nobody is saying that they should be able to continue mashing buttons as they get better gear and suffer no ill consequences. But that is different from being killed with little-to-no warning BECAUSE your damage is too good.

[Viridiana]

A couple of people not finding a certain mechanic fun doesn't inherently mean that it should be changed. It means that these people should just get over something that trivial.

Until enough of them say "If this isn't fun, why am I doing it?" >_>

I'm not saying I'm going to leave over this. Heck, I've barely touched second coil. I'm just saying there are plenty of more engaging ways to make us throttle dps. Even Blighted Bouquet from the same fight is more engaging than waiting for bees. >_>

Knowing when to hold DPS, by saving damage boost for precise timing is also what any good DPS shoud be doing.
In fact, I'm sure we can find a lot of situations where "doing maximum" is not the same as "doing well"

And I'm not disagreeing with that. I'm disagreeing with mechanics where I can zone out in the middle of the fight until the raid leader calls for dps again. Why should the dps be allowed to alt-tab when the other players can't?

Artificially limiting your DPS is when you literally have to have 6 players AFK for a minute while Ifrit EX gets far enough in his rotation to spawn final nails. Otherwise you enrage him and kill yourselves. This is terrible design and you can't argue that it isn't.

Nobody is saying that they should be able to continue mashing buttons as they get better gear and suffer no ill consequences. But that is different from being killed with little-to-no warning BECAUSE your damage is too good.

Pretty much exactly my point.

[Mook_Mook]

The main issue is gear is more or less equating to more work(or less work because you have to put away your weapon and wait) for the statics to re learn fights based on there item level and higher level of skill, which is rather counter productive.
Should dps pay attention yes! Can slowing down DPS as a mechanic be a cool feature yeah! Is slowing dps because youve reached max ilevel and you are good at your class because of poor fight structuring no!

[Dwill]

Artificially limiting your DPS is when you literally have to have 6 players AFK for a minute while Ifrit EX gets far enough in his rotation to spawn final nails. Otherwise you enrage him and kill yourselves. This is terrible design and you can't argue that it isn't.

Nobody is saying that they should be able to continue mashing buttons as they get better gear and suffer no ill consequences. But that is different from being killed with little-to-no warning BECAUSE your damage is too good.

When an encounter is designed, it's designed with an average item level that's meant for progression in mind which means that people overgearing the encounter/having the encounter of farm status isn't the biggest factor taken into account. The example you gave is one where people overgear the instance by a higher item level than it was designed for which leads to result you've described.

Honestly, I think this is a petty issue since it barely make the affected encounters that much longer.

Until enough of them say "If this isn't fun, why am I doing it?" >_>

Which is an extremely small amount of people, therefore a non issue.

[SeraviEdalborez]

When an encounter is designed, it's designed with an average item level that's meant for progression in mind which means that people overgearing the encounter/having the encounter of farm status isn't the biggest factor taken into account. The example you gave is one where people overgear the instance by a higher item level than it was designed for which leads to result you've described.

Honestly, I think this is a petty issue since it barely make the affected encounters that much longer.

That is a terrible excuse. People were running into "kill self on enrage Hellfire" when i90 was still the highest ilvl. Which is also before Echo existed for that fight. Echo and increase to i110 only made the problem more widespread.

The ilvl for Ifrit EX is what, i70? At what point do you personally consider that you've "outgeared" the fight then? My static personally was having this problem when we were all around low to mid i80s with i90 weapons. And we were still punished for a fight that was supposedly tuned to be current content.

No really, how can you defend this in any way?

[reality_check]

Which is an extremely small amount of people, therefore a non issue.

Come back after you've wiped 5+ times on Ramuh EX because of bad phase changes.

[Dwill]

That is a terrible excuse. People were running into "kill self on enrage Hellfire" when i90 was still the highest ilvl. Which is also before Echo existed for that fight. Echo and increase to i110 only made the problem more widespread.

The ilvl for Ifrit EX is what, i70? At what point do you personally consider that you've "outgeared" the fight then? My static personally was having this problem when we were all around low to mid i80s with i90 weapons. And we were still punished for a fight that was supposedly tuned to be current content.

No really, how can you defend this in any way?

The mechanic itself isn't inherently broken. It's the fact that the content was released with people already overgearing it which is something quite common in this game and something that I hope Square Enix fixes in the future.

Come back after you've wiped 5+ times on Ramuh EX because of bad phase changes.

If you can't control your phase changes after 5+ wipes, that's a PEBKAC issue.

[SeraviEdalborez]

The mechanic itself isn't inherently broken. It's the fact that the content was released with people already overgearing it which is something quite common in this game and something that I hope Square Enix fixes in the future.

Yes. It is. There is any number of ways they could have made Ifrit not just outright kill you for getting his HP% to an arbitrarily low threshold. Here's one: Ifrit takes 0 damage until nail phase ends.

When you literally have to have your tanks put their weapons away because even that much damage is going to enrage, you have a poorly designed fight.

Ifrit is not even the only fight to have an arbitrary pseudo-enrage for not throttling DPS: Haukke Manor HM's final boss works much the same way. A fucking 4-man dungeon boss.

[reality_check]

If you can't control your phase changes after 5+ wipes, that's a PEBKAC issue.

Have you beaten Ramuh Extreme? You have your achievements on Lodestone blocked.