Heaven on High duty finder error!

[HyoMinPark]

I mean it sucks but its only half of a day of downtime not really the end of the world and even with a test server you cant guarantee everything will be caught.

Never said that it was the end of the world. I’m not normally one to complain about maintenances, but I cannot ignore that the emergency ones have increased with Stormblood’s launch.

I like the experience of playing things fresh and if that means there is an occasional bug that gets through its acceptable trade off IMO.

Test servers don’t have to give you everything in one go, but they may be able to catch some of the things that the developers do not—like this bug for instance that is apparently high enough in importance to not only shut down the content for 6 hours, but also the servers for another 3 1/2. They also don’t have to be mandatory; if SE were to do a test server, I’m certain it would be an opt-in sort of deal. Don’t want spoilers? Don’t be a player tester. Simple as that.

[Iscah]

I feel like it’s not something that was guaranteed to be found even if they did playtest with a summoner, because Bahamut is summoned for such a short amount of time that there’s no guarantee he would ever be active at the time when the player left the dungeon. They might check that he’s behaving correctly within the dungeon, but not think of there being a problem when leaving.

I would have thought it’s no different to leaving any normal dungeon, and nobody’s had trouble with that up until now. Though perhaps PotD has the same coding flaw that just never got discovered because you can’t reach Lv70 in there, and any playtesting for HoH focused on new gameplay elements and not the PotD base programming.

In any case, I suspect it’s something they’ll deliberately test in any future new content modes...

[polyphonica]

I feel like it’s not something that was guaranteed to be found even if they did playtest with a summoner, because Bahamut is summoned for such a short amount of time that there’s no guarantee he would ever be active at the time when the player left the dungeon. They might check that he’s behaving correctly within the dungeon, but not think of there being a problem when leaving.

You're right. Plus, if you're a QA tester and get to the end of a test scenario, you're probably completing your notes, so you're not necessarily going to rush out of the content fast enough in that particular combination (why would you think that would cause an issue?). As you say, now that they've discovered it can be a problem, it'll be a test scenario they add to the list... but yeah, it doesn't surprise me that this bug slipped through. As some people said, it probably would have been caught on a public test server, but that definitely brings its own complications too.

[SannaR]

Nah, Man Bahamut just got super jelly of us being able to use other primals that he threw a hissy fit again. I am glad they caught this bug early before it got out of hand.

[Alleo]

I can understand that bugs can happen but it is a bit ironic that this happens with content that was already released later..well I really hope that they can fix at least that bug..will not help me much with all the DCs but hey better than nothing.

[spf1200]

Opposite, actually. Bahamut follows you out and won't despawn even with teleports, zone changes and logging out. Which gives you access to Wyrmwave at all times.

So that's why there were 3 Bahamuts in Limsa yesterday. I just thought they were hackers.

I do have to agree that this is something that should have been found before HoH was released. They keep making up wait for bread crumbs the least they could do is make sure they aren't moldy.

[Bourne_Endeavor]

This is the curse of QA teams. You can spend weeks and weeks testing and fixing tons of bugs that customers never see. But it's the one bug that inevitably gets through that everyone notices.

To be fair, I suspect people would be less angry had they not delayed HoH six weeks. At this point, many were desperately awaiting something new and it broke less than 24 hours following its release.

[CorbinDallas]

I can understand that bugs can happen but it is a bit ironic that this happens with content that was already released later..well I really hope that they can fix at least that bug..will not help me much with all the DCs but hey better than nothing.

How is it ironic? It was slated for a specific day and released with a bug resulting in down time. Just like almost every other patch we've ever had ever?

[Hestzhyen]

So...

1. YoshiP and his team do not deserve to be fired over this, despite how easy it was to find and re-produce the bug. This is pretty much a worst-case scenairo for SE- you can tell they tried to fix it without downtime but apparently that was just not possible. However, lopping off heads left and right for a mistake is a good way to lose invaluable talent.
2. Bugs happening in all software is not a free pass for a testing miss like this, especially with such disastrous results from the company's perspective. You can bet there will be internal discussions and take-aways from this so it doesn't happen again.
3. YoshiP and his team bringing the game back to life over four years ago does not have much bearing on whether we should or shouldn't criticize them over this. Yes, they did the amazing and the impossible back then. Today they had to take down the whole game to hotfix a highly anticipated new instance due to an easy to trigger critical bug. I'm grateful that XIV has been worth playing for 4+ years but that doesn't mean much when I can't play it.

[Alleo]

How is it ironic? It was slated for a specific day and released with a bug resulting in down time. Just like almost every other patch we've ever had ever?

Like others pointed out, this content was finished quite some time ago and yet thanks to their idea of staggering content in patches it was released even further down the line. Yet it needed to be taken down to fix a game breaking bug. (And there are other smaller bugs reported on reddit) i find it ironic that we get it later and yet its still buggy.

Maybe if we get everything in one patch we would also not need so many emergency shut downs. Well lets see if we have one for eureka too.