[kq76]

I find it hard to believe anyone would test this 51 times. Besides, the way you're testing this by "killing the game" is just asking for your file to get corrupted. There's clearly a safer, albeit more time-intensive, way to test it. I mean, how many times would it take most of us to be like, "okay, this is BS", 10? Maaaaaybe 20. No one is going past 30. 51 is, well, you pick the word.

That said, there was a game a while ago I was playing where my game crashed at the end because all the space on my HDD was full (I wasn't paying attention). Thankfully, I had backed it up just before that game and so I just replayed that game. Funny thing was though, the same guy batting 3rd for the opposition hit a HR in the 1st of both games. Now, he was probably the best HR hitter in the league and in the first game it was a 3-run HR while in the replay it was a solo shot, but I still thought, "huh, that's interesting".

Even if it's true, I wouldn't be too bothered if the way it goes about it is, as soon as the player comes up to bat, if the user doesn't interact in any way with the game, then it instantly figures out what the play will be. And if the circumstances aren't different then should the result? I get it, I'd prefer some random die roll aspect to it too, but I also believe in circumstances lead to results.

It could also just be the game having something in its code like, "oh, you think you're going to cheat by just shutting down the game, eh? well, we'll see about it." It wouldn't be the first time a video game did something like that.

Regardless, it shouldn't be too difficult for any of us to test this ourselves.