Fix the bug that actually matters?

[ChrisRedfield2]

....

No one disputes that bugs have always existed. The point here is that QA is slipping. Ungarmax was barely used by anyone, was treated as a meme and was basically irrelevant other than for a few dumbasses who tried to do UCoB with it. The UCoB packet bug, while unfortunate, did not impact that many people compared to the impact of TOP, Abyssos, and Caloric. For many raiders, EW is the first time they\\'re actually running into these bugs themselves since A6S, and not just hearing about them. And I see that you didn't mention any bugs from ShB, because there honestly were only a few. The encounter variability bug causing quick enrages in w1 E4S was one of the worst offenders in ShB but that seriously pales in comparison to what we have now in Endwalker. That was also the only major bug I remember from ShB. ARR and HW were buggy messes, but SB and ShB had pretty good QA. Now EW has regressed, severely, in that regard.

Blaming increasing complexity and JP work culture is fine but that's literally pointless to the end consumer. I'm sorry but no one is interested in an explanation of why they suck at QA now (beyond a curiosity as to how these firms operate). If a burger joint makes burgers that give you diarrhea, and they start to blame that their food quality assurance systems are not updated, no one gives a shit. You'll still be investigated by the FDA. In no other industry does ineptness excuse bad QA. For some reason for video games people like you try to "empathize" with the company. For what? We are the consumers here. We are not McKinsey consultants hired to understand why their management structure needs a revamp. In what other industry is the consumer supposed to excuse poor products because their organization hasn't kept up with modern business practices? You are just rationalizing away poor behavior.

[Valkyrie_Lenneth]

Rationalizing away poor behavior.





Spends most of his time trolling the forums and rationalizing it as "I'm not doing anything"

[Kes13a]

No one disputes that bugs have always existed. The point here is that QA is slipping. Ungarmax was barely used by anyone, was treated as a meme and was basically irrelevant other than for a few dumbasses who tried to do UCoB with it. The UCoB packet bug, while unfortunate, did not impact that many people compared to the impact of TOP, Abyssos, and Caloric. For many raiders, EW is the first time they\\'re actually running into these bugs themselves since A6S, and not just hearing about them. And I see that you didn't mention any bugs from ShB, because there honestly were only a few. The encounter variability bug causing quick enrages in w1 E4S was one of the worst offenders in ShB but that seriously pales in comparison to what we have now in Endwalker. That was also the only major bug I remember from ShB. ARR and HW were buggy messes, but SB and ShB had pretty good QA. Now EW has regressed, severely, in that regard.

Blaming increasing complexity and JP work culture is fine but that's literally pointless to the end consumer. I'm sorry but no one is interested in an explanation of why they suck at QA now (beyond a curiosity as to how these firms operate). If a burger joint makes burgers that give you diarrhea, and they start to blame that their food quality assurance systems are not updated, no one gives a shit. You'll still be investigated by the FDA. In no other industry does ineptness excuse bad QA. For some reason for video games people like you try to "empathize" with the company. For what? We are the consumers here. We are not McKinsey consultants hired to understand why their management structure needs a revamp. In what other industry is the consumer supposed to excuse poor products because their organization hasn't kept up with modern business practices? You are just rationalizing away poor behavior.

technically, since you and your alts do not pay you are not a "consumer" neither are you a "customer"

you may somehow play the game without paying, and post on the forums without paying, but saying you do not sub, does not place you in the same boat as the rest of us. you are the crackpot outside of said burger joint screaming that meat is bad for you that no one cares about.

[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.

[Shinkuno]

They stated the results were valid, it was just an error from moving the result to the end user where a disconnect happened.

So on the serverside the results were valid but then the error happened on the enduser screen? So in theory someone should have gotten a house right? You dont see how that makes no sense right? If the results was 0 on the server but while sending it to display on the client it got error'd to 0, then someone would have gotten a house without even knowing. But that wasnt the case, so the result was 0 on the server aswell, and in that case no it wasnt a valid result cause 0 shouldnt roll. Thats just using common sense nothing to do with conspiracy

[Valkyrie_Lenneth]

So on the serverside the results were valid but then the error happened on the enduser screen? So in theory someone should have gotten a house right? You dont see how that makes no sense right? If the results was 0 on the server but while sending it to display on the client it got error'd to 0, then someone would have gotten a house without even knowing. But that wasnt the case, so the result was 0 on the server aswell, and in that case no it wasnt a valid result cause 0 shouldnt roll. Thats just using common sense nothing to do with conspiracy

No, the server rolled a number but it wasn't passed properly to the system that handles granting the houses. So that system had a 0 but the system that generated the winner worked properly.



Those lottos didn't end, they extended the results period until they were able to fix the disconnect and the winners got their house.

[ChrisRedfield2]

OINK OINK OINK

Sorry what?

[Stormpeaks]

Sorry what?

LMAO

/10char

[BRVV]

You don't test code in production.

Yes. Never claimed otherwise. You DO test however if your multi-server setup of a massive project spanning literal continents has servers that can actually communicate with each other

#worksOnMyMachine

[TaleraRistain]

Not at all... imagine if during a transaction error your exception handling would be not abort the transaction, but removing the money from the sender and giving 0 to the receiver.

The exception handling for this case would be either reroll or set it to 1, which still unfair at least noone loses out and noone would even know if something went wrong cause 1 is a valid result after all.

Could their actual exception handling code set it to 0? Yes. Would i call it exception handling? No, cause you purposefully let through a bad result.

How exactly is the server that isn't doing the rolling supposed to do a reroll? The lottery server was doing the rolling. It had a valid result. That valid result was not being passed to the instance server due to a bug and in the absence of a result the code was displaying 0 for the end user.