Option to Autosave after so many minutes

Feedback on past, current, and future development.
User avatar
vv221
Posts: 55
Joined: 03 Oct 2012, 12:27
Contact:

Re: Option to Autosave after so many minutes

Post by vv221 »

Digmaster wrote:How I've seen multiple autosaves implemented is to have each one numbered: EG "Autosave-3", and once the max number is reached to start over from the beginning.
It is a bit counter-intuitive.
As I see it, a better way to handle this when you already have five autosaves (assuming five is the max) would be the following:
delete autosave-1
rename autosave-2 to autosave-1
rename autosave-3 to autosave-2

save as autosave-5

This way, autosave-1 is always the oldest and autosave-5 the newest.
User avatar
silentthief
Posts: 456
Joined: 18 Apr 2013, 01:20
Location: Currently traversing the Ascadian Isles

Re: Option to Autosave after so many minutes

Post by silentthief »

I do understand the idea behind the timed saves because (just like everyone else here) I've wandered out into the ashlands and gotten lost, found some cool place to explore, got some stuff and injuries from that cool place, then tried to get back home to Balmora without knowing the way and running from cliffracers, died, and realized I hadn't saved and so just lost all of the last hour and a half of gameplay to our favorite Morrowind creature :D
I think its one of the things that shows off Morrowinds "charm" and "appeal" (just kidn)
vv221 wrote: It is a bit counter-intuitive.
As I see it, a better way to handle this when you already have five autosaves (assuming five is the max) would be the following:
delete autosave-1
rename autosave-2 to autosave-1
rename autosave-3 to autosave-2

save as autosave-5

This way, autosave-1 is always the oldest and autosave-5 the newest.
I think that would be a good way to handle autosaves

ST
ezze
Posts: 513
Joined: 21 Nov 2013, 13:20

Re: Option to Autosave after so many minutes

Post by ezze »

I think it is pretty much reversed...

The algorithm would be something like:

Code: Select all

for all the saves "name[number]"
    rename the save to "name[number+1]

save the new save as "name1"
if the largest [number] is greater than the limit delete the save
So 1 is always the newest, n is the oldest. If n is too big the extra saves are deleted.

Example, existing situation: save1, save2,save3 and 3 is the limit.

Rename. We have save2, save3, save4
Save. We have save1, save2, save3, save4
check the number, 4 is too big, delete. We have save1, save2, save3
User avatar
vv221
Posts: 55
Joined: 03 Oct 2012, 12:27
Contact:

Re: Option to Autosave after so many minutes

Post by vv221 »

ezze:
Good point here.
What's really important is not to break the continuity in the saves ordering.
Tarius
Posts: 574
Joined: 24 Oct 2011, 19:29

Re: Option to Autosave after so many minutes

Post by Tarius »

Actually, I much prefer incrementing file numbers with the latest file being the largest number. However, I think a good way to do things is to simply put the date and time in the file name for use as that number. so todays date at the time of this post would be something like 20140525658. Thats year month day hour minute. I use that year month day format for some of my files.
ezze
Posts: 513
Joined: 21 Nov 2013, 13:20

Re: Option to Autosave after so many minutes

Post by ezze »

I like more the 1 as newest as it appears before in the sorted list :)

Besides if you decide that there are too many autosaves and you change the limit in a natural way all the extra saves are deleted the first time you autosave. Similarly it will work naturally if you increase the limit. Also I like the idea that all numbers are between 1 and the max number of autosave
Keeping the highest as greatest is harder to manage.
Post Reply