FreeplayScore seventh/million number not being cleared fix #4064
Conversation
This file contains 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
github-actions
bot
added
size: small
|
oh, dang it, how did my other fix end up in this branch??? |
AbnormalPoof
added
status: rejected
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Does this PR close any issues? If so, link them below.
#2318
Briefly describe the issue(s) fixed.
The last digit of the FreeplayScore doesn't get cleared before it sets a new number.
Include any relevant screenshots or videos.
2025-01-30.23-03-19.mp4
I uhhhhh think I understand how the code for the FreeplayScore now? I spent way too much time staring at the code trying to figure out how it works (and where I could set the intendedscore to 1M to test the fix), like a few hours. Ah well, I fixed it in the end, didn't I?