(formerly named "any% definition change", but this was heavily misleading)

This is a forum thread meant to discuss a new timing definition for the any% of both games. Specifically, the beginning point. Why is that, you might ask ?

Well, to find out, please make sure to check the EoD mirror thread : https://www.speedrun.com/klonoaeod/thread/lbyto/1#qkfei It is preferred that you respond in that thread instead.

https://www.speedrun.com/klonoaeod/thread/lbyto

[Edit] Choice decision has been announced in the other thread.

How's that ?

"

• Timing starts upon the first frame of the screen being completely black, which ensues right after the fade-down of the save select screen.

• Timing ends on final hit on Garlen. Time does not stop if you die. "

[Edit : Changes were made, though I'm not sure if we actually need to worry about dying during or after the last hit. Might adding another line (will be discussed in the server)]

(Copied) Changes made, last message about this probably.

The "show post-game cutscene" probably won't affect previous runs that didn't show it.

Now to work on re-timing the runs

Well looks like we're not gonna be able to use any of the black screens timing points that comes after the fade-in as the beginning of the run.

Timing from the perfectly black frame is just completely inconsistent, as the frame itself doesn't occur the same way in both its front end and back end, between different footage of the game on Youtube, or even within our own runs ! It might all be based on setups or emulators but nothing is known about the subject.

Furthermore, runs such as BC98's make it unusable since their runs are unusually darker and get pitch black before the fade-out process even ends.

We'll very likely have to resort to other timing methods. Maybe something like, timing at the first frame of the fade-down, or at a point that's much after the fade-down, like the cutscene, or even beyond idk.

Even though there are no problematic videos for EoD (that I could find), there are no reasons why those issues wouldn't affect it in the exact same way. That should probably ask for a change, even though we've re-timed a bunch of runs for it already... but that's nothing more than our fault for not doing proper research beforehand.

After some more discussion in the community server, it has been decided that we change the beginning point of the run to something that is more practical and friendly for re-timing runs.

As follow, the new text :

"

• Timing starts upon the first frame of the fade-down process that happens to the save screen soon after creating a new game. "

We had already started re-timing a lot of runs before that point, so hopefully this teaches us a lesson in not pulling such major changes without prooftesting them first.

We will again return to re-timing runs. The boards obviously remain open for new submissions. This should be the last post.

Update : all DCT runs are now re-timed !