It's easier to clean up times.
I think it's frankly unacceptable to blindly control your character.
Timings can be off due to the rule of "as soon as the cutscene starts" or "when the developer console closes."
I firmly believe that as soon as you're available to move after the opening cinematic, that's when time should start.
Same principal as when timer ends. It's on fadeout, not as soon as you enter the Bridge.
What happens when Fatshark patches out the F2 trick to move during the cutscene, let's say in version 1.1?
This would negate every run until that point with one single patch.
So... better safe than sorry.
Firstly, the moving during cutscene thing was in the first game, it's an intentional mechanic. It's not gonna get patched out. I'm 99% sure on that. Secondly, negating runs with patches is a moot point anyway thanks to the hero power changes in 1.0.5 and various buffs, various runs have very likely been negated. Finally, timing from as soon as the cutscene starts is perfectly valid, load times don't affect that and it's all dependent on the player from then on. Not sure why you're trying to compare to when the timer ends, you still have character control until fadeout. As things stand right now, how you start and how you end is inconsistent as you could have character control at the start but you choose not to? Just confusing as things stand, imho. If you can't move blindly with having basic map knowledge, I don't know what to say... It's not like it's hard to do.
Alright I'm gonna be epic and submit a run moving during the cutscene =) I'll also upload some 'speedrun legal' runs but I just wanna make a run moving during the cutscene.
I don't want to say I told you so, but I told you so.
As the F2 trick to move during the cutscene already got patched out, I go ahead and lock this thread.
