CBU3's latest blunder shows the importance of Quality Control Checks

Latest version of the Relic questline has a massive bottleneck.

It involves you going to kill a mob and get a quest item. Sounds standard right?

No.

It's an overworld mob, not the kind that spawn when you enter a darkened area. An overworld mob, that hundreds of people are fighting over to get credit for.

The worst part? IT'S NOT EVEN 100% DROP CHANCE

https://media.tenor.com/t6V-MIkkT8kA...-teach-you.gif

I'm not sure what kind of "quality check" would discover that error. They could test the whole questline from start to finish and have no problem fulfilling the objectives.

Anyway, if this is anything like the crowd of people around an MSQ questgiver on patch launch day, the very simple solution is to come back tomorrow and find it dead quiet.

At least it's not just another 1500 Tomestones

It's still shitty compared to SB and ShB relic grinds.

I'm kind of convinced this was a last minute change because of the backlash from the 2nd step being another tome grind and they couldn't think of anything else.

I haven't logged in yet. Does partying work to mitigate this issue? Might be a better temporary solution than just coming back tomorrow, especially if ... everyone else decides to come back tomorrow. xd

There are three instances I just went to instance 3 and was alone killing the mark. Maybe try another instance OP.

Sounds like a good time to play other games until the issue resolves itself :).

Quote:

---

Originally Posted by Iscah

I'm not sure what kind of "quality check" would discover that error. They could test the whole questline from start to finish and have no problem fulfilling the objectives.

---

Part of QA is knowing more real life data than what coders can think of.

This isn't the first time a massive bottleneck has hindered the game.

Quote:

---

Originally Posted by Deceptus

Part of QA is knowing more real life data than what coders can think of.

This isn't the first time a massive bottleneck has hindered the game.

---

Precisely. This is such a common issue in MMOs that even in the design phase they should have changed how the quest worked.

It's embarrassing that FF14 even implemented the quest this way.

Quote:

---

Originally Posted by Iscah

I'm not sure what kind of "quality check" would discover that error. They could test the whole questline from start to finish and have no problem fulfilling the objectives.

Anyway, if this is anything like the crowd of people around an MSQ questgiver on patch launch day, the very simple solution is to come back tomorrow and find it dead quiet.

---

If your MMO QA team can't even test in anticipation of a large amount of people, what it is even there for?