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| | {{game icons|p1=y|p2=y|p3=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 | {{image}} | ||
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 done 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. The {{ps}} also have a few glitches, exploits, and hacks that allow the player to crash the game. | |||
When a crash happens in a ''Pikmin'' game, | When a crash happens in a ''Pikmin'' game, the game stops responding, and the player can do almost nothing except shut down the console and boot it back up. Crashes in ''Pikmin'' games are very rare, and the player will likely need to do them on purpose, but a corrupted or damaged game, [[saved game]] data, or system can all cause crashes. In this case, they should be replaced or repaired. | ||
Besides crashing, some scenarios can also happen where the player is " | Besides crashing, some scenarios can also happen where the player is "soft-locked". In these cases, the game continues playing and responding like normal, but it is in a state that does not allow the player to make any progress. | ||
== Ways to crash == | == Ways to crash == | ||
| Line 13: | Line 14: | ||
Besides that, there was also a rumored glitch in ''Pikmin'' that would allow the [[Beady Long Legs]] to walk out of its arena, fall into the [[pit]], and crash the game. More information can be found [[Beady Long Legs#Presumed glitch|here]]. | Besides that, there was also a rumored glitch in ''Pikmin'' that would allow the [[Beady Long Legs]] to walk out of its arena, fall into the [[pit]], and crash the game. More information can be found [[Beady Long Legs#Presumed glitch|here]]. | ||
=== ''Pikmin 2'' === | === ''Pikmin 2'' === | ||
* [[Glitches in Pikmin 2#Treasure delivery crash|Treasure delivery crash]]: If the player pauses the game in the same [[frame]] as a [[treasure]] collection [[cutscene]] starts, and then chooses to quit the cave, the game will crash shortly after. | |||
* [[Glitches in Pikmin 2#Minor|Glutton's Kitchen crashes]]: It is possible for the game to crash when the player is playing on [[Glutton's Kitchen]] sublevel 6. The reasons for this are not known. | |||
* [[Glitches in Pikmin 2#Minor|Cavernous Abyss loading crash]]: For unknown reasons, the game can crash while trying to load [[Cavernous Abyss]]. | |||
* [[Glitches in Pikmin 2#Petrified Volatile Dweevil suicide|Petrified Volatile Dweevil suicide]]: In the Japanese [[region|version]], using an [[ultra-bitter spray]] on a Volatile Dweevil that is about to explode will cause the game to crash. | |||
=== ''Pikmin 3'' === | === ''Pikmin 3'' === | ||
* [[Glitches in Pikmin 3#Hard to reproduce|Cardboard box crash]]: The game can crash some seconds after the [[cardboard box]] at the start of the first day is pushed. | * [[Glitches in Pikmin 3#Hard to reproduce|Cardboard box crash]]: The game can crash some seconds after the [[cardboard box]] at the start of the first day is pushed. | ||
== Crash handler == | == Crash handler == | ||
{{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|published={{date|3|August|2018}}|retrieved={{date|4|August|2018}}}} 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: | |||
:{{button|gc|a}} {{button|gc|b}} {{button|gc|x}} {{button|gc|r}} {{button|gc|l}} {{button|gc|padl}} {{button|gc|padd}} {{button|gc|padu}} {{button|gc|padr}} {{button|gc|z}} | :{{button|gc|a}} {{button|gc|b}} {{button|gc|x}} {{button|gc|r}} {{button|gc|l}} {{button|gc|padl}} {{button|gc|padd}} {{button|gc|padu}} {{button|gc|padr}} {{button|gc|z}} | ||
This was used by the developers to help figure out what went wrong when the game crashed during development. Because the core game itself is frozen, the handler writes the debugging data directly onto the framebuffer, and as a result, is a bit choppy and slow. When the crash handler is opened, it begins by scrolling down the entire report, line by line, and the user can only control it after it reaches the end. {{button|gc|padu}} and {{button|gc|padd}} scroll the report up and down, while {{button|gc|b}} goes to the start and {{button|gc|a}} goes to the bottom. | This was used by the developers to help figure out what went wrong when the game crashed during development. Because the core game itself is frozen, the handler writes the debugging data directly onto the framebuffer, and as a result, is a bit choppy and slow. When the crash handler is opened, it begins by scrolling down the entire report, line by line, and the user can only control it after it reaches the end. {{button|gc|padu}} and {{button|gc|padd}} scroll the report up and down, while {{button|gc|b}} goes to the start and {{button|gc|a}} goes to the bottom. | ||
The first few lines contain | The first few lines contain information about what function crashed, and where in the code it is. Because the code map file in the game's data is outdated compared to the final build, this can sometimes point to the wrong parts of the code. Everything else in the report consists of information about the type of error that occurred, and the state of some important locations of memory when that happened. | ||
== References == | == References == | ||
{{refs}} | {{refs}} | ||
{{ | {{mistakes}} | ||
[[Category:Technical]] | |||
[[Category: | |||