A handful of end rule conditions, noteably under the "Blossom," "Pre-Blossom," and "Highest Level" Categories were innacurate from the frames verifiers were using to retime runs. The rule conditions have been updated. No run times were affected by this change.
==================================
Pre-Blossom Category Rules Update:
Old: Timer Ends when no living players are left, and at least one player is beaconed on the level 39.
New: Timer Ends when no living players are left, and at least one player is beaconed on the level which would serve as 5/5 pylons activated.
==================================
Blossom Category Rules Updates:
Old: Timer Ends When The Beacon Sound Effect Plays At The End of the Final Fight
New: Timer Ends When on the first frame where the pylon reads as completed (9/9, 11/11, 13/13, or 18/18)
==================================
High Level Category Rules Update:
Old: 1 Level Beaten = 1 Millisecond
New: 1 Level Reached = 1 Millisecond (Death on level 25 = 25ms)
We struggle to time runs properly when
- The Tab List Isn't Open (For Solos)
- You Have Domasp Enabled (For Duo+)
- Host Isn't The Person Recording
We look at the counts to time runs but some of you guys make it hard to time runs as we now have to look and discuss at when the beaconed player is, i
