Frame Data (80% Completed)

Note:
I am currently testing hitbox endings using Pikachu's spotdodge (timing the spotdodge to end on a certain frame of the move) - note I can only reliably get this for ground attacks
I am currently testing invincibility during Spotdodge, Airdodge, Rolls (ledge and normal)
I totally don't know how to do Aerial Testing (Auto-Cancels, IASA, or Ending) with the codes I'm using to get the data. Want to let me know how?

NOTE:

Data was gathered using Debug Pause and Button Modifier Codes (GeckoOS)

Data is read like this:

Hitbox - End Hitbox
(Aerials only) Auto Cancels
IASA/Ending
MISC
??? = Haven't tested it yet (mostly end hitboxes...)

JAB
First Hitbox: 3-???
Second Hitbox: 17-???
Last hitbox: 31-???

IASA Frames:
1 jab only: 11
2 Jabs only: 35
All 3 Jabs: 64

FTILT

REGULAR
9 - ???
44

UP
9 - ???
39

DOWN
9 - ???
39

DTILT
11 - ???
36


UTILT
17 - ???
49

DASH ATTACK
6 - ???
44

FSMASH

REGULAR
18 - ???
72

UP
18 - ???
71

DOWN
19 - ???
70

DSMASH
First Hitbox: 19 - ???
Second Hitbox: 29 - ???
58

USMASH
First Hitbox: 24 - ???
Second Hitbox: 37 - ???
76

NAIR
First Hitbox: 8 - ???
Second Hitbox: 21 - ???
???
???

UAIR
6 - ???
???
???

FAIR
14 - ???
???
???

BAIR
10 - ???
???
???

DAIR
14 - ???
???
???

B
54 - ???
115

REVERSED
61 - ???
122

(7 frames slower)


SIDE-B
20 - ???
24 (Ledge)
47 (Hit's with the hitbox @ 20
80 (Missed - Grounded)
??? (Missed - Aerial)

DOWN-B
15 - ???
72 (Grounded, no Ledge Cancel)

UP-B
??? - ???
23 (Ledge)
55~ (Entire thing.. it's hard to tell when it actually ends)

GRAB
7 - ???
???

DTHROW
32

FTHROW
42

UTHROW
48

BTHROW
51

LEDGE ATTACK UNDER 100%
24 - ???
62

AIRDODGE
Invincibility Frames:
47~

ROLL FORWARD
Invincibility Frames: 4 - 21
32

ROLL BACKWARD
Invincibility Frames: 4 - 19
34

LEDGE ROLL UNDER 100%
49

SPOT DODGE
Invincibility Frames: 2 - 22
27

DASH
??? (Beginning IASA frames)
29

CROUCH
6

DOWN TAUNT
14 - Sound
Facing Left: 60
Facing Right: 83

SIDE TAUNT
71 Sound
100

UP TAUNT
3 - Controller Rumble
24 - Sound
80

Reserved for if space is needed.

(I plan on bringing more then just frame data to you guys )

for aerial duration, I'd test to see what the minimum # of frames is before he can double jump (or airdodge) again.

for landing IASA, I'd probably take frame data for Falcon's SH/FH (maybe even fastfall, if you're daring lol), then start the aerial at an arbitrary frame # (maybe 10 frames after aerial duration) and start 2-5 frames later each time until you get landing lag, then adjust it upwards until you get IASA.

So for example if B-air lasted 20 frames until you could double jump, and Falcon's SH was 50 frames, then I'd try starting B-air at frame:

- 25 <- gives 25 frames (5 frames after B-air's duration)
- 30
- 35 <- he stops getting lagless landings
- 40
- 50 <- lands

So you find out that if you start B-air on frame 35, he gets landing lag. So you start to adjust upwards and start on frame 34, then 33, 32.. until you get a lagless landing again.

So say you get a lagless landing on frame 32.

50-32 = 18 frames.

So B-air has IASA landing on frame 18.

Anyway, that sounds super complicated, and I've never done this before and I'm just pulling stuff out of my head since I'm half asleep.

...gl with that lol.

I can do aerial duration, the only problem is I can't seem to input a jump or airdodge ASAP after a move with this method of testing.

Also testing the up/down forward moves was a pain because Falcon wanted to grab -_- not perform the **** move

I'll get aerial durations sometime soon, then I can work on the auto-canceling (although I think uair cancels anytime, fair is after the hitbox leaves, bair is anytime, and dair is after the hitbox leaves)

Nice. I'll link this and put it near the top as soon as I finish my index update.