That's where there's a difference between a small day one patch and a "fix it in post" mentality.CaitSeith said:Are you saying that the games get packaged and shipped intentionally with flaws, so the devs have something to do? Because the only reasons for games to require huge day-one patches is that they are released full of flaws or incomplete (something that shouldn't be accepted in certified games)Lightknight said:The game has been packaged and shipping for months before release. It would be silly to think that there wouldn't be patches or any dev work performed during those months.
Even before games go gold, the process of console certification takes months, and is expensive. When a build is deemed sufficiently bug free, content complete, and up to publication standards, it gets sent for certification. Certification is a console maker's way of saying if the game meets the console's stability/functionality requirements, and they might catch additional bugs (usually associated with nuances of that console's software, like trophies or achievements). However, cert isn't focused on glitched quests - it's focused on how the game operates with the console's systems. During that time, devs don't just sit around and wait for an answer. They keep working, and keep testing, possibly finding weird bug behaviors and odd connections in the game. If they find bugs, they might pray that they don't get found by the cert team, and still work on fixes. If the game passes cert and goes gold, those changes aren't discarded. They're made into a patch to be fixed at release. The disk still meets minimum quality standards, but it could be improved through additional fixes.
Cert also isn't the best way to gauge quality, since they mostly test integration and general standards - things like online integration, message functionality, share features, etc. Keep in mind Ride to Hell: Retribution passed certification.
A 2GB patch might be hundreds of minor bug fixes found during the cert time. Nothing that would make you fail cert, but maybe audio glitches, disappearing npcs, the like. Usually when you see bigger patches it's due to textures or audio, which have large file sizes. A minor audio bug can make a single issue patch much larger than expected, but it's still a quality of life improvement. It's not that games are intentionally released with bugs to keep devs paid - it's that games naturally have bugs from the strangest of conditions, which are constantly looked for after certification, during manufacturing, and after release - all of which imply a point where you can't modify the on-disk content anymore.
This is all an improvement over the Atari days where a game breaking bug gets listed as a feature in the manual, since they can't afford to remake the cartridges.