Today, a runner got an untied WR for a game I moderate. They submitted their time, I verified it, all good. A while later I tied that WR since we only use full seconds on the leaderboard. I submitted my run and verified it. In the WR progression graph of the game they are listed as the WR holder for today since they got the time first. But for some reason I am on top of the leaderboard. Isn't usually the person on top who got the WR first? Is this a bug?

looked at the game. sometimes the sorting is weird if it is all done on the same day. also in your case: time frame perfectly http://retime.mcbe.wtf/ wont have a tie in the milliseconds i will bet

Edit: this is not true. Look at my post below for correct information.

@survivalMichi Not everyone wants to use milliseconds if there is no in-game timer, especially for longer games. Ties may occur but it is acceptable.

@Oreo321 youngest to oldest or oldest to youngest?

The oldest account has the lower ID, so that accounts shows first.

@Oreo321 Oh, I had no idea, thanks for clearing that up!

@Oreo321 My account was created 1 year ago while the other runner signed up 3 years ago. Are you sure it's like you said?

@Oreo321 then why is laika listed first?

also the game is 4 minutes long sooo.... no argument if it was a hour i wouldnt call it a solution

We added milliseconds to the times so the issue is solved, however it still doesn't explain why I was on top despite my account being created later.

@Laika_the_Spacedog I apologize for my wrong answer earlier today, I was indeed mistaken. The account creation date has nothing to do with this.

I did some tests on a mock category, by submitting mock runs by me and 2 others (with their permission). And oh boy did I found some interesting stuff. In case 2 or more runners submit runs in the same day with the exact same time, then:

• The next order variable will be the video link, in descending "dictionary" order. So let's say for simplicity that runner 1 submitted the video link "a", runner 2 with "b" and runner 3 with "c" - the third runner will be on top, then the second runner, and then the first runner at the bottom. Another example: runner with a YouTube video link will be on top of a runner with Twitch video link.

• In the very impossible case that the 2 or more runners submitted their runs with the exact video link, the next order variable is the run submission date in ascending order. (It might also be the run verification date, hard to tell and I don't care). Which means the first person to submit their run will be on top, and so on by the order of the runs submissions/verifications.

Testing for the next order variable is useless at this point.

@Oreo321 Wow, that's an... interesting variable to chose. What the heck... 😅 Thanks for testing!

SRC is weird

@Pac pls fix

Bumping this thread so someone from Elo might see this, but this stupid order of sorting things has lead to this nonsense https://www.speedrun.com/smbce/thread/jj6ox/

I think it's better to send a report through the support hub if you want Elo to notice stuff more easily.

I honestly just don't feel like typing everything. I'll make a support hub request later if I feel like it.