i don't think that's really an accurate idea, old games also had tons of bugs and glitches
like in super mario bros. 1 for example, the spinies (the spiky balls that lakitu throws from the clouds) were not meant to fall straight down, there's code that took mario's speed into account and tossed them to predict where mario's gonna be ± random value, but one wrong function call erased that value to 0
and the whole "minus world" thing, which you can only exit by resetting the game
the 1st gen pokemon games are famous for their bugs, some of which can wreck your save data -- heck, even speedrunners don't want to touch the japanese gen1 games because of how easy they are to exploit!
sonic 3 was split into 2 games bc they couldn't miss a deadline for a mcdonalds promotion, and the game had unfixed bugs literally described in the manual as if they're traps set up by eggman
donkey kong 64 required a memory expansion pack because (guess what) there was a memory leak the devs couldn't fix in time -- players literally had to buy more ram
none of these problems are new, and usually the developers would love to fix them all and ship a bug-free game -- it's the execs who overwork them, push harsh deadlines, etc.
i don't think that's really an accurate idea, old games also had tons of bugs and glitches
like in super mario bros. 1 for example, the spinies (the spiky balls that lakitu throws from the clouds) were not meant to fall straight down, there's code that took mario's speed into account and tossed them to predict where mario's gonna be ± random value, but one wrong function call erased that value to 0
@ZySoua @drq
i don't think that's really an accurate idea, old games also had tons of bugs and glitches
like in super mario bros. 1 for example, the spinies (the spiky balls that lakitu throws from the clouds) were not meant to fall straight down, there's code that took mario's speed into account and tossed them to predict where mario's gonna be ± random value, but one wrong function call erased that value to 0
and the whole "minus world" thing, which you can only exit by resetting the game
the 1st gen pokemon games are famous for their bugs, some of which can wreck your save data -- heck, even speedrunners don't want to touch the japanese gen1 games because of how easy they are to exploit!
sonic 3 was split into 2 games bc they couldn't miss a deadline for a mcdonalds promotion, and the game had unfixed bugs literally described in the manual as if they're traps set up by eggman
donkey kong 64 required a memory expansion pack because (guess what) there was a memory leak the devs couldn't fix in time -- players literally had to buy more ram
none of these problems are new, and usually the developers would love to fix them all and ship a bug-free game -- it's the execs who overwork them, push harsh deadlines, etc.
@ZySoua @drq
i don't think that's really an accurate idea, old games also had tons of bugs and glitches
like in super mario bros. 1 for example, the spinies (the spiky balls that lakitu throws from the clouds) were not meant to fall straight down, there's code that took mario's speed into account and tossed them to predict where mario's gonna be ± random value, but one wrong function call erased that value to 0