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

PBing in gametime but not in realtime makes Splits.io "prefer" the wrong PB #762

Open
glacials opened this issue May 5, 2021 · 0 comments
Labels
bug Issues that are solved by repairing functionality

Comments

@glacials
Copy link
Owner

glacials commented May 5, 2021

Splits.io will list your PBs on your homepage and profile, and use them for certain calculations like rivalries. However the way Splits.io finds your PB is by finding your fastest realtime run for the category, and does not take gametime into account at all.

This has led to situations where runners of mostly gametime-based games PB in gametime but not in realtime (which to them is still "a PB"), but Splits.io still tells them their previous run is their current PB. There's no way to override this behavior.

Not sure about a best solution. Maybe use the game.srdc.default_timing field to determine which measurement to use?

@glacials glacials added the bug Issues that are solved by repairing functionality label May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are solved by repairing functionality
Projects
None yet
Development

No branches or pull requests

1 participant