PDA

View Full Version : How do these Bugs keep Getting Missed?



Impaqt
02-06-2008, 12:25 PM
Raid Repeating....

The last three modules have all had significant Raid repeating Bugs..... Being able to repeat too much or not being able to repeat at all....

Repeating the raid is a BASIC and Fundamental part of this game...... Perhaps the Repeat Mechanic should be on the top of the QA testing form?

Especially this raid.. COme on... you NEED to farm the first 3 parts in order to build your raid loot.... Everyone who completed it now is Stuck.. Unable to continue their progression ontheir stuff.... Bad form.....

Kerr
02-06-2008, 12:31 PM
I've been suggesting they add testing timers in their QA process for Raids for the last three Raids.

Hasn't done any good. Three Raids in a row now broken due to ineffective timers.

Oreg
02-06-2008, 12:31 PM
Thread Repeating.....

The last three days have all had significant Thread repeating Bugs..... Being able to repeat too much or not being able to repeat at all....

Repeating the thread is a BASIC and Fundamental part of this forum...... Perhaps the Repeat Mechanic should be on the top of the QA testing form?

Especially this thread.. COme on... you NEED to farm the first 3 pages in order to make your point.... Everyone who completed it now is Stuck.. Unable to continue their progression ontheir stuff.... Bad form.....


Sorry Impact - Couldn't resist ;)

parvo
02-06-2008, 05:21 PM
Raid Repeating....

The last three modules have all had significant Raid repeating Bugs..... Being able to repeat too much or not being able to repeat at all....

Repeating the raid is a BASIC and Fundamental part of this game...... Perhaps the Repeat Mechanic should be on the top of the QA testing form?

Especially this raid.. COme on... you NEED to farm the first 3 parts in order to build your raid loot.... Everyone who completed it now is Stuck.. Unable to continue their progression ontheir stuff.... Bad form.....

Careful. You're starting to sound like ole' crochety parvo. hehe... Tomorow I start a thread on things I love about DDO.

parvo
02-06-2008, 05:24 PM
I've been suggesting they add testing timers in their QA process for Raids for the last three Raids.

Hasn't done any good. Three Raids in a row now broken due to ineffective timers.

I'm not sure why, but the process is really slow. We begged for a public test server forever before we got one. I don't think anyone will argue that change was bad for the game. What I don't get is why this MMO hasn't learned some of the good things from others. There's a pretty good history of things good for MMOland.

TechNoFear
02-06-2008, 06:01 PM
I'm not sure why, but the process is really slow. We begged for a public test server forever before we got one. I don't think anyone will argue that change was bad for the game. What I don't get is why this MMO hasn't learned some of the good things from others. There's a pretty good history of things good for MMOland.

Ummm....

Didn't lots of people find exploits (how to bypass raid timers) and NOT report them, so they could expoilt when it went live?

Didn't lots of people get prematurely bored because they had already run the content on Risia. Then zerg everybody else through the new content first day it was released?

Did all the bugs reported on Risia get fixed before release?

I don't think Risia has helped much.

Kerr
02-06-2008, 06:41 PM
Even ignoring the Risia problems.. this has happened THREE TIMES NOW. It doesn't take all that much effort to add three checkboxes on their QA forms..

Test 231: Beat Raid
Test 232: Speak to Raid giver to test if timer is applied
Test 233: Wait 2 days 18 hours and talk to Raid quest giver again to repeat.

Vormaerin
02-06-2008, 09:54 PM
Yes, that sounds simple. The real problem is that QA probably doesn't have the same build 3 straight days and quest setting variables are getting lost. Also, QA needs to run the quests more often than once every three days, so they probably bypass that alot even if they do have the same build going.

Of course, given that its a recurring problem you'd think they'd make a specific set up to test it. On the other hand, the bug may have been introduced in the last build and they thought they'd already tested that. QA is basically a thankless, doomed enterprise...