This OP is kinda disheartening, tbh. I feel like I'm being bamboozled with this "innovation means bugs" talk.
This would be those posts that keep getting deleted. Since you're basically saying that they don't do any QA testing. Which again is unfair to the QA team. They clearly have documented a lot of these bugs that we see, the outrage over the TODOs left in the code is a testament to this. At some point someone who doesn't work with the devs or the QA team says "This has to go out at X date". That is the person you should be angry at if you just have to blame someone.
I'm sure it'll be just as high-quality as the "extensive QA testing" they did before forcing this out the door.
Though the implementation is definitely shaky in places, and I can understand why some people feel upset, the core concepts underlying the game are now far stronger in my view
The QA surely does a good job, I believe him when he says that. The problem is most likely that they were forced to release anyway, despite having a stunning list of known issues. Yes this is pure speculation but still an educated guess based on my personal experience and reports from the gaming industry as a whole. Good work takes time, unfortunately those in the higher up positions do often have other priorities than quality products.
Fair points. And I agree about the distinctions.I pretty agree with your priority list, the only difference I'll made would be a distinction like 3 : major bugs, 4 major balance issues, 5 : minor bugs, 6 : minor balance issue.
However I think you're a bit ambitious asking for an interesting AI as that would be a huge amount of work and some bugs are way more urgent to fix (like crisis). A functionnal AI would be OK for now, I can wait for the next DLC for an interesting one.... IF the rest of the issues are covered, that's it....
The way you word it makes it sound as if you believe the people working on the game do not know what they are doing and fail horribly at it.
Count the following as my speculation based on personal experiences working in a completely unrelated company. While my work is not producing video games I still assume a lot of similarities regarding management of resources (workforce as well as money) and marketing decisions apply here as well.
I work in the IT department of our company and if things went my way, something would be done once it is done. Now comes the big BUT. While those above sometimes listen to our concerns, this isn't how things normally work. Often times deadlines are being pushed with little regard of what those who do the work can achieve in the given time frame. The result is neither good for the customer nor the programmer as shortcuts have to be taken.
The QA surely does a good job, I believe him when he says that. The problem is most likely that they were forced to release anyway, despite having a stunning list of known issues. Yes this is pure speculation but still an educated guess based on my personal experience and reports from the gaming industry as a whole. Good work takes time, unfortunately those in the higher up positions do often have other priorities than quality products.
Interestingly enough, I work in the Medicare/Medicaid insurance industry, where our biggest enrollment season ends on December 7th. Which means right after we spend 2 months enrolling every senior citizen in America in new plans, which they then get drop-shipped a ton of paperwork on that they invariably have piles of questions on... my entire industry, including private companies, state-run Medicaid agencies (like Departments of Health and Human Services) and the Federal Department of Health and Human Services... literally shut down for the holidays and we all go on vacation until January 2nd. We do it every year. And the world doesn't end.that's great, but tell us, if your company released a product that didnt work, would you all go on holiday? or would they get people to fix it first, and who would be in trouble over the complete mess of a release?
it is always interesting when someone in a similar field wants to compare notes on process, but doesn't want to say what would happen to them if they released a product in such a state at their company...
Interestingly enough, I work in the Medicare/Medicaid insurance industry, where our biggest enrollment season ends on December 7th. Which means right after we spend 2 months enrolling every senior citizen in America in new plans, which they then get drop-shipped a ton of paperwork on that they invariably have piles of questions on... my entire industry, including private companies, state-run Medicaid agencies (like Departments of Health and Human Services) and the Federal Department of Health and Human Services... literally shut down for the holidays and we all go on vacation until January 2nd. We do it every year. And the world doesn't end.
I like to think our industry is more important than a video game.
that's great, but tell us, if your company released a product that didnt work, would you all go on holiday? or would they get people to fix it first, and who would be in trouble over the complete mess of a release?
it is always interesting when someone in a similar field wants to compare notes on process, but doesn't want to say what would happen to them if they released a product in such a state at their company... because we all know heads would roll.
You're the one making wild analogies and comparing a video game to earth shattering consequences. If one of my carriers shipped a "buggy product" (which, ironically, both Humana and Blue Cross/Blue Shield of Michigan did this year) it would and could cause hundreds of thousands of people to have incorrect coverages that could LITERALLY cause life threatening coverage issues. Unlike Megacorp causing LITERALLY UNPLAYABLE stuttering.I am unsure where the comparison comes in? do people not get any medical services for that time? does most of the system not work while you are gone? your analogy has nothing to do with this release.
You're the one making wild analogies and comparing a video game to earth shattering consequences. If one of my carriers shipped a "buggy product" (which, ironically, both Humana and Blue Cross/Blue Shield of Michigan did this year) it would and could cause hundreds of thousands of people to have incorrect coverages that could LITERALLY cause life threatening coverage issues. Unlike Megacorp causing LITERALLY UNPLAYABLE stuttering.
I kid thee not: Blue Cross/Blue Shield of Michigan shipped an explanation of benefits book this year that had 2 pages with a line crossed out with a black sharpie. You want to talk about a "day one patch". I died laughing when I saw it.
Actually that would mean overtime for me. Which can also not be the solution for a failed policy in the first place. I thought my post made it very clear where I assume the cause of the problems. You are asking me how a situation should be handled, that shouldn't exist in the first place. What has to change in the long run is how such releases are treated. Either by allocating more time for polishing before release or releasing the content as well as the DLC as officially declared beta (which means - for those who are unfamiliar with the term - a feature complete but unpolished version) on an opt in experimental branch. The latter would be basically the same thing that happens anyway right now but would be more upfront with the consumer. I think I could live very well with it if I am informed correctly about what I am in for if I buy in at that point in time.