I’ve worked on a bunch of games and they’ve all left me with different feelings and memories about the job of QA. One of my most recent titles was a large (200+ team) action game that was a critical and commercial catastrophe when it was released.
The worst thing about it was sitting there in QA seeing it all falling apart. You could see that the vehicles were no fun, that the shooting was awful, that the weapon balance made no sense, and the entire progression system was laughable.
You could see it was slow, ponderous and plodding and you just knew it was going to be a total disaster and all you can do is submit suggestion bugs saying “The general feeling in QA is that the weapon is, at the moment, significantly above the average in terms of killing potential,” only to have a one word response of ‘no’. They say no because they have the numbers for all the guns and can see that they’re obviously balanced just fine.
The math is right there! So what if as soon as you pick up that gun your K:D goes from 4:12 to 50:3.
The numbers show that it’s fine. It’s just… fine.
Imagine standing on the side of a railroad track. You can see this giant train speeding toward your best friend and he’s just standing there looking at the train like it’s some sort of alien thing they don’t recognise. You want to pull your friend off the tracks and save him and you can even see how you would do it, but all you can do is whisper.
“There’s a train coming. Get off the track. There’s a train coming and it’s going to kill you.”
Your friend puts their fingers in their ears and says, “Lalala I’m not listening to you.”
And then the train hits, your friend explodes and everyone loses their job.
Fitocracy: Join us in the SE++ group!
XBox LIVE: Bogestrom | Destiny
PSN: Bogestrom
To be fair, the job of a QA person isn't to tell the game designers how to do their jobs. It's to find broken things.
Well the example in the story is a broken thing. QA is not just limited to technical glitches, design decisions that break the game should be expected to be found as well. If your devs/designers just close their ears when you point out a weapon or a certain skill combination or whatever is overpowered and breaks the game then they're bad. Problems like that should be fixed before ship so then you don't have people scared away from the game due to everyone using that one weapon and destroying everyone else. Coupled with the cost and time it takes to issue a patch on the consoles, nipping stuff like this beforehand can literally save tens of thousands of dollars, if not hundreds.
0
Options
HenroidMexican kicked from Immigration ThreadCentrism is Racism :3Registered Userregular
To be fair, the job of a QA person isn't to tell the game designers how to do their jobs. It's to find broken things.
Testing the balance of the game with all the rules applied seems like it would be something they do, actually. "Hey this gun is actually kinda cheezy and ruins the game progression" seems like something the sort of thing the QA team should report on.
My guess would be Modern Warfare 2, but that might be my gritty flashbacks to the old days of double-1887s talking. It definitely wasn't a commercial failure.
And everyone definitely didn't lose their jobs. Nothing really comes to mind, except for maybe games like Rogue Warrior that you forget about almost the second you see them.
0
Options
HenroidMexican kicked from Immigration ThreadCentrism is Racism :3Registered Userregular
To be fair, the job of a QA person isn't to tell the game designers how to do their jobs. It's to find broken things.
Testing the balance of the game with all the rules applied seems like it would be something they do, actually. "Hey this gun is actually kinda cheezy and ruins the game progression" seems like something the sort of thing the QA team should report on.
In all my experience with QA, balance is the game designers job. If a document says "gun should kill in 3 shots" but the gun kills in 4, then they can submit a report, but if the gun is intended to completely obliterate everything on the field, regardless of how over-powered, it's working as intended.
If it's a smaller company I suppose it could fall under QA's responsibility, though. I've never run into that.
It has cars, like grand theft auto, and the poor design made them decidedly unfun to drive. It had the gun problems, too. Plus the game put the company that made it out of business.
If the game was APB, then it's not like the devs saying "yes, we'll look into this" for situations like this:
You could see it was slow, ponderous and plodding and you just knew it was going to be a total disaster and all you can do is submit suggestion bugs saying “The general feeling in QA is that the weapon is, at the moment, significantly above the average in terms of killing potential,” only to have a one word response of ‘no’. They say no because they have the numbers for all the guns and can see that they’re obviously balanced just fine.
Was really going to save that train anyway.
0
Options
AthenorBattle Hardened OptimistThe Skies of HiigaraRegistered Userregular
I was thinking that this sounded like Rage, but I have not played it or APB, so I wouldnt know.
Oh yeah, Duke seems so obvious now. Although, again, I dunno if it lines up in terms of staff/budget, and I doubt it failed enough for everyone to lose their jobs. I mean, they knew they what they were putting out. It just kinda had to be put out.
0
Options
admanbunionize your workplaceSeattle, WARegistered Userregular
Posts
What a weird walking pose.
Well the example in the story is a broken thing. QA is not just limited to technical glitches, design decisions that break the game should be expected to be found as well. If your devs/designers just close their ears when you point out a weapon or a certain skill combination or whatever is overpowered and breaks the game then they're bad. Problems like that should be fixed before ship so then you don't have people scared away from the game due to everyone using that one weapon and destroying everyone else. Coupled with the cost and time it takes to issue a patch on the consoles, nipping stuff like this beforehand can literally save tens of thousands of dollars, if not hundreds.
Testing the balance of the game with all the rules applied seems like it would be something they do, actually. "Hey this gun is actually kinda cheezy and ruins the game progression" seems like something the sort of thing the QA team should report on.
Does it have vehicles?
http://trenchescomic.com/new-readers
In all my experience with QA, balance is the game designers job. If a document says "gun should kill in 3 shots" but the gun kills in 4, then they can submit a report, but if the gun is intended to completely obliterate everything on the field, regardless of how over-powered, it's working as intended.
If it's a smaller company I suppose it could fall under QA's responsibility, though. I've never run into that.
It has cars, like grand theft auto, and the poor design made them decidedly unfun to drive. It had the gun problems, too. Plus the game put the company that made it out of business.
Was really going to save that train anyway.
Compared to expectations? I seemed to hear it getting a lot of flak...
Then again, there's Duke Nukem Forever, which might also fit the criteria. That game could probably fill a few years worth of Trenches stories.
Rage got some flak, but it wasn't panned. Plus, it sold really well.
Duke Nukem Forever wasn't a huge success, but it was profitable (for Gearbox, at least.) Not a catastrophe.
I can't think of what else it might be