Check map exchange string when overwriting a save

[Marvin01]

TL;DR

Add additional check(s) before overwriting a save file. A good candidate is the map exchange string.

What ?

Pretty much what the TL;DR says.

Why ?

It is currently too easy to overwrite a different game file when saving and it can cost a lot of time and be really frustrating.
Especially when one has saving more or less in muscle memory.
The check for the playtime already exists and helps a great deal, but it isn't enough when playing a save with a long playtime where one can easily overwrite a save with a slightly shorter play time.
An additional check (such as the map exchange string) would be even more safe and can probably be implemented at the same place where the playtime is checked.
It also might not be that much effort to implement.

[Koub]

For the records, here is an answer from a dev a few years ago on that subject :
viewtopic.php?p=475982#p475982
The devs do change their minds sometimes, so it's just for the records.

[SoShootMe]

The current UI is just bad: it tries to combine two actions in a way likely to lead to mistakes and data loss. Prompting for confirmation based on rules determining "this looks like a different save" misses a simpler solution of separating "save" (overwrite current file without confirmation, or show save window for an unsaved game) and "save as" (show save window and always prompt before overwriting a file). Like countless applications have done for decades.

[nethus]

Great idea. Or maybe based on a GUID or other unique identifier, generated at the start of a game (or first time it is saved) and stored into the save file?
I can imagine map exchange strings being reused...

[Koub]

I will shamelessly self advertise my suggestion on this other thread : viewtopic.php?p=169112#p169112.
I think this would be optimal as a design, and would check all the needs.