Editing Crash
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{game icons|p=y|p2=y|p3 | {{game icons|p=y|p2=y|p3=y|hp=y}} | ||
In computing, a '''crash''', sometimes also referred to as a '''freeze''', happens when a piece of software stops working properly and can not continue running. This is usually because the code has tried to do something impossible, like trying to divide by zero, or read from an invalid memory position. Ideally, most software will be programmed in such a way that the final user can almost never cause the program to do something illegal, but some [[glitches]] or exploits can allow the user to do so. Games in the {{ps}} also have a few glitches, exploits, and hacks that allow the player to crash the game. | In computing, a '''crash''', sometimes also referred to as a '''freeze''', happens when a piece of software stops working properly and can not continue running. This is usually because the code has tried to do something impossible, like trying to divide by zero, or read from an invalid memory position. Ideally, most software will be programmed in such a way that the final user can almost never cause the program to do something illegal, but some [[glitches]] or exploits can allow the user to do so. Games in the {{ps}} also have a few glitches, exploits, and hacks that allow the player to crash the game. | ||
| Line 152: | Line 152: | ||
| Snitchbug crash | | Snitchbug crash | ||
| ''New Play Control! Pikmin 2'' can randomly crash a short time after a [[Swooping Snitchbug]] catches a Pikmin. || || || [https://twitter.com/smpki/status/1653800801322823682?s=61&t=SikA4XUxf3vnm53kdo9UTg Twitter video] | | ''New Play Control! Pikmin 2'' can randomly crash a short time after a [[Swooping Snitchbug]] catches a Pikmin. || || || [https://twitter.com/smpki/status/1653800801322823682?s=61&t=SikA4XUxf3vnm53kdo9UTg Twitter video] | ||
|} | |} | ||
| Line 164: | Line 161: | ||
* [[Glitches in Pikmin 3#Vehemoth Phosbat capture skip|Vehemoth Phosbat capture skip crash]]: By skipping the [[Vehemoth Phosbat]] capture in day 1, and obtaining Yellow Pikmin and Red Pikmin instead, the game will crash after the [[cutscene]] where Alph finds the [[S.S. Drake]], triggered by leaving the day 1 cave [[segment]] in the [[Tropical Wilds]]. | * [[Glitches in Pikmin 3#Vehemoth Phosbat capture skip|Vehemoth Phosbat capture skip crash]]: By skipping the [[Vehemoth Phosbat]] capture in day 1, and obtaining Yellow Pikmin and Red Pikmin instead, the game will crash after the [[cutscene]] where Alph finds the [[S.S. Drake]], triggered by leaving the day 1 cave [[segment]] in the [[Tropical Wilds]]. | ||
* [[Glitches in Pikmin 3#Formidable Oak backwards (Pikmin 3 Deluxe)|Formidable Oak backwards]]: Exclusively in {{p3d}}, if the player enters the Formidable Oak from the exit, starts the Plasm Wraith fight, and then goes through the entrance, they'll control two leaders at once. In this state, the game tends to crash. | * [[Glitches in Pikmin 3#Formidable Oak backwards (Pikmin 3 Deluxe)|Formidable Oak backwards]]: Exclusively in {{p3d}}, if the player enters the Formidable Oak from the exit, starts the Plasm Wraith fight, and then goes through the entrance, they'll control two leaders at once. In this state, the game tends to crash. | ||
== Ways to softlock == | == Ways to softlock == | ||
| Line 203: | Line 196: | ||
== Crash handler == | == Crash handler == | ||
[[File:Pikmin 2 crash handler.png|thumb|The crash handler in ''Pikmin 2''.]] | [[File:Pikmin 2 crash handler.png|thumb|The crash handler in ''Pikmin 2''.]] | ||
{{game help|npcp2|Figure out if there's any crash handler in the ''New Play Control!'' version.}} | |||
In {{p2}} for the [[GameCube]], if the game crashes, the player might be able to input a development button combination in order to get a crash handler screen to pop up.{{cite youtube|cPqyk5PyL-E|of the crash handler in action}} The code should be pressed one button at a time, and with ample time between each button press: | In {{p2}} for the [[GameCube]], if the game crashes, the player might be able to input a development button combination in order to get a crash handler screen to pop up.{{cite youtube|cPqyk5PyL-E|of the crash handler in action}} The code should be pressed one button at a time, and with ample time between each button press: | ||
| Line 214: | Line 208: | ||
The Interactive Multi Game Demo Disc Version 17 has a ''Pikmin 2'' demo with an intact code map file. This means that if the player crashes the game there, the crash handler will be able to accurately show what points of the code the game was running when the crash happened. Because of the state of the system and how large the map file is, converting the memory locations can take several seconds.{{cite youtube|31B3vF6wkdk|of the crash handler in the Interactive Multi Game Demo Disc Version 17|published={{date|7|August|2018}}|retrieved={{date|14|December|2018}}}} | The Interactive Multi Game Demo Disc Version 17 has a ''Pikmin 2'' demo with an intact code map file. This means that if the player crashes the game there, the crash handler will be able to accurately show what points of the code the game was running when the crash happened. Because of the state of the system and how large the map file is, converting the memory locations can take several seconds.{{cite youtube|31B3vF6wkdk|of the crash handler in the Interactive Multi Game Demo Disc Version 17|published={{date|7|August|2018}}|retrieved={{date|14|December|2018}}}} | ||
== References == | == References == | ||