Wouldn't it be great to keep a backlog of quicksaves to fall back upon later during play? It would certainly be much more effective than even the autosave function at being current and at points where the player deems important to save at.
Inb4 save states are a hassle to create compared to quicksaves and is intended to be more permanent.
Quicksave history.
Re: Quicksave history.
First a small warning quick saves/savestates are inherently less stable then in game saves, are corrupted more easily, and can cause more odd issues. They are great for temporary saves when you are not able to use the in game save menu.
With that warning aside how about the ability to incriment your save slot (like with most emulators do). I am not sure if DraStic ecen has a limit to the number of savestates you can have in a single game, but if Lordus added to the ingame menu (the radial menua) save slot up and sown buttons would that do what you want? It would allow you to make as many savestates as you wanted with out having to go to the options screen and you could incriment each by 1. You could then even use the load function to see where each was saved.
With that warning aside how about the ability to incriment your save slot (like with most emulators do). I am not sure if DraStic ecen has a limit to the number of savestates you can have in a single game, but if Lordus added to the ingame menu (the radial menua) save slot up and sown buttons would that do what you want? It would allow you to make as many savestates as you wanted with out having to go to the options screen and you could incriment each by 1. You could then even use the load function to see where each was saved.
-
Anduin1357
- Posts:14
- Joined:Thu Aug 11, 2016 3:58 pm
Re: Quicksave history.
It's still much more convenient to keep a backlog of quicksaves than to save and load to save state numbers even from the radial menu.
Even then, the radial menu idea does not replace the quicksave backlog idea.
A quicksave is stored with the press of a button. There is no slot to select and it is very quick. When the button to load is pressed, the most recent quicksave is loaded.
The entire backlog can be accessed via manage savestates.
Looking at the quicksave, an additional option under 'play' is labelled 'history' or 'backlog'. Selecting it brings you to a list of savestates that is the history of the quicksave. By loading a backlog quicksave, that quicksave becomes the most recent to the quickload.
The quicksaves that were made after the quicksave that has been backlog loaded is then marked a unique colour.
Even then, the radial menu idea does not replace the quicksave backlog idea.
A quicksave is stored with the press of a button. There is no slot to select and it is very quick. When the button to load is pressed, the most recent quicksave is loaded.
The entire backlog can be accessed via manage savestates.
Looking at the quicksave, an additional option under 'play' is labelled 'history' or 'backlog'. Selecting it brings you to a list of savestates that is the history of the quicksave. By loading a backlog quicksave, that quicksave becomes the most recent to the quickload.
The quicksaves that were made after the quicksave that has been backlog loaded is then marked a unique colour.