You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?The text was updated successfully, but these errors were encountered: