3,628
edits
Game crash: Difference between revisions
m
→In Super Smash Bros. Brawl
m (A while ago, Toomai reverted my interwiki box addition to Bandai Namco as it was improper usage; thus, I'm removing it here) |
|||
| Line 23: | Line 23: | ||
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 ingame 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 resetted by holding down the power button until the Wii turns completely off; just pressing the power or reset button will have no effect. | 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 ingame 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 resetted 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 stage]]s 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 {{SSBB|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 (the [[Subspace Emissary]] is particularly notorious for how unstable it is with hacks in play, to the point that the [[Project M]] team decided to completely disable access to the mode in Project M). | 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 stage]]s 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 {{SSBB|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 (the [[Subspace Emissary]] is particularly notorious for how unstable it is with hacks in play, to the point that the [[Project M]] team decided to completely disable access to the mode in Project M prior to 3.5). | ||
Like in ''Melee'', a few glitches are capable of causing crashes. The most notorious such glitch in ''Brawl'' is the grab-break glitch with {{SSBB|Yoshi}}, where if a player grabbed by Yoshi manages to break out of the grab before going into Yoshi's mouth, as soon a the player breaks out of the grab, the game will instantly crash (likely due to Yoshi still trying to access "the grabbed opponent", or 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 [[mash]]ing 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 {{SSBB|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. | Like in ''Melee'', a few glitches are capable of causing crashes. The most notorious such glitch in ''Brawl'' is the grab-break glitch with {{SSBB|Yoshi}}, where if a player grabbed by Yoshi manages to break out of the grab before going into Yoshi's mouth, as soon a the player breaks out of the grab, the game will instantly crash (likely due to Yoshi still trying to access "the grabbed opponent", or 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 [[mash]]ing 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 {{SSBB|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. | ||