Changes between Version 4 and Version 5 of Ticket #14737


Ignore:
Timestamp:
Apr 1, 2024, 11:11:10 AM (5 weeks ago)
Author:
fusefib
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #14737 – Description

    v4 v5  
    1414...
    1515}}}
    16 ''Blues1.nam'' and ''[PlayerName1].bca'' are shared between the CDs and contain the game profile, i.e. sign-in information and overall game progress across e.g. minigames from all four pathways. The .sga to .sgd files are pathway-specific savefiles that get generated once you enter a pathway and the game saves progress. [PlayerName1] is whatever gets chosen.
     16''Blues1.nam'' and ''[PlayerName1].bca'' are shared between the CDs and contain the game profile, i.e. sign-in information and overall game progress across e.g. minigames from all four pathways. The first has name/color/birthday in INI-format (when uncompressed); the other is a light, player-specific game progress file. When you create a sign-in profile and proceed, both get generated. ''[PlayerName1]'' is whatever gets chosen.
    1717
    18 ScummVM generates the same type of savefiles, but its behavior is to add "[gameID]-" as a prefix to these savefiles, and to increment gameIDs (or targets) when adding what is considered ID-wise the same game. With the Yellow CD and Red CD being considered separate games with one default gameID, we get "**BluesBirthday-**" and "**BluesBirthday-1-**" as default savegame prefixes, thus:
     18The ''.sga'' to ''.sgd'' files are pathway-specific savefiles that get generated once you enter a pathway and the game saves progress.
     19
     20ScummVM generates the same type of savefiles, albeit compressed, though its behavior is to prefix the files with the game entry's **target**. Targets get incremented if one adds, ID-wise, the same detected game again. With the Yellow CD and Red CD being considered separate games with one default `gameID`, in a typical scenario we get "**BluesBirthday-**" and "**BluesBirthday-1-**" as default savegame prefixes, thus:
    1921{{{
    2022BluesBirthday-Blues1.nam
    … …  
    5052Per MD5s and detection entries, there is only one known Red version and Yellow version of the full game and demos don't create these files, so probably zero compatibility issues on that account.
    5153
    52 The prefix remains useful so users can distinguish these savegames among other ScummVM saves as well as partial overlap with the existing default naming.
     54The gameID-based prefix remains useful so users can distinguish these savegames among other ScummVM saves as well as partial overlap with the existing default naming.
    5355
    54 A minor drawback is the "BluesBirthday-1-" progress gets reset to zero, unless the user manually swaps the savesets which would still exist. I would say the drawback is minimal and the possibility of restoring game profiles by renaming can simply be documented in the game's Wiki entry.
    55 
    56 A seamless user experience fix might be to newly add a game configuration key by default (e.g. boolean "sharedsaves") when adding these games going forward, and to add a check for that configuration key in the code above. This way, (the other half of the) existing entries will continue to work with the current savegame naming convention and newer entries will have shared game sign-in and progress by default. However, this needlessly clutters the code.
     56A minor drawback is the other target's (e.g. "BluesBirthday-1") progress gets reset to zero, unless the user manually swaps the savesets which would still exist. But the inconvenience is minor.