Heaven on High duty finder error!

Quote:

---

Originally Posted by Aster_E

It's the curse of all forms of review or editing. There's always bound to be that one thing the maker misses, some imperfection, that the consumer notices, and then the consumer proceeds to beat the maker over the head with that one mistake like the maker was some incompetent poor soul. Game development, book writing, you name it.

---

As an artist, I highly agree to this post^^^^

Quote:

---

Originally Posted by hynaku

Whole bug thing and them disabling it sounds very fishy and vague. Should been able to fixed the bug without shutting in down. Now makes me wonder about new eureka area when comes out. Will they find some bug and shut it down same way. I'm just surprised they still have a player base when just can't get there acts together.

---

Oh yes, SE has some ulterior motive to disable content they've worked hard on making. There's just a major issue with Demi-Bahamut if it's summoned while inside Heaven on High. Their explanation is a little vague but if I had to guess is that if a Summoner uses Demi-Bahamut inside and then leaves before it despawns it remains inside the instance. Considering they labeled it as critical it may mean that the instance cannot shut down since Demi-Bahamut isn't despawning. If the instance can't close then it continues to take up space on the server. Now multiply for each Summoner that has Demi-Bahamut and they were left with little choice but to lock the instance until it could be resolved. Again this is a lot of speculation but it would make sense, if it were that players couldn't summon Demi-Bahamut and nothing more then they'd have just told people not to use it until they resolved the issue instead of taking the entire content offline.

Quote:

---

Originally Posted by NephthysVasudan

If you think its so easy to develop a product...then you do it.
Otherwise please...stop being childish.

Software always has an issue or two on launch day. People always find ways to abuse things and break things. This is normal.
Yes..we should fire Yoshi for a bug....totally rational...totally reasonable comment to make.......not.

---

While true, there's a bigger issue in this case.

Yes. Users will ALWAYS find ways to bend and break your product in ways you never expected. On the other hand, this is not a weird or rare situation that no one could have predicted. This issue easily could, and should have been discovered with even a basic amount of play testing.

Quote:

---

Originally Posted by Warghoul570

The fact that just about every part of Stormblood has been a broken disaster is what’s grounds for termination

---

Clearly you don't play very many games, if you think this is a "Broken Disaster" you need to get out more. Actually, FFXIV is one of the more polished MMO's I've played, you want broken disaster, try WoW, STO (In its early days, still could be better now), just to name a few. Every game has its flaws, and even with players testing things on PTS's, things occasionally slip thru the cracks. Honestly until I couldn't get into HoH I hadn't experienced any problems at all, I thought it might have just been congested like SB when it released. Trying to que for that fight with Grynewaht, now that was a disaster.

Quote:

---

Originally Posted by NyteKitsune

Clearly you don't play very many games, if you think this is a "Broken Disaster" you need to get out more. Actually, FFXIV is one of the more polished MMO's I've played, you want broken disaster, try WoW, STO (In its early days, still could be better now), just to name a few. Every game has its flaws, and even with players testing things on PTS's, things occasionally slip thru the cracks. Honestly until I couldn't get into HoH I hadn't experienced any problems at all, I thought it might have just been congested like SB when it released. Trying to que for that fight with Grynewaht, now that was a disaster.

---

Hell have him try any of the Korean MMOs that have been coming out. They all start out as a dumpster fire. Most recently Bless Online.

Quote:

---

Originally Posted by NyteKitsune

Clearly you don't play very many games, if you think this is a "Broken Disaster" you need to get out more. Actually, FFXIV is one of the more polished MMO's I've played, you want broken disaster, try WoW, STO (In its early days, still could be better now), just to name a few. Every game has its flaws, and even with players testing things on PTS's, things occasionally slip thru the cracks. Honestly until I couldn't get into HoH I hadn't experienced any problems at all, I thought it might have just been congested like SB when it released. Trying to que for that fight with Grynewaht, now that was a disaster.

---

My favorite I ever heard of was in LotR online when a friend of mine was playing, there was an update that broke the ground. Everywhere. Log in, fall forever, or something like that, and it was busted so bad people had to reinstall to fix it.

Saying anyone should lose their job over a bug is ridiculous. No game goes without them, especially one this massive, and all in all.. like others said. FFXIV is polished.

That being said... I do agree that it would be nice if SE hadn't split up the patch so much. Disabling HoH wouldn't be such a big deal if it was alongside other content we could focus on in the meantime...

If people got fired for bugs getting out Bethesda would of probably closed down after Skyrim's launch.

Quote:

---

Originally Posted by ArkNova

If people got fired for bugs getting out Bethesda would of probably closed down after Skyrim's launch.

---

Long before that tbh haha.

Quote:

---

Originally Posted by Deceptus

This wasn't some crazy bug. It could easily be in the realm of normal play.

---

Typically the way this sort of issue happens is that a fix to some other bug causes an unexpected, seemingly-unrelated failure. So your QA team does all its rounds and files all its reports. Then you fix the critical bugs the QA team found, and they test to confirm that the fixes addressed those specific issues. But at that point you're not necessarily going to have the whole team test everything all over again from scratch when it seems the bugs are fixed. Except for the unexpected consequence...