Normally I would not, but 2.0.4 has been live long enough for us to feel pretty confident about it, and we didn't want to keep this many valuable fixes hidden behind the beta wall forever. We'll of course monitor how it goes. There are still things we want to fix (in game dev, there's ALWAYS more things you want to fix), but the bigger a patch gets, the longer you guys have to wait and the more difficult testing it becomes, because of all the moving parts. We've got a good milestone here.
To be honest I'd be happy to wait, for a month or more if necessary, as long as the bugs get fixed. At least finish the Scaling feature in the settings that has been "experimental" for so long and has enough problems to force the Mod community to create UI mods simply for resolution changes. In my opinion "pretty confident" is a LONG stretch from "Fairly Certain", and both are further still from "Completely Stable", most people are subscribed to the Beta anyway because of the existing bugs so it's not really "hidden behind the beta wall", just keep working on those bugs a little longer and I doubt anyone will care much as long as the bugs get fixed. "There are still things we want to fix..." So please by all means go ahead and fix them. "A good milestone" should never be a reason to push half-finished fixes, it should be about finishing the fixes and making sure it all works, let the event create the milestone, not just a production schedule.
I propose you look at the production methodology and find a system that relies on product testing to create effective solutions, iterations based on full fixes and move away from this date driven development where you set a date and then race toward it as best you can but miss things along the way because you're already starting in a hurry. Deadlines are great in some projects but in this scenario I believe you are doing your product more harm than good. Please drop this timed release profile and focus on stable iterations instead, we WILL wait, gamers will always wait for a good game, but they won't always struggle on with a bugged product in the hopes it gets better down the track. Actually that's the biggest reason I stopped supporting EA, development time-frames had them pumping out buggy and broken games and not providing effective patches because of timed support for the product, after a month or two they move to another project.
I love Stellaris as it is exactly what I've wanted in 4X for a long time, but at the same time I hate it because every time I think I can play a full game there's another bug which breaks the gameplay at some point, like the AI which is horrible, bad, atrocious, ridiculous, flawed, broken, bugged oh and did I say horrible? Last game I played I wanted a war to end between two AI so I could adjust my fleets to combat one of the empires, but the winning empire sat there occupying the enemy systems and refused to actually invade the final world to gain a definitive win, there was no reason for the hold up, the last planet had 3 defending armies, they had 17 attacking armies in the next system, but after 120 years and 100% war exhaustion on both sides they still wouldn't end it by simply landing those 17 armies on that last planet. That scenario wouldn't happen in any reality, but it certainly happened in Stellaris, that's not Artificial Intelligence, it's Artificial Stupidity. I did end up just invading and utterly steamrolled the "winning" empire despite them having more territory and larger fleets because they were weakened by the war exhaustion they faced in the other war that they refused to end. Had they won their war I was ready to seek an alliance to face others because I knew they'd be more powerful, but because they wouldn't move I decided they were weak and punished them severely.
I'm not meaning to have a go at the Dev team or anything, but there are bigger problems here than timed release patches can fix, please just focus on the AI alone for one patch, then the balance for the next and so on and release them when they work, not just when the date says they should be out or you'll compound the problem with even more errors. I wish the Dev team well and only want to see you succeed.
Last edited: