A lot of runs have glitches in their timers... you should recheck them, or if you want me to, I can send them here.
This one is obviously unlegit , just check the timer while he is doing the map , it's as clear as crystal.
Why do you think certain races are unlegit? Don't you think they can be considered skills? In that map (zen 1) I used the strategy of not jumping but simply running and it saved me some time so I think my run it's not unlegit.😉
That's not the issue , the issue is the freezing timer , a few tics are not counted , and that's not skill ^^ This problem happens because of lag from the server , or from your internet , you shouldn't submit your run when this occur , it ruins the leaderboard, and as you can see , the moderators do not verify them carefully enough. (btw you have the same thing on your zen 2 record)
PLEASE WATCH YOUR VIDEO IN 0.25x SO YOU CAN CLEARLY SEE THE TIMER
Your run is unlegit because the timer is lagging at (1:201 for longer than usual) (3:131 for too long) and (6:251) And trust me , 201 is not possible ~290 is the max.imum
Oh and , if you think it's not changing the timer, i can put your video in an app to re-time it , and you'll see the huge difference of time between what is shown and what's the real one.
@stxffeur Just realized that time freeze in my modern 1 run! Big apologies from me! I will take down the video asap:)
This is a big problem in cubecraft. It makes alot of runs not legit. maybe cubecraft needs to take a look at this and maybe rethink the timer. Iv'e just realized that another run that i posted is lagging alot. I will take down this video to.
-Jakesoft
stxffeur what would be better is if the moderators retimed it :)
Disclaimer: I am not a moderator and do not set the standards of what it considered a valid run. This is just my opinion.
A laggy timer in the middle of the run is no issue. Even if the server is lagging, as long as the timer starts and ends at the same ping, the run is legitimate. Cubecraft isn't measuring its timer in ticks, otherwise it would only be in exact multiples of 0.05 seconds (though it does tend to be around these markers since ticks are roughly 0.05 seconds in practice). I'm pretty sure it uses the Date.now() method to figure out the time, so it gets time from outside of minecraft. This means it doesn't matter if there is a lag spike in the middle of the run. I didn't really see any issues with this run regarding the start and ending, at least that were obvious.
This is a bit of an old thread now, but I feel it would still be beneficial to clarify a few things. Timer lag is really only an issue when it happens at the beginning of a run, since in that case the timer gets a delayed start and ends up showing a false time. When there's lag in the middle of a run the timer just catches up to itself once its over, and lag at the end doesn't help the player at all.
In the mentioned Zen 1 run there's only brief stuttering in the middle, but there's no lag in the beginning where it would actually cause problems. And in the time since that submission, multiple others have been able to confirm that a .200 is indeed possible. So I don't see any issues with it.
Of course timer lag can still be quite problematic, and we try to find a balance between preventing lag and not being too harsh on potentially legitimate runs. Sometimes instances of lag can slip through, so we do welcome people voicing their concerns. Just keep in mind that minor timer fluctuations are fairly normal and not necessarily indicative of anything.
