DRL > Requests For Features

Quicksave protection?

<< < (2/2)

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

Navigation

[0] Message Index

[*] Previous page