summaryrefslogtreecommitdiff
path: root/Source/Core/InputCommon/ControllerEmu/ControlGroup/Cursor.cpp
diff options
context:
space:
mode:
authorAdmiral H. Curtiss <pikachu025@gmail.com>2020-06-28 00:26:40 +0200
committerAdmiral H. Curtiss <pikachu025@gmail.com>2020-07-15 19:17:22 +0200
commit556e93f357a3e008481d4e8bb453e387e948df04 (patch)
treecaa97a4bda4cb4f9edb36425c25341ec1477465d /Source/Core/InputCommon/ControllerEmu/ControlGroup/Cursor.cpp
parent1ab37990b12fd327f48786ab76daeda17feb7af2 (diff)
GCMemcard: Change behavior of TitlePresent() to more closely resemble how saves are actually identified.
This modifies GCMemcard::TitlePresent() to match my findings of how the GC BIOS and various games behave when you alter the fields in the directory entry. It looks like for a save to be recognized by a game, the following have to be true: - Game code and maker code must exactly match what the game expects. - Filename is only checked up to the first null byte. All bytes afterwards can be whatever. The BIOS itself does a full compare of the filename when checking for whether it should allow copying a file from one card to another, but behaves oddly in some cases when there's non-null bytes after the first null. See the big comment in `HasSameIdentity()` for details.
Diffstat (limited to 'Source/Core/InputCommon/ControllerEmu/ControlGroup/Cursor.cpp')
0 files changed, 0 insertions, 0 deletions