Crash: Difference between revisions

From SMO.wiki
→‎Examples: Added more examples
→‎Examples: Updated Bowser crash info
Line 36: Line 36:
|-
|-
|[[Moon Kingdom]]
|[[Moon Kingdom]]
|[[False capture|False capturing]] [[Bowser (capture)|Bowser]] (i.e. dying at the moment Bowser is captured)
|Capturing [[Bowser (capture)|Bowser]] just as he is [[Unloading|unloaded]]
|
|[https://twitter.com/2pants/status/1308499833519570949 Link]
|-
|-
|[[Odyssey]] travel
|[[Odyssey]] travel

Revision as of 07:18, 12 February 2023

A crash refers to the game forcibly closing due to an error. Crashes are a general phenomenon with computer programs and are essentially caused by the code performing an invalid operation, such as attempting to perform an operation on a null pointer. In Super Mario Odyssey, this often translates to situations in which the game attempts to perform an action on a game object that does not exist.

Situations that trigger crashes in Super Mario Odyssey are often similar in nature to those that cause softlocks.

Examples

The following is a list of some actions that are known to trigger crashes:

Kingdoms Method Video
Cap Kingdom Capturing the frog for the first time just as it is unloaded
Cascade Kingdom Collecting Our First Power Moon after Multi Moon Atop the Falls (achievable with First Moon Skip)
Sand Kingdom Being inside a capture while a Moe-Eye wanders into a 2D pipe (achievable with Moe-Eye Escape) Link
Sand Kingdom Unknown, but involves landing in Deepest Underground while wearing the Mario 64 outfit Link
Seaside Kingdom Using water fluctuation to kill Glydon and capturing it as it dies Link
Moon Kingdom Repeatedly opening and closing the cutscene skip menu during the Peach cutscene in the Bowser Arena Link
Moon Kingdom Capturing Bowser just as he is unloaded Link
Odyssey travel Unknown Link