Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not attempt to recalculate non-legacy scores or scores set on custom rulesets #26439

Merged

Conversation

bdach
Copy link
Collaborator

@bdach bdach commented Jan 8, 2024

Addresses discussions such as #26407 or #25914 wherein:

  • the game would attempt to convert scores for custom rulesets, which makes no sense, especially so when they're not there,
  • the game would also "recalculate" lazer scores, but that was never the intention or was never supported; the game would just increment the score version on those but still include them in the converted tally.

bdach added 3 commits January 8, 2024 22:10
This was a source of confusion for users previously, wondering why their
non-legacy (non-stable) scores weren't being converted in line with new
scoring changes, when it was never actually our intention to support
anything of the sort.
…om rulesets

Addresses discussions such as ppy#26407
or ppy#25914 wherein:

- the game would attempt to convert scores for custom rulesets, which
  makes no sense, especially so when they're not there,

- the game would also "recalculate" lazer scores, but that was never the
  intention or was never supported; the game would just increment the
  score version on those but still include them in the converted tally.
@bdach bdach added realm deals with local realm database type:behavioural area:scoring labels Jan 8, 2024
AddUntilStep("Wait for completion", () => processor.Completed);

AddAssert("Score not marked as failed", () => Realm.Run(r => r.Find<ScoreInfo>(scoreInfo.ID)!.BackgroundReprocessingFailed), () => Is.False);
AddAssert("Score version not upgraded", () => Realm.Run(r => r.Find<ScoreInfo>(scoreInfo.ID)!.TotalScoreVersion), () => Is.EqualTo(30000005));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is okay, means that non-legacy scores are going to get stuck with a total score version that may or may not have meaning to us.

@peppy peppy merged commit 06447e9 into ppy:master Jan 9, 2024
@bdach bdach deleted the do-not-attempt-score-upgrade-for-custom-rulesets branch January 9, 2024 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants