Issue with save label

MikeH

Hi all,

When I save over a save slot using the Save:Overwrite action in my actionlist, the date/time no longer seems to update in the name of the save file. The actual save seems to work fine, but the name does not update. In my own project, as I was using ActionLists for saving via menu's, I tried also choosing the 'Custom Label' in the Save:Overwrite action (as well as the 'update label' option), but this did not make a difference to the save name.

Recreated this issue in a new project, leaving most things default and just changed the save game time format to Date+Time, but when playing the game, if I overwrite a save, the time/date remains the same in the name of the save game.

Unity: 2020.3.17f1
AC: 1.81.6

Thank you

ChrisIceBox

Does this only occur when using the Action to overwrite the save slot, or does it also occur when leaving the SavesList element's click behaviour as its default such that clicking saves automatically overwrites them?

MikeH

Hi @ChrisIceBox - it happens with either. In a new project set up using the 2D demo, the only thing I change is Settings > Saving > Time Display: Use Time and Date. The Saves menu is (already) set to 'Save when click on' but in my own project I use ActionLists and have the same problem.

Then ran the game. Saved into 2x slots at 10:03AM, and moved my character's position onscreen. Saved the game over both slots at 10:04 but they are still named '09/16/2024: 10:03'

Loaded the game and my previous character's position was loaded, so the saving seems to work but not the label.

ChrisIceBox

Open up AC's SaveSystem script, and look for the following around line 141:

UpdateSaveFileLabels (ref foundSaveFiles);

Does removing this line solve the issue?

MikeH

Hi Chris - yes it does indeed fix it. There were three instances of that line in the SaveSystem script, so I commented out all three, and the save names now appear correctly - the labels are updated with the current date/time when I save the game.

So going forwards, can I leave it like this or is there more to do?
I noticed this when I moved to 1.81.6, I'm pretty sure it was working on 1.81.5.

Thanks for your help so far

ChrisIceBox

Just remove that one instance. If it fixes the issue, I will roll out an official change in v1.82.

MikeH

I hadn't noticed you mentioned the line number in your previous comment - so I've now only commented the one at line 137 (the closest to 141) and left the other lines active.

It seems everything is working with just that line commented.

Thank you