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 (→Overview: Stuff about Sm4sh Cloud's down-air) |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
A downward stab with the Buster Sword that boasts a large, powerful sweetspot and decent speed. It serves as a threatening [[Edgeguarding|edgeguard]] due to its size and [[Spike|spiking]] capability, and an effective deterrent for juggling because of its surprisingly wide and long-lasting sourspot. [[Auto-canceling|Autocancelling]] the move allows the low knockback of the sourspot to offer combo potential into a variety of finishers, while also making it deceptively difficult to intercept or punish. | |||
==Hitboxes== | ==Hitboxes== | ||
{{SSB4HitboxTableHeader}} | {{SSB4HitboxTableHeader}} | ||
Line 104: | Line 105: | ||
==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 | *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). |
Latest revision as of 22:10, April 28, 2024
Overview[edit]
A downward stab with the Buster Sword that boasts a large, powerful sweetspot and decent speed. It serves as a threatening edgeguard due to its size and spiking capability, and an effective deterrent for juggling because of its surprisingly wide and long-lasting sourspot. Autocancelling the move allows the low knockback of the sourspot to offer combo potential into a variety of finishers, while also making it deceptively difficult to intercept or punish.
Hitboxes[edit]
Timing[edit]
Attack[edit]
Initial autocancel | 1-4 |
---|---|
Clean hit | 11-13 |
Late hit | 14-42 |
Ending autocancel | 43- |
Interruptible | 60 |
Animation length | 77 |
Landing lag[edit]
Animation length | 26 |
---|
Lag time |
Hitbox |
Hitbox change |
Autocancel |
Interruptible |
Trivia[edit]
- 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).
|