I haven't read about the specifics of this Tetris crash, but usually what happens with these old games is that memory is very tightly packed, imagine you have a small version of Tetris that has 3 digits XYZ where X is the speed of the game, Y is the amount of lives and Z is the level you are in, so for example if you're in speed 5 with 8 lives on level 7 the number would be 587, if you go up one level it becomes 588, now on that example if you're on speed 9 with 9 lives on level 9, i.e. 999, and you go up one level the number becomes 1000, but because only the 3 last matter you're now on speed 0, with 0 lives on level 0, since speed zero means nothing moves you crashed the game.

Again, this is not exactly what happened here, but probably something similar where increasing a number overflew to the next one in memory and that caused some weird behaviour.

[–] AnUnusualRelic@lemmy.world 1 points 10 months ago (3 children)

Yes, I completely understand that those games that ran on a shoestring can easily crash when some values are exceeded. What puzzles me is that I would have expected the player to be annoyed at his game crashing (of course simpler games on dedicated hardware didn't really get to crash all that much back then, so maybe that was seen as an achievement of sorts).

I suppose it's my lack of exposure to the console side of things, having gone from 8 bit PCs to the ubiquitous intel machines without ever using one of the dedicated gaming devices.

[–] calculuschild@lemm.ee 6 points 10 months ago* (last edited 10 months ago)

Tetris doesn't really have an end. It just keeps going. So this is a very specific crash where if you get far enough into the game, it can't keep up with the player any more. You "beat" Tetris by playing so well you make the game break.

This is similar to getting pacman to crash by beating level 255 at which point incrementing the level goes past what can be stored and the data gets corrupted.

load more comments (2 replies)

load more comments (7 replies)