FANDOM

FandomVideo


A game crash, also known as a game freeze, is when a video game freezes up and ceases to respond to any input. Crashes typically occur when the game console's connection with the game is interrupted, when its CPU is overwhelmed by how much it has to process (and runs out of space to hold it all), or when it tries to access something that does not exist. Crashes are usually just an inconvenience that result in no permanent damage to the game nor console, and simply require the player to turn the console's power off to play the game again, though they will result in any data between the crash and the last time the game was saved being lost.

In the Super Smash Bros. series

As with any other game, crashes can occur in the Super Smash Bros. games. It is very rare for crashes to occur from normal ingame play, though glitches and hacks can cause them.

In Super Smash Bros.

Since the Nintendo 64 was a cartridge-based system that could have difficulty securing a connection between it and its game, this connection was far easier to disrupt, with a gentle touch of the console or cartridge (which is well known as cartridge tilting) being potentially enough to disrupt the connection and crash the game. As such, Smash 64 was far more prone to freezing without the aid of hacks than its successors. Aside from hacks and physical disruption, the game is highly stable. One of the easiest ways to crash the game is by directing Ness's PK Thunder between two Fox players using their Reflectors. If cartridge tilting was the reason for crashing the game, it would sometimes render scrolling white bars and other visual glitches throughout the screen.

In Super Smash Bros. Melee

Unlike the Nintendo 64, the Nintendo GameCube was a disc-based system that was notoriously durable and could effectively keep inserted games in place. As such, freezes in Melee from a connection disruption were rare. When crashes do occur in Melee, the game will completely freeze and cease all response to any input, though any in-game music playing when the crash occurred could keep on playing on loop, resulting in a buzzing sound.

While Melee can occasionally lag the GameCube in certain circumstances, it is never CPU-intensive enough in normal play to crash the system. However, "black holes" created from the black hole glitch can strain the system to an exorbitant amount, heavily lagging the game when they are in play. If players create more than one black hole, or create a more intensive black hole (such as putting more Turnips in it or using multiple PK Fires on it), they heavily risk crashing the game, and will inevitably do so if they keep on making more black holes or keep putting more stuff into one.

A couple of other glitches can also cause Melee to crash. Playing as Master Hand through the Name Entry glitch or hacking is notorious for causing crashes through many scenarios, as since he was not supposed to be playable, he lacks many of the assets other playable characters require (such as a victory pose, which results in the game invariably crashing if Master Hand wins a Vs. match). Potentially due to how Zelda technically takes up two character slots (one with her, the other with Sheik ready to be switched to), Master Hand will also crash the game if used in any Vs. match involving her. Another lesser-known glitch capable of crashing the game is the Shadow glitch; the Shadow glitch allowed players to catch the mini-Shadow Balls thrown during Mewtwo's forward throw as if they were an item, and if a player who caught one threw it without it being immediately caught by another player, it would crash the game. However, since the glitch was discovered early on, it only exists in Version 1.0 of Melee, as it was fixed in subsequent versions.

Crashes can also occur from attempting to improperly access incomplete data with an Action Replay. The most well-known example of this is trying to access normally inaccessible uncompleted stages through the debug menu, particularly AKANEIA. Additionally, if a player uses an Action Replay to play as Sandbag, they will crash the game if they attempt to perform any attack with Sandbag, as it has no attacks programmed in.

In Super Smash Bros. Brawl

Like Melee, console hardware-related crashes are rare in Brawl, as the Nintendo Wii is easily capable of keeping a connection with its inserted game in place, and can handle anything that can occur normally in Brawl. When crashes do occur in Brawl, the game will freeze up and cease all response to any input as usual, but all in-game sound will also be frozen, resulting in a buzzing noise that will play until the game is turned off. Additionally, when crashes occur, the Wii must be hard restarted by holding down the power button until the Wii turns completely off; just pressing the power or reset button will have no effect.

Players typically experience crashes in Brawl from improper use of hacks. One of, if not the most common, means of crashing players experience is when they have the Smash Stack file on their SD card, without running a code that disables custom stages from being loaded, and then going to the stage select screen; the game invariably crashes in this scenario on the stage select screen, as it tries to load the Smash Stack file as if it were a custom stage. Outside that novice mistake, crashes commonly occur from players placing their hacks improperly on their SD card and then trying to access the hack ingame (such as by placing a hacked stage based on Smashville over Lylat Cruise instead of Smashville, and then going to Lylat Cruise ingame trying to play on the stage). Crashes can also commonly occur when a specific hack or code itself is unstable or simply not properly made (hacks of Pokemon Trainer's Pokémon and other transforming characters are especially susceptible to causing crashes, and some texture hacks will crash the game when spontaneously loaded ingame, such as during multi-man matches). Crashes also commonly occur from playing in some single-player modes where the hack/code is unstable or simply unable to be used in such modes.

Like in Melee, a few glitches are capable of causing crashes. The most notorious such glitch in Brawl is the grab-break glitch with Yoshi, where if a player grabbed by Yoshi manages to break out of the grab before going into Yoshi's mouth, as soon as the player breaks out of the grab, the game will instantly crash (likely due to Yoshi still trying to access "the grabbed opponent", or the programming not knowing what to do if his grab is broken at that time). The glitch's infamy is from the fact that unlike other game-crashing glitches, it can occur in any match involving Yoshi without any outside elements, and through normal play instead of through a complicated and unnatural procedure that wouldn't be done by a player not trying to intentionally cause the glitch; thus it has the potential to crash the game in the middle of a tournament match without intentional invoking, resulting in either disrupting an ongoing match or forcing one of the players to be disqualified to no fault of their own (and in the potential ban of Yoshi from competitive play). However, since the time between Yoshi's grab connecting and going into Yoshi's mouth is so small, it can only occur at extremely low damages and only with exorbitant mashing skills, thus it doesn't actually occur in normal play and is a virtual nonfactor in tournaments. Another glitch capable of causing a crash is the Chain Jacket glitch; the game will invariably crash if Sheik performs the glitch without having used a prior move. While this can occur in any match involving Sheik, a Sheik player would have to be intentionally invoking it to crash the game through it, thus the only tournament consequence of it would be the forced forfeit of the Sheik player causing it.

Another means of causing crashes in Brawl is the disc itself being damaged. Several players with damaged discs have been permanently unable to access certain characters and stages as the Wii could no longer read them off of the disc; this results in any matches on the disc involving the afflicted characters or stages instantly crashing the game (or even crashing the game if the afflicted characters and stages are even hovered over on the select screens). A damaged disc could only have one specific character unable to be read anymore, or up to a significant portion of Brawl's cast and stages being completely inaccessible. When this occurs, the afflicted player has to get a new Brawl disc, have the disc repaired, or use the file replacement hack to simply load the default files through the SD card instead, though proper handling of the disc will prevent it from happening in the first place. Playing the game from its image file (such as with WODE Jukebox) prevents many of these problems, as it does not read from a physical disc.

In Super Smash Bros. for Nintendo 3DS and Wii U

As Super Smash Bros. 4 features two different versions for different consoles, the specifics in game crashes for the game varies between consoles. In general, crashes for both games are rarer than in Melee and Brawl, with no specific, repeatable method being available to cause a guaranteed crash. In the event that such a method is discovered, this behaviour can theoretically be patched via a download; currently, the only known ways to potentially cause crashes in either version is via extensive application of a model-meshing glitch involving Nabbit on Mushroom Kingdom U. This glitch was fixed in version 1.0.6, however. In the 3DS version, there is one discovered game crashing glitch: when in Training mode with Mario, if a Smash Ball is spawned and the speed is set to 1/4 with the "hold L" function, the game will crash if it's paused on the frame that Mario hits the Smash Ball and the match is then attempted to be restarted. The player will be forced to quit the game and exit to the HOME menu. Classic mode in the 3DS version is also prone to overworking the console when it requires many elements to be running, such as a high intensity and items, with some Final Smashes such as Mii Gunner's Full Blast and Ryu's Shin Shoryuken / Shinku Hadoken occasionally crashing the game.

Super Smash Bros. for Nintendo 3DS and Wii U, similar to Smash 64, can crash if the connection between the game card and the Nintendo 3DS is disrupted, as well as if the connection between the 3DS and its SD card is disrupted; compared to the Nintendo 64, however, these connections are more resilient, and under most circumstances, the 3DS will reboot into its Home Menu if this connection is lost. For digital copies of the game, crashes can occur if the data saved onto the 3DS's SD card is corrupted; in this case, an online service offered by Nintendo allows the player to verify the integrity of the game's data and redownload the appropriate files to replace corrupted data. The 3DS version has also been reported to occasionally crash in Smash Run; some 3DS consoles also have problems running the game, with the fix focusing on replacing the console itself.

Super Smash Bros. for Nintendo 3DS and Wii U, similar to Brawl, can crash if the disc becomes scratched, with the Wii U's lens being unable to read data critical for the game; no known circumvention method for this is available, due to the current lack of accessible hacks for the Wii U. Like Brawl, game crashes can be detected by the console. If this happens, a loud buzzing sound is emitted for around 5 seconds. Afterwards, the player will have to turn off the Wii U.

Community content is available under CC-BY-SA unless otherwise noted.