I have a fun one for you, mods -
It's number 17723 on spreadsheet - using -3.62
eddiecatgaming and a few others thought I lost 7 fames on axegrab, which would mean a 4:58.991 - and mario did stop moving on that frame... but he appeared to "hover" over the axe for a while. Comparing it to other 4:59.174 runs shows that the axe disappears on the same frame... BUT bowser is dropped earlier, as well as the floor and chain.
[Mod note: I also believe this is 7 frames lost and ended up with the same timing. Even though the axe did not disappear the hammers still did which is still the frame you lose control of the player and when timing stops.]
[ecg: according to recent research it has been determined that 8 frames were actually lost on axe, making this run a 4:59.008]
| # | Name | Split | Finished at |
|---|---|---|---|
| 1 | 1-1 [0] | 0m 29s 804ms | 0m 29s 804ms |
| 2 | 1-2 [0] | 0m 33s 983ms | 1m 03s 788ms |
| 3 | 4-1 [0] | 0m 34s 842ms | 1m 38s 630ms |
| 4 | 4-2 [0] | 0m 31s 966ms | 2m 10s 596ms |
| 5 | 8-1 [0] | 0m 48s 520ms | 2m 59s 116ms |
| 6 | 8-2 [0] | 0m 36s 603ms | 3m 35s 720ms |
| 7 | 8-3 [0] | 0m 35s 780ms | 4m 11s 500ms |
| 8 | 8-4 [0] | 0m 47s 673ms | 4m 59s 174ms |
Any% (NTSC) runs below 4:57.000 must now fulfill additional requirements in order to be verified.
- The run's full session must be included in the submission description.
- For emulator runs below 4:57.000, some form of input display must be visible for the duration of the run. A hand-cam or input
