Super Smash Bros. 4

Cloud (SSB4)/Down aerial: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
m (→‎Trivia: Slight grammar change to better convey the uncertainty of this statement)
m (that's a lot of italics)
Line 104: Line 104:


==Trivia==
==Trivia==
*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an ''asynchronous'' timer, which enables the auto-cancel ''on'' frame 37, rather than a ''synchronous'' timer, which would enable it 37 frames ''after'' the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.
*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an asynchronous timer, which enables the auto-cancel on frame 37, rather than a synchronous timer, which would enable it 37 frames after the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.
**A very similar error can be seen with {{SSB4|Sonic}}'s {{mvsub|Sonic|SSB4|up aerial}}.
**A very similar error can be seen with {{SSB4|Sonic}}'s {{mvsub|Sonic|SSB4|up aerial}}.
**Since this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, like with Cloud's up aerial, it was [[Cloud (SSBU)/Down aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 46 (in addition to the hitboxes ending earlier, on frame 40).
**Since this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, like with Cloud's up aerial, it was [[Cloud (SSBU)/Down aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 46 (in addition to the hitboxes ending earlier, on frame 40).

Revision as of 12:43, April 26, 2024

Hitbox visualization showing Cloud's down aerial.

Overview

Competitive.png This article or section may require competitive expertise.
You can discuss this issue on the talk page or edit this page to improve it.

Hitboxes

ID Part Damage SD Angle BK KS FKV Radius Bone Offset SDIx T% Clang Rebound Type Effect G A Sound Direct
Clean hit
0 0 15% 0 AngleIcon270.png 10 100 0 3.6 25 0.0 11.0 to 12.5 0.0 1.0x 1.5x 0% HitboxTableIcon(Clang).png HitboxTableIcon(Rebound).png Sword (type) Slash (effect) HitboxTableIcon(GroundedFalse).png HitboxTableIcon(AerialTrue).png L Cloud Hit SpecialsDirect.png
1 0 13% 0 AngleIcon60.png 30 105 0 4.5 25 0.0 7.0 to 13.0 0.0 1.0x 1.2x 0% HitboxTableIcon(Clang).png HitboxTableIcon(Rebound).png Sword (type) Slash (effect) HitboxTableIcon(GroundedTrue).png HitboxTableIcon(AerialTrue).png L Cloud Hit SpecialsDirect.png
Late hit
1 0 8% 0 AngleIcon65.png 80 55 0 3.5 25 0.0 9.0 to 11.0 0.0 1.0x 1.2x 0% HitboxTableIcon(Clang).png HitboxTableIcon(Rebound).png Sword (type) Slash (effect) HitboxTableIcon(GroundedTrue).png HitboxTableIcon(AerialTrue).png M Cloud Hit SpecialsDirect.png

Timing

Attack

Initial autocancel 1-4
Clean hit 11-13
Late hit 14-42
Ending autocancel 43-
Interruptible 60
Animation length 77
FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(HitboxChangeS).png FrameIcon(HitboxChangeE).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Hitbox).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png FrameIcon(Interruptible).png
FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Blank).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png FrameIcon(Autocancel).png

Landing lag

Animation length 26
FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png FrameIcon(Lag).png
Legend (1 square = 1 frame)
Lag
Lag time
Hitbox
Hitbox
FrameIcon(HitboxChangeS).pngFrameIcon(HitboxChangeE).png
Hitbox change
Auto-canceling
Autocancel
Interruptibility
Interruptible

Trivia

  • Like Cloud's up aerial, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an asynchronous timer, which enables the auto-cancel on frame 37, rather than a synchronous timer, which would enable it 37 frames after the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.
    • A very similar error can be seen with Sonic's up aerial.
    • Since this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, like with Cloud's up aerial, it was eventually fixed in Ultimate, where the move's auto-cancel properly uses an asynchronous timer on frame 46 (in addition to the hitboxes ending earlier, on frame 40).