Afternoon chaps. I posted this over the road, which might explain things a bit more:
Hello!
Well I'm still not entirely 100% of what the issues with marathoning Missile Command are, but in short, there are regular risks of the game crashing at several points. The three main problems are:
1. Wave 256 - like most 8 bit machines, there is a "killscreen" of sorts on Missile Command. At wave 255, everything is worth 256 times it's normal value. At wave 256, the same thing happens, but you can't actually play the level. The game then restarts at wave 1, but you maintain the same score. Those two screens alone are worth 750,000 points if you play them through properly.
2. The bonus cities count. On marathon settings you are awarded a bonus city every 10,000 points. This count also has a "killscreen" - if you get to a point where you have 256 bonus cities in reserve, that count also resets to 1.
3. Scoring 810,000 points. Every time the score shows 810,000 points, you are awarded 176 bonus cities. This is the more well-known bug in the game. (This is why at certain points, you will see Victor killing off his cities and not actually playing, because he has too many cities in reserve, and has a score that is about to trigger the killscreen and the 256 bonus cities kill).
So, imagine being at the killscreen at wave 256, and scoring enough points at that wave to trigger the 810,000 point score, and at the same time rolling the bonus city count, and triggering the killscreen back to wave 1. As I understand it, it's a combination of these things happening at the same time will reset the game. You also have smaller issues. Ignore the scores for a moment - imagine you have 85 bonus cities in reserve. You hit 810,000 points and are awarded 176 bonus cities as I mentioned above. How many bonus cities do you now have? The answer isn't 261. You will actually have 5. So you see there's a lot to think about, and a lot that could end your game.
The fact is, once you become competent at MC you can marathon it. I'm uncomfortable with the fact that a computer aid is being used to manage the game and to keep track of where you are if you want to do it seriously like Victor is doing here.
What's even more bizarre, is that the bugs are corrected in v3 of the ROM which was found a couple of years ago. For some reason, no one seems to have made an attempt using those roms.
As for playing marathon settings like Victor is doing, I don't know really. Stay awake, get through a wave (without worrying about what your score is or whether you lose cities), press a button to keep count of where you are. Stay awake, get through a wave. Stay awake. Rinse and repeat. Rinse and repeat. Rinse and repeat.
It's an admirable achievement, but is it authentic? Using assistance from a computer, breaking down the game in this way to manage an attempt? It all feels a bit artificial to me and not quite in the spirit of what classic arcade gaming is all about.
But there's no point breaking it down. Victor's a nice guy, and he's trying to play for 100 hours, and has got quite a bit of exposure for doing what he's doing. Good luck to him I say.