by Ciantic on 5/26/24, 10:01 PM with 7 comments
by stevage on 5/27/24, 12:33 AM
And the team ratio of mostly creatives and a small number of junior devs is pretty baffling.
Oh and the final estimated price tag, of $60m?! Wow.
by Ciantic on 5/26/24, 10:07 PM
- Trying to employ mostly junior engineers
- Not allowing the new team to talk to the KSP 1 developers
- Not paying enough to keep senior engineers
- Re-using old codebase and coding themselves in the corner and couldn't fix bugs that old game had
Re-using old codebase wouldn't necessarily be bad if they were familiar with it, but from what I understood nobody was. They weren't able to move fast with it.
The list probably goes on, and I didn't take notes, but I found it interesting.
by md5wasp on 5/27/24, 3:59 AM
So I was naturally extremely excited for KSP2, but all-along I had a strong feeling this would happen. What's sad to see is that it's not just a second-system effect of being too ambitious, which was what I was assuming would cause issues, but an even more pathetic failure than that.
The joy I get from games has a really wide variance, and barely any relationship to the actual amount of money I spend on the game. I'd pay $1000 for a truly good KSP2, yet all the games that would actually _let_ me spend $1000 are shallow skins over gambling.
by KerrAvon on 5/27/24, 1:59 AM
I hope at some point they stop enshittifying things, but I don’t know how that happens without government regulation.