Messages

Thank you, should be solved now 👍

The number of replays is already part of this chart:


I could add a line there, showing the position at the end of a race. Might be difficult to find the right vertical scale, and the horizontal one will look a bit odd, since we don't have precisely on track per month. I'll give it a try at some point 👍

Sadness

You cannot view this attachment.

I'll echo HerrNove in congratulating you for the great season, and well deserved champion title! 🎆

A strong season means a lot of effort, and I can understand if you want to take it easy now. (No-one has ever won three seasons in a row, racing does take the toll!)

Hope we'll still see you around on the forum, and any races where you feel inspired by the track. Or maybe a live race for a different challenge!

Thanks for letting us know! I've triggered another 'save' on the Internet Archive, for posterity.

Thank you! When you look at the map, or when you drive through?

Should be fixed now. I've removed all casts, and replaced them with the explicit conversion function in each occasion: floor, round, and intval.

I think exploits are possible if you look at a single pipsqueak. But when you have a system of competing pipsqueaks, connivance notwithstanding, efforts balance out to avoid the extremes.

And because the "exploit" is publicly visible, it becomes part of the stregic game: "it looks like someone is holding back, ah, let me ruin their plan by doing this other thing!"

I'm interested in digging deeper though, because there are competition 'principles' that I think are important:

- strong pipsqueaks should have to make more difficult choices
- moves that can advantage a strong pipsqueaks should also lift the (not-immediate) followers

If there is an "exploit" that can advantage someone without giving something back to the lower scoreboard, that's something we should look into.

Internally, it's definitely 8303 hsec or 1:23.03, so I can confirm the number reproduced by the scoreboard is the correct one.

The problem seems to be the cast to integer I (hastily?) introduced last time when I fixed the replay preview. As a cast, it truncates, so it works as a floor instead of a round, and 8302.9 becomes 8302.0 hsec, or 12:23.02.

I'll double check during the day, but I think it's an easy fix. Thanks for bringing it up!

[2]

There's still time for another 2!

Hope things are looking up for whoever the emergency was for, and everyone affected!

Thanks for keeping these stats @alanrotoi! Looking forward to the thread "26th race winner of ZakStunts" !

Let's stick to ZakStunts tracks in this thread. Want to open a discussion for you event in the main section?, @stanceboyCZ

Oooh, I think you just gave me a great idea. Let's see if I can make time this weekend!

Hahahha, I'm going to look for some CSS that turns all exclamation marks 178° around to almost-fix this!

Or we can fix it on your actual birthday, if you tell us! 🎂