Super Smash Bros.

Pikachu (SSB)/Dash attack: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
No edit summary
Line 3: Line 3:
==Overview==
==Overview==
[[File:Pikachu Dash Attack Hitbox Smash 64.gif|thumb|The hitbox of Pikachu's dash attack.]]
[[File:Pikachu Dash Attack Hitbox Smash 64.gif|thumb|The hitbox of Pikachu's dash attack.]]
Pikachu does a running headbutt and falls on the ground, doing 9%-12% damage and average knockback. While it can be used as a finisher, its one of the moves Pikachu players will try not to use due to its high [[ending lag]], being predictable, and not being disjointed unlike Pikachu's other moves. Whats more, this move is easy to [[shield grab]] and punish, questioning its usefulness. Commonly considered Pikachu's second worst move behind its ftilt.
Pikachu does a running headbutt and falls on the ground, doing 9%-12% damage and average knockback. While its power is high enough to make it a decent move for getting opponents offstage, its very high [[ending lag]] and predictability makes it very easy to [[punish]] (especially [[shield grab]]). This makes its usefulness rather questionable. Commonly considered Pikachu's second worst move behind its {{mvsub|Pikachu|SSB|forward tilt}}.


{{technical data}}
{{technical data}}
[[Category:Pikachu (SSB)]]
[[Category:Pikachu (SSB)]]
[[Category:Dash attacks]]
[[Category:Dash attacks]]
[[Category:Normal attacks]]

Revision as of 12:45, October 13, 2013

Overview

The hitbox of Pikachu's dash attack.

Pikachu does a running headbutt and falls on the ground, doing 9%-12% damage and average knockback. While its power is high enough to make it a decent move for getting opponents offstage, its very high ending lag and predictability makes it very easy to punish (especially shield grab). This makes its usefulness rather questionable. Commonly considered Pikachu's second worst move behind its forward tilt.


Data.png This article or section may require additional technical data.
You can discuss this issue on the talk page or edit this page to improve it.