I have tryed whit DailyBuild... but i thinks every version has been affected by this BUG.... and i thinks we can reproduce it whit every version on every supported games :)
I have also tryed it usually for SCUMM Games in games when it's possibly to Save using F5 Button.... how to reproduce:
- Start a game whitout any previous savegame... ex MI1
- Open F5 menù
- Select SAVE
At this point this savegames it's been stored to SLOT 0 and not on SLOT 1... the SLOT 0 it's the slot used by AutoSave (usually and default setted to every 5 minutes) on all SCUMM Games, only whit this motive i thinks it's a general bugs :)
I have also tryed and find the same function whit this title:
- Monkey Island 2
- Indy Fate of Atlantis and Last Crusade
- Zak McKraken
It's 3 title using SCUMM :)
The normal response to this is "Don't save in the Autosave slot".
Will leave this open as we should consider preventing "manual" saving in the autosave slot for all engines in future.
Yeah..... but it's not possibly, at the fist savegames it's ever used the autosave slot......
This is definitely not affecting all engines. A lot of engines seem to be setting the write protected flag for some of the slot ids (usually slot 0). A quick scan reveals that AGI, BBVS, CGE, CGE2, Drascula, Hugo, Kyra, Mortevielle, ZVision seem to set it for some slots (note that not all might be auto-saves). Thus I mark this as SCUMM only, other engines not protecting special save ids should get their own bug report.
Last edit: Johannes Schickel 2015-04-13