Add customizable follow circle size setting to Strict Tracking mod#37265
Closed
byrbyrka wants to merge 4 commits intoppy:masterfrom
Closed
Add customizable follow circle size setting to Strict Tracking mod#37265byrbyrka wants to merge 4 commits intoppy:masterfrom
byrbyrka wants to merge 4 commits intoppy:masterfrom
Conversation
Implements feature request ppy#30438. Changes: - Add FollowCircleScale bindable setting to OsuModStrictTracking (range: 0.5-3.0, default: 2.4) - Expose setting in mod customization panel with label 'Follow circle size' - Update SliderInputManager to use custom follow circle scale for tracking calculations - Update FollowCircle implementations (Default, Argon) to scale visually based on setting - Add real-time visual scaling when setting is changed during gameplay - Fix memory leak by properly unsubscribing from OnLoadComplete event
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements feature request #30438.
Changes: