Changes between Version 1 and Version 2 of Ticket #13841


Ignore:
Timestamp:
09/13/22 03:42:04 (20 months ago)
Author:
macca8
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13841 – Description

    v1 v2  
    1111Now that the saveType test has been restored to its intended purpose of identifying a save file’s type, changes relevant to this alternative method should be reverted as soon as possible, to restore the integrity of the autosave system. It offers no objective way of differentiating between an autosave and a regular save, and is therefore inappropriate for determining which type of save is stored in the autosave slot.
    1212
    13 As it stands, we can expect this bug to affect most engines whose querySaveMetaInfos() method returns a SaveStateDescriptor instance of type SSD(slot, description). It’s initiated when creating the SSD, and overwrites any previous _saveType value which may have been stored in the save file’s metadata. Note that engines which return a SSD without parameters appear to be unaffected, and retain their original _saveType values (e.g. Myst III, Riven).
     13As it stands, we can expect this bug to affect most engines whose querySaveMetaInfos() method returns a SaveStateDescriptor instance of type SSD(slot, description). It’s initiated when creating the SSD, and overwrites (or perhaps, overrides?) any previous _saveType value which may have been stored in the save file’s metadata. Note that engines which return a SSD without parameters appear to be unaffected, and retain their original _saveType values (e.g. Myst III, Riven).
    1414
    1515Hopefully, most users will have removed any regular saves from their more popular games, via the in-game warning dialog, before this latest switch was effected.