How can either of us answer that question?I don't see it that way. The pace of fixing things is glacially slow. Like, no one more turn button yet, no re-naming cities at launch? How on Earth was there "no time" to include that stuff at launch?
But, to me, the pace is actually pretty fast. I didn't expect the number of patches we've seen in the weeks and months following release. What large studios patch a cross-platform game multiple times in a month or so? Age of Empires IV didn't see this (quite the opposite, in fact). I don't buy a lot of games these days (certainly not on release), so that's my off-the-cuff example.
Why do you think it's so slow? Is it because we've seen modders experiment with all sorts of neat things, and therefore developers should be able to go faster? Is it your own experience? I'm guessing here - not trying to put words in your mouth.
This feels both very uncharitable and completely speculative.In the case of one more turn, they're obviously reserving that to hype up a later patch so it seems like a bigger deal and generates buzz.
Interesting.I don't think moving Right to Rule back is "prioritizing". I think it's them needing to let quarterly results process so executives can make decisions on stuff. In some ways, not releasing Right to Rule early is false advertising, since many people already paid for it. To be fair, they didn't announce exactly when it would release.
So you'd be happier if they released more paid DLC when they originally stated it would be released, even if that meant that the post-launch support timeline suffered for it. Because I think that's the thing folks don't understand. People think it's ready to go. In some cases, that this was content cut out of the main release, to be sold, intentionally.
What if that isn't the case? What if they're still working on it, and it wasn't ready at launch (like most post-launch DLC)? How can we know which is which?
Why not?It's just, these bare bones civs that ship with additional bugs than what there were at the start can't possibly take so long to program.
Why not? We had Covid in the middle. Firaxis had layoffs in that same time (most of the industry did, and Firaxis lasted a long time to avoid them compared to many I know).That's a good question. I wouldn't believe that that's true unless the publisher meddling was insanely chaotic, with one demand one month and a new demand the next.
Typically, "publisher meddling" deals with rushed release, predatory pricing. Well, they had 7 years so I can't believe they didn't have enough development time from the publisher side of things. I mean, there was no ability to rename your cities at launch! That can't be the publisher rushing them with 7 years of dev time.
I guess I'm asking the same question a lot - sorry about that.
Glassdoor is infamously, regularly, not evidence. It can be, it also isn't necessarily factual. One of the reasons I don't use it myself (that said, I barely tolerate LinkedIn, so).The Glassdoor post is actual evidence.
But regardless, the thought experiment were if evidence were forthcoming, a la a well-researched piece from Schreier or the like. So you should bake that assumption into the answer.