Omega Ultimate bugged

[VerdeLuck]

yes we are regulated
but that doesn't mean we are not allowed to judge developers on a moral level, especially when we are beaten on the head about how "they cleared without the use of third party tools"
as if the prog of developers is equivalent to what players have to do to prog, i.e. restarting all the way to the beginning each wipe

yes it's illegal
yes it's against the rules
but that's not what I'm discussing here

The testers are not "progging" the fight. They're pulling open up different phases to make sure that buffs are applied correctly in situations even when players disconnect, and that nothing despawns or falls out of the map in fringe cases. You seem to have a fundemental misunderstanding of what testers do. They aren't there to prog the fight blind and then clear multiple times, they're there to make sure the DPS check is possible to hit and that mechanics don't glitch out leaving players unable to complete it.

Every bit of content in this game is designed, balanced, and tested based on the assumption that players doing this will not be using tools. Full stop. That doesn't mean testers and devs don't use debugging tools while testing to make sure everything reacts the way it's supposed to.

[solimiano]

yes we are regulated
but that doesn't mean we are not allowed to judge developers on a moral level, especially when we are beaten on the head about how "they cleared without the use of third party tools"
as if the prog of developers is equivalent to what players have to do to prog, i.e. restarting all the way to the beginning each wipe

yes it's illegal
yes it's against the rules
but that's not what I'm discussing here

Ok, so you want to discuss the setup they used, unless they state it somewhere we will never know.
I also tend to put a lot more effort in job than my hobbies, I get paid for my work, my hobbies are for me to relax and have fun, so whoever is clearing the fights might be better and putting more effort than us.
It might be they actually never encountered the bugs in a meaningful way that warrants a maintenance, but like always if enough people can prove the bug and complain in the technical forums/ bug section they might go for emergency maintenance and fix it.

[SeiyaSoiya]

The testers are not "progging" the fight. They're pulling open up different phases to make sure that buffs are applied correctly in situations even when players disconnect, and that nothing despawns or falls out of the map in fringe cases. You seem to have a fundemental misunderstanding of what testers do. They aren't there to prog the fight blind and then clear multiple times, they're there to make sure the DPS check is possible to hit and that mechanics don't glitch out leaving players unable to complete it.

Every bit of content in this game is designed, balanced, and tested based on the assumption that players doing this will not be using tools. Full stop. That doesn't mean testers and devs don't use debugging tools while testing to make sure everything reacts the way it's supposed to.

ah yes because checkpointing clearly allowed them to test the fight properly without leaving out the possibility of the main tank having a lingering magic vuln debuff that would get him instantly killed upon the boss autoattacking

maybe if they didn't cheat they could have caught this problem before release

[Mikey_R]

I suspect this is more to do with latency than anything else, ie. if you have higher latency, you could get tagged for the auto, before the debuff expires. Of course, being a tester, you have very minimal latency, so these issues do not come up, meaning you can make the time between the debuff wearing off and the first auto as small as possible.

In theory, this should be a learning point for the battle team to test buff/debuff timers and potential one shot hits in a range of different latency scenarios, just to make sure nothing like this happens again.

[Striker44]

ah yes because checkpointing clearly allowed them to test the fight properly without leaving out the possibility of the main tank having a lingering magic vuln debuff that would get him instantly killed upon the boss autoattacking

maybe if they didn't cheat they could have caught this problem before release

You seem to believe that it is only possible to test something one way, that somehow if tools were used at some point to examine a specific part of the fight, it magically becomes physically impossible to also test the fight at other times without using said tools. This view conflicts with reality.

[Stasya]

The testers are not "progging" the fight. They're pulling open up different phases to make sure that buffs are applied correctly in situations even when players disconnect, and that nothing despawns or falls out of the map in fringe cases. You seem to have a fundemental misunderstanding of what testers do. They aren't there to prog the fight blind and then clear multiple times, they're there to make sure the DPS check is possible to hit and that mechanics don't glitch out leaving players unable to complete it.

If only there were testers that didnt use god mod only, bugs like p3 auto attack, p5 vuln auto, buff cap limit wouldn't get into release (also might add p4 dps check in heavily 2 min meta)

[Amenara]

I suspect this is more to do with latency than anything else, ie. if you have higher latency, you could get tagged for the auto, before the debuff expires. Of course, being a tester, you have very minimal latency, so these issues do not come up, meaning you can make the time between the debuff wearing off and the first auto as small as possible.

In theory, this should be a learning point for the battle team to test buff/debuff timers and potential one shot hits in a range of different latency scenarios, just to make sure nothing like this happens again.

Just an overarching problem with SE not realizing people have to deal with latency when they live outside of Japan. You can really see that weakness when you see how long it has taken them to add charges the hypercharge for MCH and we still have problems with double weaving or even single weaving.

[Hanaya]

Just an overarching problem with SE not realizing people have to deal with latency when they live outside of Japan. You can really see that weakness when you see how long it has taken them to add charges the hypercharge for MCH and we still have problems with double weaving or even single weaving.

The netcode/ping issues are so whack. I used to main ninja, and moving to a location way closer to the US servers made me feel like I was playing a different game. I went from being the master of rabbit hats to consistently using mudras properly in 3 days, entirely because of the ping difference.

It's just so strange to me, bc from what I understand, noclippy/xivalexander mostly fixes ping issues? so clearly it's possible for them to fix it. I don't understand why, after years, nothing has been done to allow people with higher ping to play the game as initially intended without forcing them to resort to 3rd party plugins. I'd understand if it was impossible to fix, but the existence of noclippy proves that wrong.

[Atelier-Bagur]

ah yes because checkpointing clearly allowed them to test the fight properly without leaving out the possibility of the main tank having a lingering magic vuln debuff that would get him instantly killed upon the boss autoattacking

maybe if they didn't cheat they could have caught this problem before release

This is a whole LOT of assumptions you're throwing out here as someone who lacks the insider information on what actually goes on with the testing group. I'll give you that its a plausibility but it would be idiotic to even assume they havent thought of just that as someone whom designed the encounter.

[SeiyaSoiya]

I suspect this is more to do with latency than anything else, ie. if you have higher latency, you could get tagged for the auto, before the debuff expires. Of course, being a tester, you have very minimal latency, so these issues do not come up, meaning you can make the time between the debuff wearing off and the first auto as small as possible.

In theory, this should be a learning point for the battle team to test buff/debuff timers and potential one shot hits in a range of different latency scenarios, just to make sure nothing like this happens again.

I don't think it's a latency issue
p8s p2 has a similar very tight timing with the debuff
if you got picked for Natural Alignment 1 you got a debuff called forcible failure
if you took ANY damage with that debuff on you would explode and deal 99999999 damage to everyone
the debuff wears off literally at 3/4ths of the cast bar of aionopyr which is a raid wide
but the debuff consistently wore off before the raid wide hit regardless of latency or ping, I know because I play on NA as an european and I have 160 ping to the servers.