Version changes are not graceful #79

Open
opened 2023-12-13 17:33:09 +00:00 by EmmyHeart · 2 comments
Contributor

When changing the version of a profile, such as upgrading from a base version of a game to Plus (specifically Chunithm, MaiMai, and Ongeki), a completely separate profile is created on the new version, and updated with all the information from the next upsert. On next card-in, the old profile is loaded again with no upgrade info, and the cycle continues. Likely just need to switch the add to an upgrade for now, as going back in versions is very broken at the moment anyway.

When changing the version of a profile, such as upgrading from a base version of a game to Plus (specifically Chunithm, MaiMai, and Ongeki), a completely separate profile is created on the new version, and updated with all the information from the next upsert. On next card-in, the old profile is loaded again with no upgrade info, and the cycle continues. Likely just need to switch the add to an upgrade for now, as going back in versions is very broken at the moment anyway.
Owner

Versioning stuff needs to be decided on a per-game basis, since some games handle going back in time more gracefully then others. For example, maimai should be able to handle going back and forward through any DX version just fine, so no explicit versioning is needed there, but wacca gets crash-happy when you start time traveling. The current bad state of profile versioning is due to past me saying that that's a future me problem, and now I'm future me...

Versioning stuff needs to be decided on a per-game basis, since some games handle going back in time more gracefully then others. For example, maimai should be able to handle going back and forward through any DX version just fine, so no explicit versioning is needed there, but wacca gets crash-happy when you start time traveling. The current bad state of profile versioning is due to past me saying that that's a future me problem, and now I'm future me...
Author
Contributor

If I'm honest, cross-version compatibility going backwards with Chunithm is more trouble than it's worth. There aren't many things that can be preserved going back, and a lot can break going forward. While keeping version-specific data is still essential, I think for Chunithm at least, blocking profile loads from older versions would prevent a lot of potential data corruption, especially in the jump forward and back between New and up, and Plost and lower.

If I'm honest, cross-version compatibility going backwards with Chunithm is more trouble than it's worth. There aren't many things that can be preserved going back, and a *lot* can break going forward. While keeping version-specific data is still essential, I think for Chunithm at least, blocking profile loads from older versions would prevent a lot of potential data corruption, especially in the jump forward and back between New and up, and Plost and lower.
Hay1tsme added the
bug
seen
labels 2024-01-08 21:41:29 +00:00
Hay1tsme added the
system
label 2024-01-08 21:42:40 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hay1tsme/artemis#79
No description provided.