Then you haven't been in any kind of software development. It's completely normal to decide which are major bugs (crashes/freezes), which are minor bugs (game works but impedes/degrades gameplay in an aspect), and which are bugs that aren't going to be fixed (yet, or at all) because they are not relevant for gameplay/sales.
If you aim to fix all bugs for a patch/bugfix/release this is what happens: you never release. There's always more bugs coming in than you have time to fix, so you prioritize until you have something you feel can be handed out.
You set a quality goal which maybe says: "no major bugs, 5 minor bugs and the number of low priority bugs doesn't even count for the goal"
And sometimes even that is compromised by deadlines (there are monetary considerations to any software project, you know?)
And - gasp - even testers aren't infallible. Sometimes a bug just isn't found during testing.
So then you get a bugfix for a bugfix. It happens more than you think.
1- this bug is major, or they should rescale
2- this bug was known from players, reported to FDEV and acknowledged, thanks to the beta server
- - - - - Additional Content Posted / Auto Merge - - - - -
What he said. Software development is hard, I am sure they are doing the best they can.
And about ignoring beta feedback: From what I gathered on the forums they thought they had fixed the collision damage when they made the 1.1 release. Turns out it was not fixed. They have already pushed out 2 hotfixes in less than 24h. They seem to be working overtime to get things right. I dont know what an apology from the head honcho would accomplish so I think we should just give FD a break and let them do their work.
then it means they didn't even tested the code they pushed live or they would have at least noticed the bug was not fixed.
i do QA testing among many other things, be it hardware or software, when a new build come up, you run standard test suite, and you double check every point that the new build is supposed to fix (that is actually one of the many purpose of patch note, so that not only customers know what is changing, but other ppl working with you, later in the process, can act accordingly).
that is how QA works in real life
Last edited: