Print

Please login or register.

1 Hour 1 Day 1 Week 1 Month Forever

Login with username, password and session length

[Omega Tyrant]

I recently had a A100 run that was going amazingly well. When I was on the 89th floor, about to advance to the 90th while still in perfect shape, my laptop suddenly turned itself off due to low battery, without having gave me the low battery warning beforehand. With no save protection for such circumstances, that run is now gone, with absolutely nothing to show for it.

As such, would it be possible to implement a feature, where if Doom RL is abruptly ended while still in play, the game will do a quicksave of where you were before the game turned off? Seeing such deep runs just vanish like that is discouraging.

[Kornel Kisielewicz]

Problem is that DoomRL would have no way to detect whether your power went off or you did a force close on it.

[Game Hunter]

Problem is that DoomRL would have no way to detect whether your power went off or you did a force close on it.

I don't know if we need to make that distinction. Obviously if it's an unexpected shutdown (i.e., power outrage without backup) then nothing can be done, but if it's a "this computer's out of power, let's start shutting down" automatic process then it should be able to do an autosave all the same. I also doubt there are enough people who use force-close to restart the game to consider the negative side-effects.

So I guess I don't see any problems with adding it. It'll be more useful once "save anywhere" is implemented, at least.

[Kornel Kisielewicz]

Game Hunter, you didn't get the point :) -- you're about to die? Do a force close and replay the level from the save point. Unless we had save anytime, and the game would save on every move, this would be an exploit to save your character.

[Game Hunter]

Do a force close and replay the level from the save point.

Oh right, derp. Change that "more useful" to "only workable" from the previous post, then!

[thelaptop]

How about storing the save file (for the previous level) plus some transaction-log-like thing that stores the current seed and a transaction record of moves taken to replay?  In short, we use save points as a "committed" transaction, and then use redo-logging to recover the lost state for the current level.

Maybe incorporate a query to the OS on how long it has been up compared to some checkpoint in the move transaction log.  =P