Unless you expect paradox to be hiring 50,000 testers what do you really expect them to do? They could test and test and test for 2 years to make sure there are no bugs.
Ah, yes. Shoving in a false dichotomy of releasing a game with no bugs at all (which, given how no one asked for that also makes this a straw man) and releasing the game with even the more serious bugs (which is what @
PhilzuNeide considers their examples to be) still in is truly a masterpiece of argumentation.
The bug you bring up could easy be the result of a change to make sure the AI save some money for war or some other thing that isn't buildings. This could have been introduced in the release candidate after fixing an issue of the AI going bankrupt as soon as a war starts.
But the AI doesn't save money for war anyway. It merrily goes bankrupt during a war by using boats to travel just two provinces away.
It's super easy to miss that the AI isn't buying buildings if you don't have time to play 100 years to notice without checking the same AI counties over and over.
You know what's not super easy to miss though? AI not using matrilineal marriages. There are literally female rulers among the suggested ones. Including an unmarried and childless Matilda of Tuscany. Launch 1066 game as anyone else but Matilda and then observe her. Within a minute she'll marry patrilinealy with no regard for preserving her dynasty. Each time.
And, in doing so, The AI's flat out ignoring the game over condition of Crusader Kings. Which means the AI is completely botched. At which point your excuse of "but what if it was introduced only in the release candidate built" excuse no longer flies.
One person could figure that out in just a few minutes of testing. And what makes it even better is that CK3 has an inflated amount of female rulers thanks to knights (most of whom are landed characters) dropping like flies and even the 1.02's succession bug that made mothers the primary heirs of their children. Making it all the easier to spot the issue.
Again you don't know how many bugs there were before and the game is not trash given the amount of people who are playing it happily. I never said Dread and talent trees were bugs, they are balance issues but work in the same way in that each change has to be tested and each change can effect and break something else.
You don't know either, so why bring it up to put yourself on a pedestal? And the bugs extend to the core gameplay loop of CK3. That some people turn a blind eye to that doesn't negate their severity, nor excuse Paradox for releasing the game in that state.
Which fundamental mechanic is broken that they should have known about before release that you know for a fact wasn't created in the release candidate?
If a FUNDAMENTAL mechanic gets broken it doesn't matter if it was done so by a release candidate built. There's more than one release candidate built in each software release. Just slapping "lel release candidate" is no excuse for breaking fundamental mechanics. It's a reason to make
another release candidate build in which
it isn't.
Also, as was the case in the paragraph above, you don't know for a fact that such bugs weren't there for months either (it'd truly be a surprise coming from a company with such stellar history of QA) , so you sticking to that tangent like glue is utterly ineffective.
Seriously guys tell me, what's better delaying the game's release so that some players don't get as angry as you guys seem to be (and there will always been some whenever the game is released) or delaying the game and pissing off the other 90%?
Because out of all years of human history it's 2020 when people would have had oh, so much trouble being understanding about a game getting postponed. Just look at Cyberpunk 2077. Oh, wait, that's made by a company that actually deserves goodwill from the playerbase so maybe it's not the fairest of comparisons.
And yes, delaying a game's release when your AI is so busted it completely ignores the game's game over condition whenever it has a female character as a ruler or a heir is the better choice than releasing it in such a sorry state.