SSB64 Icon.png
SSBB Icon.png
SSBU Icon.png

Blast through

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
Donkey Kong using his forward smash on Sonic, making the latter pass through the Great Fox's fin.

Blast through is a glitch in Super Smash Bros., Super Smash Bros. Brawl and Super Smash Bros. Ultimate. It involves hitting a character at such high speeds towards a solid part of the terrain that they go straight through. Despite the mechanics around the glitch being simple and with the potential to lead to several instances of the glitch happening, it is difficult to pull off accidentally.


Super Smash Bros.[edit]

The glitch is only currently known to work on the Race to the Finish and Peach's Castle stages, and with two characters. A character with sufficiently high damage can go through the surrounding walls of this enclosed stage.

  1. Pick a character with a strong attack like Donkey Kong or Captain Falcon for one player, and a light character for the other player.
  2. Enter the Race to the Finish stage in a VS match using the debug menu.
  3. Have the stronger character pummel the weaker character until their damage is around 900% or above.
  4. Attack the weaker character with a very strong attack, like Giant Punch.

If done successfully, the character should escape from the inside of the stage and be KO'd.

On the Peach's Castle stage, it is performed in a different way, rather than the walls or floors.

  1. One character must deal up to 900% or higher damage to the other, using either set knockback attacks, hacks, or the Green Shell glitch.
  2. The damaged character should be placed below the Bumper of the stage, and the other character must hit them towards the Bumper.

If done successfully, the character will pass through the Bumper and be Star KO'd. In Training Mode, however, if the game is slowed down via the speed features, it can be seen that the character collides with the Bumper, rather than passing through it.

Super Smash Bros. Brawl[edit]

In Brawl, this glitch allows a character to pass through thin terrain in a stage. It can be done in at least two places:

  1. In Corneria:
    1. Enter the training mode, pick Donkey Kong for the first player, and a medium-weight character like Mario as the opponent.
    2. Pick Corneria as the stage.
    3. Place Donkey Kong on the right edge of the ship, facing left, and the other character on top of the most elevated part of the dark gray exhaust at the back, near Donkey Kong.
    4. Set the opponent's damage to 999%.
    5. Forward smash the opponent to the left.
  2. On a custom stage:
    1. Create a custom stage on the industrial setting.
    2. Place the I-shaped structure on the stage, the one with pass-through ceiling and floor platforms, and a solid wall in the middle.
    3. Play on this stage in training mode, with a strong character as the first player and a light character as the opponent.
    4. Set the opponent's damage to 999%.
    5. Use a strong attack on the opponent to make them fly towards the wall on the I-shaped structure.

For the first scenario, if all went well, the opponent should fly through the tip of the Great Fox' fin. For the second case, the character should pass through the structure.

Super Smash Bros. Ultimate[edit]

In certain stages, such as a No KO custom stage, if a character is hit hard enough through semi-thin walls, they can end up inside the walls if their velocity is high enough, such as being hit by reverse aerial Warlock Punch, Critical Hit, almost any fully charged forward smash from a character above a weight of 120, Giant Punch, and several other moves that have a large amount of knockback.

No KO stages[edit]

There are reports that this glitch can be done on enclosed custom stages. This seldom happens successfully, if at all, however, given the stage builder blocks' high thickness. The hardly-coherent instructions that are most used are roughly as follows:

  1. Create a No KO stage, with a fully enclosed solid box and spikes on the top so that characters don't spawn there.
  2. In training mode, pick either Ganondorf or Marth and the aforementioned stage.
  3. Get the opponent to be KO'd once (maybe make them get out with a Final Smash like Aura Storm), and when they respawn, they should be in the middle of the bottom structure.
  4. Set the opponent's damage to 999% and set the speed to 1.5x.
  5. Hit the right of the opponent to make them go left:
    1. As Marth, use a Critical Hit.
    2. As Ganondorf, perform a Reverse Warlock Punch.


A diagram explaining the glitch. On the top scenario, the knockback is too weak; the character doesn't move enough between frames.

One of the easiest and least performance-intensive ways to check for collisions is to analyze if a character's hitboxes would be inside the stage's hitboxes on the next frame of movement. If so, then the move doesn't happen, and the character bounces off. If not, that means that there is probably no terrain in the way for the next frame, so movement can happen.

If the speed is too high, the character moves a large distance per frame. Suppose one frame, the character is very close to a piece of solid scenery, and the game calculates their position on the next frame. Due to their huge distance move per frame, the next position is beyond the terrain. As such, the game assumes there is nothing in-between.

This glitch isn't usually a problem because the Super Smash Bros. game engines check for collisions at least once per frame, which is enough to cover most scenarios. It can only happen if severe amounts of knockback are implemented, and only on terrain that's thin enough. A solution would be to implement a different collision detection method, like one that checks for hitboxes between the before and after positions.

Interestingly, it can be noted in the Corneria case in Super Smash Bros. Brawl that the stage actually shifts the character's trajectory a bit, as if it were refracted. Whether or not this is influenced by the interference of knockback from a small detection of collision on the frame after the pass through, or if this "glitch" is actually accounted for in the engine is unknown.