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

Explicitly specify NC/DC as mods valid for PP #163

Merged
merged 1 commit into from
Oct 20, 2023

Conversation

smoogipoo
Copy link
Contributor

As of ppy/osu#24640, NC no longer inherits DT and DC no longer inherits HT.

This can be merged as is without an update to nuget packages.

@@ -163,13 +163,27 @@ public static bool AllModsValidForPerformance(Mod[] mods)
case ManiaModKey10:
return false;

case ModNightcore nc:
Copy link
Sponsor Member

Choose a reason for hiding this comment

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

wonder if it's worth casing ModRateAdjust at the end of the switch to cover all of these? rather than having individual handling?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Doesn't it feel iffy to blindly allow all rate adjust mods?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Judging that we're in this predicament due to relying on inheritance hierarchies, I think specifying mod classes explicitly is better.

You could maybe try to keep one unified copy of the code under four case labels. Maybe.

Copy link
Sponsor Member

Choose a reason for hiding this comment

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

You could maybe try to keep one unified copy of the code under four case labels. Maybe.

Might read better, not fussed either way just curious on preference.

@peppy peppy merged commit 9ffefcb into ppy:master Oct 20, 2023
3 checks passed
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.

None yet

3 participants