Fix the bug that actually matters?

[ChrisRedfield2]

QA teams always get a lot of flack in situations like this but it's entirely possible they knew and reported this bug but higher ups decided to push through anyway.

That's why QA sucks but that doesn't mean QAers suck. The responsibility ultimately lies with their managers and the people controlling resources. It ultimately boils down to the insane lie that they're investing heavily back into this game and are sparing no expenses, because fundamentally it's a money issue: I wouldn't be surprised if they fired half their in-house QA team or sent them off to other teams.

[ChrisRedfield2]

OINK OINK OINK

Sorry what?

[Stormpeaks]

Sorry what?

LMAO

/10char

[Thurmnmurmn]

It's clear people don't care about the why this is happening. They just want to complain for the sake of complaining since we all know devs don't look at the forums.

[Atelier-Bagur]

It's clear people don't care about the why this is happening. They just want to complain for the sake of complaining since we all know devs don't look at the forums.

Its kinda obvious at this point as the people who argue for the bug are non-raiders anyway. I would've just said "please fix this asap" and then see that they've addressed it for its fix this week and leave it at that, but people enjoy hearing the sound of their own farts and want to pass it around so that everyone can deal with it.

[BRVV]

It's clear people don't care about the why this is happening. They just want to complain for the sake of complaining since we all know devs don't look at the forums.

I did but i keep getting conflicting statements. People claim the reason for bug X is Y. When i or someone else mentions something like "that should have been caught in testing", a post like yours follows and then a movement of the goalpost where apperently the reason for X was actually Z all the time. I thought people knew stuff from like dev infos but it seems they make stuff up. Probably reasoning until everything ends in "something something spaghetti code; nothing they could do"

[Thurmnmurmn]

I did but i keep getting conflicting statements. People claim the reason for bug X is Y. When i or someone else mentions something like "that should have been caught in testing", a post like yours follows and then a movement of the goalpost where apperently the reason for X was actually Z all the time. I thought people knew stuff from like dev infos but it seems they make stuff up. Probably reasoning until everything ends in "something something spaghetti code; nothing they could do"

Honestly I think the best possible explanation was from daeriion on page 16.
But your prob right, people make stuff up a lot. Sometimes intentional, sometimes not.

[BRVV]

Honestly I think the best possible explanation was from daeriion on page 16.
But your prob right, people make stuff up a lot. Sometimes intentional, sometimes not.

Liked and agreed.

Let's hope they can fix the bug for the next hotfix.

[VelKallor]

It's a creepy, and obsessive fetish that some people have to try and take some form of high-ground in a forum argument.

It is indeed. Kind sickening to a point. This is the kind of crap stalkers get up to.

Because nothing comes up when you search for your name?

Which then begs the question as to what the hell were you doing looking for it in the first place?

Am I in your static?

No.

Am I on your server?

No.

Am I any savage or ex groups you may be in?

No.

Then what damned business is it of yours poking your nose in there to begin with?

[Mosha]

Which then begs the question as to what the hell were you doing looking for it in the first place? Am I in your static? Am, I on your server?

No?

Then what damned business is it of yours poking your nose in there to begin with?

Because it's a public website and its funny.