Noting the lack of (currently) clear rules on timing, I'm planning to set them as follows:

• Time begins when selecting difficulty (first frame of fade).

• Time ends on first full black frame after defeating the final boss.

• Emulator runs need to state name and version. Input display, frame count, and FPS are all strongly recommended.

I've already noticed inconsistencies between several runs that were approved for start and (mostly) end timing. As such I plan to retime all runs with the above timing to get everything consistent. I've selected these times as they're commonplace options in many games and very easy to identify. The last hit in this game isn't always clear when that happens, and timing on the first jump back frame has been difficult to identify as well.

I'm certainly open to discussion about the end time. Having it at first empty frame after last boss might give advantage to runs ending with only one hop instead of two. I'll certainly be looking at comparing that before I go retiming everything. If there's generally a clear visual cue for the last hit, please do share!

Thanks for everyone's understanding!

Great display of effort ! GL :)

My main concern was that earlier runs (including top placements) were timed differently — often ending on the last hit — and were still accepted under those conditions. So this update and the plan to retime all runs will really help level the playing field.

Thanks for the clarification and for aiming to retime all runs — really appreciate the consistency.

Looking forward to the updated board!

This could be the appropriate frame. First frame after the final explosion