Song lengths are very inaccurate. (And another suggestion)

[Wafles]

When you select a song online it gives you a length. Much of the time these lengths are hilariously inacurate. Is there any way this can be fixed? Or removed? The times are accurate far less than 50% of the time.

The reason for the inaccuracy appears to be that the server saves the length of the file the last time it was played, even if someone quits out early, it counts this as a finished file.

A possible way to make it more consistent:
Have the server store the longest length of a given song, provided its unique song title, artist, and difficulty rating. Very few files are named identically with the same ratings so this would narrow the inconsistencies massively. Basically if someone plays a file and it ends up being shorter than the already recorded time, count this as a quit out.

On top of this, I would recommend trying to find a way to not store results from files that are quit out early. Here's a quick example of why this is a problem:


Basically you can gimmick the leaderboards. This happens intentionally sometimes, and unintentionally some other times. Maybe implement so that popular files, maybe files with more than 50 plays, can be compared against the average number of total steps, and if the file is far below the average, don't count it?

[Guilhermeziat]

[Izzy]

Throwing out incomplete scores from the scoreboard shouldn't be too hard. We can use the average MIGDP as a basis and then get rid of scores that differ from it too much to where it would have to of been failing or incomplete. Something like 70% should get rid of all super high incomplete scores, but keep all low scores.

We already throw out scores like this for your averages on your profile so I'll see what we already do for that.

[houkouonchi]

I believe this should be mostly fixed now atleast the next time the right person plays the song. I made it so only 3.95 clients with failoff or failafter song will update the song lengths now.