Since last "visible fruit" discussion we settled that timer will stop once player lands on rock or in water nearby the fruit (while it's still visible). Same for Towers.

Using this cool freeze frame effect over stopping the timer altogether, I can just playback video further and edit your time while keeping the precious milliseconds :-)

AnyTech/NoTurbo currently refer only to poosting methods used.

I'd prefer to let the runners make new runs if the change affects the run by reducing the time potential.

Map updates will be handled case-by-case basis, if the map update is unbearable I'll archive it as a level and add new one, eg.: "Temple [2023-12-24]".

Nah don't bother, give me speedrun.com links to these runs and I'll update their description

Discussion moved here

even though I have met them

If you re-encode a 25FPS video to 60FPS, you only duplicate existing frames, so that doesn't meet the borderline minimum requirement. You can compare your videos to ones of other runners. I'm telling you you have wrong video settings, either in recording software or editing software. You can choose to do something about it or give up.

This is upsetting and beyond my strength, so I assigned it to another moderator for verify/reject.

This run was artificially converted to 60FPS from much lower value in post-production.

This is upsetting and beyond my strength, so I assigned it to another moderator for verify/reject.

This run was artificially converted to 60FPS from much lower value in post-production.

If you record at 60FPS, you def shouldnt lower it by processing in whatever program you're using. If you want to cut out segment unrelated to speedrun, you can use lossless-cut to cut videos without re-encoding.

In Kdenlive, you can switch the project settings to match imported video clip, so it'd be easier to export at 60FPS, but don't bother with that - we just need a run evidence.

I open "statistics for nerds" on YouTube, or if I want to inspect more thoroughly I download entire video and put into Kdenlive

This and several next runs are 25FPS, the deleted one was even lower. My guess is you have good original footage, then you're rendering your videos with wrong settings and lower their quality just to add an optional timer.

You'd be better off with LiveSplit, I added a guide for it in Guides section

Can't respect your sub-second measurement due to footage not meeting minimum requirement (look up my previous run comments), so had to round it up. Also I updated the ruleset to prohibit timers from taking up more than 5% of screen space, so for future videos you gotta size down your timer or preferably not re-render your videos for it. I'll add a guide to use a dedicated live software for time measurement.

Ooh I like that freeze frame effect at the end!

Rules currently don't prohibit coop runs of Fruit, or 1v1 flag race :-)

Coop as a sub-category would only generate more runs to verify with no added value. 3 guys start from spawn, then 2 wait at the flag post. Headache for runners to evidence that too, people have trouble meeting basic video parameters requirement, and you ask them to merge 2-3 video POVs!?

After inner moderator discussion, Towers fruit will stop the timer landing on rock and this thread will be linked in the ruleset.

Like I said in your other run, please don't edit your videos to add the timer, upload original raw unedited footage. Bottom left corner says you're getting 60FPS so I assume you could record with that, or at least 30, because these latest videos are only 25FPS.

I'll verify this one because I care less about 10sec long runs.

All this talk in video description about meeting the requirement 30FPS, and you still uploaded it as 25FPS. Just 5 frames short.

Won't take it down unless other runner complains, but next time make sure to upload raw footage to youtube, don't re-render entire video just to add an on-screen timer.

floor poosting is basically crab poosting, so it would fall in AnyTech

Correct. I've updated the rules to link to Poosting Guide, which explains each poost. Crab Poost is the original name given by its founder, later it was bastardized as Floor Poost by community.

Rules dont state otherwise, though it comes with slight time loss

Actually neither Arena or Fields need this rule clarification, they have a solid win condition. Updating this rule just for Towers is wrong. Towers Fruit: as long that green dot is shining you're good to stop the timer. Run Gatehouse fruit instead, there's yet for someone to poost through it properly.