I've configured Autosave so that it only saves on 2 occasions:I won't argue with you, as I know far, far less than you do about it, but I'm not sure it was that particular save file. Any v2.6 save when loaded in v2.6.1 behaves the same way, unless the "Autosave" is enabled and disabled in v2.6.1, saved, shutdown and restarted. (Though I'm not sure the restart is necessary, its just habit to do so in these kinds of situations, and I didn't test it.)
I'd like to stress something. Even with the current funky autosave situation (v2.6.1), the "Change scene location" is part of the problem -
Load a map in May's bedroom on the 2nd floor -
Activate "Save" function -
The "Autosave" file description does not change; shows May on 2nd floor -
Move to 1st floor -
Activate "Save" function -
The "Autosave" file description does not change; shows May on 2nd floor -
Move outside the house -
Activate "Save" function -
The "Autosave" file description shows May in Neighborhood -
Didn't try it before prior post. Just did experiment:
Load Wednesday afternoon at Beach; go to College; go to 2nd floor -
Save to any slot but "Autosave" -
Exit menu -
Activate "Save" function -
"Autosave" slot shows location as "Left Wing" -
Load "Autosave" file -May's location is 1st floor, Left Wing -
Move May to 1st floor, Right Wing (Nurse/Principal's Offices) -
Activate "Save" function -
"Autosave" slot shows location as "Left Wing" -
All this is just FYI, as I've opted not to use that slot for any saves, and am content to work around it. I would suggest that, unless other players complain, you not tear your hair out trying to fix it, just do what seems best to you and attempt an explanation in a "Read.txt"
Do consider a separate config file to be loaded at Game start, with some persistent player settings saved there. (No idea how much trouble that might be to implement.) Currently, it asks which save file to load, and will load any setting stored in that file, which might be from some previous version (i.e. v2.6 - "Autosave" glitch included). Any subsequnt save will propagate the glitch.
BTW, currently, with "Autosave" disabled, overwriting the "Autosave" slot does NOT change the file name.
- When switching between outdoor maps
- When May's moves from outside to inside.
So the behavior you've observed is as it's intended.
Autosave will not create a save when crossing a map while indoors.
The reason for this is that when certain events run May switches map and thus would create an Autosave. This proved to be problematic since many of those saves where unusable and actually caused people to loose there progress when the game crashes shortly after. So I changed the behavior to prevent that.
A separated config file would be a nice feature, but it would require extensive knowledge of the Ruby programming langue, which I don't have, and I don't feel like investing 6 months to a year to learn a programming langue that isn't used much anymore is worth my effort.