Ideally, there’d be no updates at all. Getting the full, finished game right from the get-go would be awesome.
I know, I know. Things are not that easy and shit, well, shit happens.
If updates are unavoidable, let’s at least make them count and add weigh.
At launch, devs are basically testing the waters to see if their game can survive among thousands of others. You work your tail off for years, and the last thing you want is for it to flop immediately (basically marriage in a nutshell). That’s why a flexible initial release with updates that actually cater to the fans makes sense. As long as it’s a steady pace of 'good' content and not just low-effort slop.
On top of that, we have to consider the genre—if it even qualifies as a 'game' in the traditional sense. Each type of project benefits from a different update schedule. For me:
- Arcades - Constant and fast updates that address the gameplay (focus of this type of game) and slower ones with the "rewards"
- Story-focused - Since these kinds of games don't usually need system patches—thanks to established platforms—slower updates, even in an episodic or chapter-based format, are ideal.
- Fap-Fest - Quantity is its own quality here. Since variety is the name of the game, I'm all for huge, frequent content drops to keep things fresh.
Ultimately, it depends on the players relationship with the game. That relationship is shaped by the type of game it is and the community surrounding it. The developer should probe to see, case by case, what works.