[Scummvm-tracker] [ScummVM :: Bugs] #12951: TITANIC: Error when moving an old savegame to make room for an autosave

[ScummVM :: Bugs]

#12951: TITANIC: Error when moving an old savegame to make room for an autosave
-----------------------------+-----------------------------
Reporter:  eriktorbjorn      |      Owner:  (none)
    Type:  defect            |     Status:  new
Priority:  normal            |  Component:  Engine: Titanic
 Version:                    |   Keywords:
    Game:  Starship Titanic  |
-----------------------------+-----------------------------
 I have an old Starship Titanic savegame that still uses slot 0, which is
 now reserved for auto saves.

 When the engine auto saves, it asks if I want to move the old savegame.
 But if I answer that I do, I get "ERROR: Could not copy the savegame to a
 new slot".

 It turns out that the engine uses Engine::getSaveStateName() when reading
 and writing save games. That generates "titanic-win.000" for slot 0.

 The function that copies the savefile uses MetaEngine::getSavegameFile().
 That generates "titanic-win.s01" for slot 0.

 To make getSavegameFile() generate the correct string, the engine has to
 support the kSavesUseExtendedFormat feature. But that, as I understand it,
 has other implications.

 Does that mean the Titanic engine needs to define its own
 getSavegameFile()? I haven't kept up with the recent auto save changes, so
 I'm a bit wary of making changes like this.

 I also can't help wondering which other engines may be affected...
-- 
Ticket URL: <https://bugs.scummvm.org/ticket/12951>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM