United StatesHey what do you know, I just got on to review some. Thanks for being patient, I've been busier than usual for the past few days, but I should have more time soon. As for the verifier position, we're not currently looking for applications but if we do open them in the future we'll make an announcement about it on our discord.
Your actual run didn't start until ~14 seconds in. When you died on level 1, the time before the death doesn't count as part of the run. Which is good for you because it means you actually got a faster time than you thought, but it does mean that portion of the video needs to be skipped.
You died 14 seconds in, not 11. Other than that, you are correct in that your irrelevant footage was over the stated limit, which is why your run was rejected. If you want to get around this you can either re-edit the video to contain less time before the run, or you can use a timestamped link to take the viewer directly to the beginning of the run. I would recommend using the timestamped link since it's quite straightforward and easy, instructions for how to do so are in the rules. Once you make this adjustment I'd be happy to review your time.
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.
Update: Competitive parkour has been added! :)
We actually used to have a category like this a while ago, but very few people used it and since it required a whole extra variable we ended up removing it.
As someone who suffers from lag fairly often, I can understand your frustrations. The thing with lag is that while your timer may not stop immediately after you touch the pressure plate, your timer also starts a little bit after it is supposed to. This means that even if your ping is high, as long as it is consistently high the lag will effectively cancel itself out and your time will actually be more or less accurate. I've taken a look at the runs you've submitted thus far and while it takes a bit for the end pressure plate to register, it also takes about the same amount of time for the start to register as well. So your runs shouldn't be much longer than they are supposed to, if at all.
Also if we were to retime runs for laggy players independent of the in game timer and purely eyeball when the end pressure plate is reached, it would be too subjective and quickly lead to disagreements. So sadly that option isn't really feasible. Fortunately it shouldn't be too much of a problem for the reasons outlined above. We're open to suggestions though!
I've cleared the affected runs for Java Edition of Modern 6, although I'm not sure if this problem is also present in Bedrock Edition. If this issue afflicts Bedrock as well, those times can be cleared too.
When I click on 'View rules', it seems that no rules have been defined. Is this some sort of visual glitch, or is this actually the case? Also, a lot of the maps don't have pages on the level leaderboard. I assume this is to reduce the clutter that would come with having a lot of maps with no runs, but is there some way to get a map added if one wanted to do a run for it?
