Bug?

So I recently played dinodude's level 'you' and something weird happened: I got the top score of 5138 and dinodude got 5137, however when I looked at the replay I saw I actually got a lower score than him.

(I most likely will not have the highest score by the time anyone reads this, however, I felt it was interesting to observe.)

My final time was 85.635, while his was 85.665. Any explanations why?


(dinodude's final score)

(my final score)

I remember eddy saying it was something to do with the calculations being a bit off from the time, yes its a bug

Yes, the timer doesn't work properly, sometimes it will stop earlier or later than it should, but the actual true score is the frame count (the "points" as some people call them).

I'm not too sure on this, but I think that upon reaching a max score on a run, they will all show the same count at the top. Eddy, take a look at the count on 00-3, your run ends on 65, and whitewhales ends at 35, this makes me think that 70 isnt the max.
On 00-1, and 01-2, the clocks end at the same time for the max scores.

Thats would be pretty interesting, but I doubt it since its impossible for the game to "know" what the max score for a level is (there can be thousands of different routes and thousands of ways to do each part for each level). I think its rather that the maxed levels are done pretty much similarly, because they are too simple, which means we all end the same (same speed, angle, etc), so the timer ends in the same spot. So maybe the timer isn't random, but it rather works badly because it takes other things into consideration, it basically other factors affect it. Meanwhile the other levels, the non-maxed ones, are more complex, so even if you are just as fast, you might be finishing the level differently, which might change the final time. And I'm always saying might because these are just conjectures of course.

I have sometimes dreamed about a feature that tells you the absolute max for a level, but its simply impossible to determine except when levels are overly simple, in which case we, the players, can guess the max (since we reach it), but not the game itself. It would be cool though.

By the way, this doesn't happen anymore on the new, browser version.

The fact that the game cant know what the max score for a level is indicates that there is an element of consistency with the clock. I dont think that similar runs would result in a glitchy clock stopping at the same time, because thats not inconsistent. (I mean if the similarity of the run is why the clocks all show the same time, then the clock is doing its job perfectly, therefore consistent [which it isnt... is it?])
Something spooky is going on....

cooperverdon wrote:The fact that the game cant know what the max score for a level is indicates that there is an element of consistency with the clock. I dont think that similar runs would result in a glitchy clock stopping at the same time, because thats not inconsistent. (I mean if the similarity of the run is why the clocks all show the same time, then the clock is doing its job perfectly, therefore consistent [which it isnt... is it?])
Something spooky is going on....

Its not doing its job consistently if people with the same score get a different time and people with the same score get different times. Even if this decision is not random at all, and is based somehow on similarities of the run, the only thing the timer should actually take into account is, surprise, the time, and nothing else. Anything else is just wrong behaviour, consistent or not, it doesn't matter.

So the frames, that is, the score, is the real reliable measure here, there's no need to take the clock into account.

@up

Ye dude, I know. I'm just talking about things I have observed. I do think a score of 71/72 is possible on 00-3.