-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
gameplay.pp.maxThisPlay sometimes broken #38
Comments
Yes i get that part. Let's say I get a couple of 100's and misses early on and from there SS the rest of the map. At any given point during the SS part until the end, shouldn't the maxThisPlay be the same value, as you are literally on your way to get the maximum amount of pp you can with the misses/acc loss? |
This is probably not the behavior that we are expecting, could be a regression, will look at it |
Can I have this replay? @viddie |
Sure, here you go https://fu.vi-home.de/f/sLofHRl7 (direct download) |
Attempt was made to fix that, test build could be obtained here: https://github.com/l3lackShark/gosumemory/runs/1355174754 |
Had to redo that job, Here is the build. |
That seems to have fixed the issue. I'll repoen this if it does happen to occur again. Thanks! |
My impression of this attribute was that if, from any given point in a play, you SS everything, that will be the pp you get at the end. However, sometimes after breaking combo this value slowly decreases even while playing perfectly. That isn't really the maximum then, or am I misinterpreting this attribute?
Video of this happening (see the pp-bar at the right side at around 0:22): https://www.youtube.com/watch?v=v9cMb2aP_Rw
The text was updated successfully, but these errors were encountered: