Thanks Thirdeye. I can't red-tick you since I did it already too recently, so the reward will be that I post race #50 right now.ThirdeyeI'll help chip away at the last few that are remaining. I'll post again when I verify them!
👍 ThanksFlat-outThanks Thirdeye. I can't red-tick you since I did it already too recently, so the reward will be that I post race #50 right now.
KLR142Ps. Did the thread originally say that all the times under 1'20 had to be posted? Because, if not, I never saw it then, because I only saw this thread the first day it was posted...
Damn. I didn't notice it, I didn't actually read the post, just checked the times real quick and my position before I had to leave for work, or wherever I went... I guess I just can't take things for granted... Whatever.CasioYes it did.
KLR142Damn. I didn't notice it, I didn't actually read the post, just checked the times real quick and my position before I had to leave for work, or wherever I went... I guess I just can't take things for granted... Whatever.
So why did we do it like this for this week anyway?
I don't see why we can't use it every week. It's a great idea 👍Flat-Oexcept that we should use this kind of global time cut-off from time and time.
Flat-outThanks Casio for doing the talking while I'm away (click). And Kyle, I'll let the thread open here so that you have a chance to post your replay.
As Casio pointed out, the replay topic was "sensitive" (don't know if the word has in english all the meanings it has in french), which explains the 1'20 overall cut-off time.
Since most of us have a replay device anyway, I think we'll have a wider replay request range in the near future.