Welcome to SmashWiki! Log in or create an account and join the community, and don't forget to read this first! |
Notices |
---|
The Skill parameter has been removed from Smasher infoboxes, and in its place are the new "Best historical ranking" and "Best tournament result" parameters. SmashWiki needs help adding these new parameters to Smasher infoboxes, refer to the guidelines here for what should be included in these new parameters. |
When adding results to Smasher pages, include each tournament's entrant number in addition to the player's placement, and use the {{Trn}} template with the matching game specified. Please also fix old results on Smasher pages that do not abide to this standard. Refer to our Smasher article guidelines to see how results tables should be formatted. |
Check out our project page for ongoing projects that SmashWiki needs help with. |
Whispy blink glitch
How to perform
The player must choose Marth or Roy in any type of Vs. match or training and choose Dream Land (64) as the stage. Then, wait until Whispy, the tree in the back of the stage, blinks. On the last 2 frames of Whispy blinking, the player must execute a jab, Forward tilt, up tilt, down tilt, dash attack, or standing grab.
The hitboxes for thase attacks (sans standing grab) will disappear until the move finishes.
As for the standing grab, Marth/Roy does the grab without lunging forward, making it safer than a normal grab.
Explanation
No one knows why the hitbox dissappears when Whispy blinks.
One explanation provided by a user on twitter stated that when he was using a mod that shows textures, when Whispy blinked, he saw blink textures of Marth. He said when Marth blinks and Whispy does the blink at the same time, the game cannot execute the hitbox as the textures is very close to the blink. However, this theory was debunked when a youtuber called AsumSans asked why can't Marth and Roy do it to each other. The user said he would check again. This time, he did not see any texture of Marth/Roy blinking when whispy blinks.
The reason behind this glitch is still unknown.