Ukikipedia - User contributions [en]

Unsolved single-goal challenges

2019-09-04T02:51:14Z

Bad boot:

This page lists '''unsolved single-goal challenges''' that are extremely difficult or impossible with current knowledge. None of these challenges have been completed or solved.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch and living
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)
* Moving during [[Time Stop|time stop]] in JRB (to get shell clones)
* Grabbing the hangable ceiling on the bottom of the beginning cloud in [[WMotR]]
* Cause a game crash by going out of bounds in the [[CotMC]] entry room or in [[TTM]]
* Accessing the upper floors of the castle without first collecting the key from BitFS
* Living after collecting [[1-Up Mushroom#The Impossible 1-up|the Impossible 1-up]]
* Collecting [[Blast Away the Wall]] without using the cannon, ledge grabbing, or using time stop

==Former challenges that have been completed==
* Picking up the cannon bob-omb on the same frame as leaving its radius
:* https://youtu.be/uFuC5DcbsjU
* Putting the Ukiki that steals your hat on the monkey cage
:* https://www.youtube.com/watch?v=oErcSAAwy4U
* Collecting Mystery of the Monkey Cage without changing the HOLP
:* https://youtu.be/UhchV2Kr_ig

[[Category: Challenges]]

{{Challenges}}

Unsolved single-goal challenges

2019-09-04T02:48:22Z

Bad boot:

This page lists '''unsolved single-goal challenges''' that are extremely difficult or impossible with current knowledge. None of these challenges have been completed or solved.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch and living
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)
* Moving during [[Time Stop|time stop]] in JRB (to get shell clones)
* Grabbing the hangable ceiling on the bottom of the beginning cloud in [[WMotR]]
* Cause a game crash by going out of bounds in the [[CotMC]] entry room or in [[TTM]]
* Accessing the upper floors of the castle without first collecting the key from BitFS
* Living after collecting [[1-Up Mushroom#The Impossible 1-up|the Impossible 1-up]]
* Collecting [[Blast Away the Wall]] without using the cannon or ledge grabbing

==Former challenges that have been completed==
* Picking up the cannon bob-omb on the same frame as leaving its radius
:* https://youtu.be/uFuC5DcbsjU
* Putting the Ukiki that steals your hat on the monkey cage
:* https://www.youtube.com/watch?v=oErcSAAwy4U
* Collecting Mystery of the Monkey Cage without changing the HOLP
:* https://youtu.be/UhchV2Kr_ig

[[Category: Challenges]]

{{Challenges}}

Movement steps

2019-07-02T00:45:04Z

Bad boot:

{{stub}}

Typically, Mario's position is updated incrementally using his velocity. These increments are called '''steps''', and they behave differently when Mario is on the ground, in the air, in water, hanging, and climbing a pole. When on the ground or in the air, these steps typically occur four times per frame, and are commonly referred to as '''quarter steps''' or sometimes '''quarter frames'''.

Steps are also responsible for detecting collision with [[surfaces]], updating Mario's [[referenced surfaces]], and updating Mario's [[Water|water level]]. However, quarter steps don't detect object collisions or warps.

== Air Step ==
''Certain things here are more explained on their individual pages. If something lacks detail, check the link for more information.''

When an action performs a ''common'' air step, the first thing Mario does is update his horizontal velocity/sideways position via [[straining]]. This is only for the common air step and is not part of the quarter-frame checks.

=== Quarter-Frame Checks ===

After that is updated, the movement is split into "quarter-steps" that breakdown Mario's movement and determine what his outcome of each step is. The checks for the quarter-steps are as follows:
# The position a quarter of Mario's velocity ahead of Mario is checked for cancels/outcomes. Anything in bold is an exit out of the rest of the checks.
## If the position is above OOB but below Mario's current floor height, Mario's height is changed to the floor height and he '''lands'''.
## If the position is above OOB but not below Mario's current floor height, Mario's height is set to the new height and he '''hits a wall'''.
## If the action has the "riding shell" flag and the water level at the position is above the position's floor (up to 78 units above the position):
##* The floor height from here on is the water height.
##* The floor from this point on is a "fake" floor on the surface of the water.
##* The floor's origin offset is set to the water height.
## If the position's height is 78 units or less below a floor and there is not a ceiling 160 units or less above it (because of how variable types an [[overflow jump]] may occur here):
##* Mario's position horizontally is updated to the new position.
##* Mario's height is set to that of the floor's height.
##* Mario's floor and floor height are updated.
##* Mario '''lands'''.
## If the position's height is 78 units or less below a floor and there is a ceiling 160 units or less above it (because of how variable types an [[overflow jump]] may occur here):
##* Mario's height is set to that of the floor's height.
##* Mario '''lands'''. (Because Mario's floor is not updated, this is where a [[Pedro Spot|pedro spot]] may occur)
## If the position's height is 160 units under, at, or above a ceiling and his vertical velocity is positive or zero:
##* Mario's vertical velocity is set to zero.
##* If the ceiling above Mario is hangable and the air step has the "check hang" flag, Mario '''hangs'''. (Since this did not use the new position's ceiling/location, this is potentially a [[Hangable-Ceiling Upwarp|hangable-ceiling upwarp.]])
##* Otherwise, '''nothing happens'''.
## If the position's height is 160 units under, at, or above a ceiling and his vertical velocity is negative:
##* If the position's height is at or below Mario's floor height, Mario's height is set to the floor height, and he '''lands'''.
##* Otherwise, Mario's height is set to the new height and he '''hits a wall'''.
## If there is a wall 30 units above the position but not 150 units above the position and the air step has the "check ledge grab" flag:
##* If Mario's velocity is positive, Mario is pushed by the wall opposite the velocity direction, and there is a floor 60 units behind the wall within 238 units upward, Mario '''ledge grabs'''. (Potentially a [[GLG]])
##* Otherwise Mario's position is set to the new position, his floor and floor height are updated, and '''nothing happens'''.
## Mario's position is set to the new position and his floor and floor height are updated.
## If Mario is colliding with a wall 150 or 30 units up and the upper or only wall is lava, he '''lava wall boosts'''.
## If Mario is colliding with a wall 150 or 30 units up and Mario is facing perpendicular to 0x6000 units away, he '''hits a wall'''.
## If no other exit has occurred, '''nothing happens'''.
# This repeats until Mario encounters something besides '''nothing happens''', up to four times including the initial time.
# Mario tracks his "exit", with '''nothing happens''' being tracked if the whole process completed four times.

With the outcome selected and the movement mostly done, a series of things happen.
* If Mario's velocity is not negative, his "peak height" is updated.
* Mario's step noise is updated based on his floor.
* If Mario is not flying, [[gravity]] is applied.
* [[Vertical Wind|Vertical wind]] is now applied/accounted for.
* Mario's visual position is updated to Mario's position.
* Mario's yaw is updated to match the in-game angle.

=== Common Air Step Results ===
If doing a common air step, Mario now decides what to do based off the "exit" from the quarter-frame checks before. Here is what he does for each exit:
* '''Nothing Happens''':
** Mario's animation is now applied.
* '''Lands''':
** If Mario is not over a hard [[surface]], the [[terrain]] is either snow or desert, Mario's peak height is more than 1000 units above him, the surface does not belong to an object, and the Y normal of the surface is not less than .8660254 (square root of 3 divided by 2):
*** Mario plays an OOF noise, dependent on which [[Version Differences|version of the game]].
*** Mario spawns particles.
*** Mario's action is set to the [[Feet Stuck in Ground|feet stuck in ground]] action and the '''lands''' checks stop.
** If Mario's action is not twirling, the floor is not lava, his negative velocity is less than -55, and the distance from the peak height to Mario is more than 3000 units:
*** Mario is hurt by 16 (24 without his hat).
*** The camera shakes.
*** Mario plays the "attacked" noise.
*** Mario is set to the [[Hard Backward Ground Knockback|hard backward ground knockback]] action and the '''lands''' checks stop.
** If Mario's action is not twirling, the floor is not lava, his negative velocity is less than -55, and the distance from the peak height to Mario is more than 1150 units:
*** Mario is hurt by 8 (12 without his hat).
*** Mario is squished for 30.
*** The camera shakes.
*** Mario plays the "attacked" noise.
** Mario is set to his action's landing action.
* '''Hits a Wall''':
** Mario's animation is now applied.
** If Mario's forward velocity is more than 16 and is in contact with a physical wall/surface:
*** Mario's yaw is "reflected" across the most recent wall Mario collided with, up to the first 4 walls. (This can be glitchy with more than 1 wall, i.e. [[Unreferenced Walls|unreferenced walls]]).
*** Mario plays a noise depending on whether or not he is wearing a metal cap.
** If Mario's forward velocity is more than 16 and he is not in contact with a physical wall/surface (i.e. OOB):
*** A different sound is played, but Mario's yaw is not reflected. 
** If Mario is in contact with a wall, his action is set to the [[Air Hit Wall|air hit wall]] action.
** If Mario is not in contact with a wall (i.e. hitting OOB):
*** Any positive vertical speed is capped to 0.
*** If Mario's forward velocity is 38 or more, spawn particles and set his action to the [[Backward Air Knockback|backward air knockback]] action.
*** If Mario's forward velocity is more than 8 but less than 38, set Mario's forward speed to -8 and set his action to the [[Soft Bonk|soft bonk]] action.
** If Mario's forward velocity is 16 or less (initially, not after these other changes), set the forward velocity to 0.
* '''Ledge Grabs'''
** Mario's animation is set the idle ledge grab animation.
** Mario enters the [[Ledge Grab|ledge grab]] action while dropping any held objects and no longer riding a shell.
* '''Hangs'''
** Mario's action is set to the [[Start Hanging|start hanging]] action.
* '''Lava Wall Boosts'''
** Mario's yaw is set perpendicular to the wall.
** Mario's forward speed is capped to 24.
** If Mario is not wearing a metal cap, he is hurt 12 (or 18 without his hat).
** Mario plays the noise for being burned.
** The camera preset is set to the area's default preset. 
** Mario enters the [[Lava Boost|lava boost]] action while dropping any held objects and no longer riding a shell.

Unsolved single-goal challenges

2018-12-15T00:46:59Z

Bad boot: shaking my ted

This is a list of single goal challenges that are incredibly difficult/impossible with current knowledge. None of these have been completed.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Collecting [[Wing Mario over the Rainbow]] Capless and/or Cannonless
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch and living
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating 4 or 5 stars at once in BoB
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)
* Get back on the platform after falling off in the Bowser 2 fight
* Moving during [[Time Stop|time stop]] in JRB (to get shell clones)
* Changing the position where Koopa the Quick finishes the race
* Grabbing the hangable ceiling on the bottom of the beginning cloud in [[WMotR]]

==Former challenges on this list which have been accomplished==
* Beating SA in one irl breath
:* https://youtu.be/3BueQSrscks
* Picking up the cannon bob-omb on the same frame as leaving its radius
:* https://youtu.be/uFuC5DcbsjU
* Putting the Ukiki that steals your hat on the monkey cage
:* https://www.youtube.com/watch?v=oErcSAAwy4U
* Collecting Mystery of the Monkey Cage without changing the HOLP
:* https://youtu.be/UhchV2Kr_ig

Unsolved single-goal challenges

2018-12-10T00:18:19Z

Bad boot: - totwc crash, + wmotr hangable ceiling

This is a list of single goal challenges that are incredibly difficult/impossible with current knowledge. None of these have been completed.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Collecting [[Wing Mario over the Rainbow]] Capless and/or Cannonless
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch and living
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating 4 or 5 stars at once in BoB
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)
* Get back on the platform after falling off in the Bowser 2 fight
* Moving during [[time stop]] in JRB (to get shell clones)
* Changing the position where Koopa the Quick finishes the race
* Grabbing the hangable ceiling on the bottom of the beginning cloud in [[WMotR]]

==Former challenges on this list which have been accomplished==
* Beating SA in one irl breath
:* https://youtu.be/3BueQSrscks
* Picking up the cannon bob-omb on the same frame as leaving its radius
:* https://youtu.be/uFuC5DcbsjU
* Putting the Ukiki that steals your hat on the monkey cage
:* https://www.youtube.com/watch?v=oErcSAAwy4U
* Collecting Mystery of the Monkey Cage without changing the HOLP
:* https://youtu.be/UhchV2Kr_ig

Talk:Surface

2018-12-01T20:49:57Z

Bad boot:

This page should be moved to [[Triangle]], which is a much better name for the phenomenon [[User:MMMMMMMMMMMMM|MMMMMMMMMMMMM]] ([[User talk:MMMMMMMMMMMMM|talk]]) 20:11, 1 December 2018 (UTC)
:The name "triangle" is ambiguous, as it could be confused with visual triangles. Furthermore, "surface" has become the standard, both in decomp and in general conversation. Another minor point is that when riding a shell on water, the water under mario becomes a floor, yet it is not a triangle. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 20:47, 1 December 2018 (UTC)

Talk:Surface

2018-12-01T20:48:07Z

Bad boot:

This page should be moved to [[Triangle]], which is a much better name for the phenomenon [[User:MMMMMMMMMMMMM|MMMMMMMMMMMMM]] ([[User talk:MMMMMMMMMMMMM|talk]]) 20:11, 1 December 2018 (UTC)
:The name "triangle" is ambiguous, as it could be confused with visual triangles. Furthermore, "surface" has become the standard, both in decomp and in general conversation. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 20:47, 1 December 2018 (UTC)

Triangle

2018-12-01T19:50:54Z

Bad boot: Bad boot moved page Triangle to Surface over redirect: We do call it surface, both in decomp and in casual speech. Plus triangle is ambiguous

#REDIRECT [[Surface]]

Surface

2018-12-01T19:50:54Z

Bad boot: Bad boot moved page Triangle to Surface over redirect: We do call it surface, both in decomp and in casual speech. Plus triangle is ambiguous

{{stub}}
A '''surface''' or '''triangle''' in Super Mario 64 is a piece of geometry that exerts some kind of force or effect on Mario. Every triangle falls into one of three categories: a floor triangle, a wall triangle, or a ceiling triangle. However, a triangle does not store what category it is. Instead, its category is determined based on the y component of the triangle's [[wikipedia:normal vector|normal vector]]. If y component > 0.01, then it is a floor. If y component < -0.01, then it is a ceiling. Otherwise, it is a wall<ref>https://www.youtube.com/watch?v=UnU7DJXiMAQ</ref>.
==Walls==
[[File:Non-Vertical Wall.png|300px|right|thumb|This wall in [[BoB]] is not quite vertical.]] The majority of walls in the game are perfectly vertical, but not all. Walls that are not vertical are one cause of [[Glitchy Ledge Grab]]s.
'''hitbox stuff'''
==Floors==
==Ceilings==
==References==
<references />

Coin limit

2018-11-19T07:37:07Z

Bad boot: /* Coin limit for each course */

Note: Code shown in this section is recreated and may not be the exact code used by the game

A '''coin limit''' is the maximum number of coins that can be collected or saved in a given area. Some courses allow infinite coins to be collected. However, in the NTSC (American) version, the coin counter is programmed to stay at the maximum of 999.

There are two types of coin limits - the 999 coin limit within the course (except Japanese version), and the 255 coin limit that is saved in the save-able records.

==The 999 coin limit==
The limit is intentionally put in by the programmers to prevent the game to count up coins greater than 999:

if(coin_counter > 999) {
coin_counter := 999;
}

==The 255 coin limit==
Separately, there is an unintentional coin limit involving the saved coin score. This value overflows and is set to 0 if the number of coins Mario collected in the course is a multiple of 256. (Not within the course, but when recording the saved coin score after Mario exits the course.) Thus, the easiest way to obtain the highest possible saved coin score in a level is to simply collect 255 coins. 511 and 767 also produce a saved coin score of 255, but collecting more than 255 coins is not as efficient as collecting a star when 255 coins have been collected. 1,023, 1,279, etc. also save as 255, but these coin scores cannot be obtained in the NTSC version.

==Coin limit for each course==
Normally, the number of available coins in the course prevents the player from getting an excess number of coins to reach either of the coin limits. Nonetheless, there are ways for a player to perform infinite coin glitches such as moneybag duplication, [[cloning]] or utilizing certain exploits of the game, allowing infinite coin glitches in certain courses.

Some courses have only a finite number of coins; in these courses, [[cloning]] is impossible and there are no infinite coin glitches. The three courses that don't fall into either of these categories, namely [[Tick Tock Clock]], [[Rainbow Ride]], and [[Bowser in the Fire Sea]], allow for clones to be created, but due to a lack of [[loading zone]]s, the clones fill up the game's [[object slot]]s. Due to this, there is a limitation on the number of coins that can be collected within these three courses.

In the table below, 999 coins represent stages with infinite coin glitches available that does not have clones occupy object slots making the game crash.

{|class="wikitable"
|-
!Course
!Available coins
!Maximum possible coins
!Strategies
|-
!colspan=4|Save-able courses
|-
|[[Bob-omb Battlefield]]||146 coins||999 coins||Breaking/Disappearing cork box glitch<ref>https://www.youtube.com/watch?v=nw24PeumUqE</ref> Ride cancel<ref>https://www.youtube.com/watch?v=Q1yCvUBIZmE</ref> (Cloning is possible but limited)
|-
|[[Whomp's Fortress]]||141 coins||999 coins||Breaking/Disappearing cork box glitch
|-
|[[Jolly Roger Bay]]||104 coins||104 coins||
|-
|[[Cool, Cool Mountain]]||154 coins||154 coins||
|-
|[[Big Boo's Haunt]]||151 coins||151 coins||
|-
|[[Hazy Maze Cave]]||139 coins||139 coins||
|-
|[[Lethal Lava Land]]||133 coins||133 coins||
|-
|[[Shifting Sand Land]]||136 coins||999 coins||Breaking/Disappearing cork box glitch (Cloning is possible but limited)
|-
|[[Dire, Dire Docks]]||106 coins||999 coins||Water shell cloning, loading area reset<ref>https://www.youtube.com/watch?v=y5IvORQstFM</ref>
|-
|[[Snowman's Land]]||127 coins||999 coins||Moneybag duplication<ref>https://www.youtube.com/watch?v=eJnEh4Cjs0M</ref> Time stop coin collection, loading zone<ref>https://www.youtube.com/watch?v=gJhMwxtsTGQ</ref>
|-
|[[Wet-Dry World]]||152 coins||999 coins||Chuckya cloning, loading area reset
|-
|[[Tall, Tall Mountain]]||137 coins||999 coins||Bob-omb cloning, loading area reset Time stop coin collection, loading zone<ref>https://www.youtube.com/watch?v=1htuwz2qJa4</ref>
|-
|[[Tiny-Huge Island]]||192 coins*||999 coins||Piranha plant glitch<ref>https://www.youtube.com/watch?v=OalrzUMc-oQ</ref> Time stop coin collection, loading zone<ref>https://www.youtube.com/watch?v=WseQkejCuz4</ref> Cloning using chuckya Ride cancel
|-
|[[Tick Tock Clock]]||128 coins||279 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Rainbow Ride]]||146 coins||290 coins**||Bob-omb cloning, with limit due to object slots
|-
!colspan=4|Non-saveable courses
|-
|[[Bowser in the Dark World]]||80 coins||999 coins||Infinite coins from Bowser's fire<ref>https://www.youtube.com/watch?v=izGgTt3v0ho</ref>
|-
|[[Bowser in the Fire Sea]]||80 coins||250 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Bowser in the Sky]]||76 coins||999 coins||Infinite coins from Bowser's fire
|-
|colspan=4|*Including [[the impossible coin]], underground, to the left of the line of 3 coins **Maximum number of objects allowed: 239 for TTC, and 227 in RR.
|}

==Unbounded Coin Limit Glitch (Japanese version)==
In the Japanese version, there is no coin limit within the courses. When the coin counter reaches a value of 1,000, the game runs a few lines of code wherein there is a typo:

if(coin_counter > 999) {
lives_counter := 999;
}

This should be the following:

if(coin_counter > 999) {
coin_counter := 999;
}

Because the lives counter is a signed short, the value of 999 overflows to -25. This is displayed in the HUD as "M25." (The "M" presumably means "minus.")

After reaching a value of 32,767, the ''coin display'' remains at that value. After that, only the hidden ''coin count'' keeps incrementing. That is because the coin count is a signed short, so if the player collects more coins, the coin counter will overflow to -32,768. Since -32768 is not greater than 32,767, the coin display will not increment any further. If one were to collect a 65,636th coin (65,536 for the overflow and 100 for the star), a second 100 coin star would spawn. This was a part of a strategy that could have been applied to collect "To the Top of the Fortress" in 0x A presses<ref>https://youtu.be/GMOxYVtJhOI</ref>, but it wasn't because a faster 0xA strategy was discovered for that star<ref>https://youtu.be/M4M_OyUorRQ</ref>.

==References==
<references/>

Coin limit

2018-11-19T07:24:29Z

Bad boot: /* Coin limit for each course */

Note: Code shown in this section is recreated and may not be the exact code used by the game

A '''coin limit''' is the maximum number of coins that can be collected or saved in a given area. Some courses allow infinite coins to be collected. However, in the NTSC (American) version, the coin counter is programmed to stay at the maximum of 999.

There are two types of coin limits - the 999 coin limit within the course (except Japanese version), and the 255 coin limit that is saved in the save-able records.

==The 999 coin limit==
The limit is intentionally put in by the programmers to prevent the game to count up coins greater than 999:

if(coin_counter > 999) {
coin_counter := 999;
}

==The 255 coin limit==
Separately, there is an unintentional coin limit involving the saved coin score. This value overflows and is set to 0 if the number of coins Mario collected in the course is a multiple of 256. (Not within the course, but when recording the saved coin score after Mario exits the course.) Thus, the easiest way to obtain the highest possible saved coin score in a level is to simply collect 255 coins. 511 and 767 also produce a saved coin score of 255, but collecting more than 255 coins is not as efficient as collecting a star when 255 coins have been collected. 1,023, 1,279, etc. also save as 255, but these coin scores cannot be obtained in the NTSC version.

==Coin limit for each course==
Normally, the number of available coins in the course prevents the player from getting an excess number of coins to reach either of the coin limits. Nonetheless, there are ways for a player to perform infinite coin glitches such as moneybag duplication, [[cloning]] or utilizing certain exploits of the game, allowing infinite coin glitches in certain courses.

Some courses have only a finite number of coins; in these courses, [[cloning]] is impossible and there are no infinite coin glitches. The three courses that don't fall into either of these categories, namely [[Tick Tock Clock]], [[Rainbow Ride]], and [[Bowser in the Fire Sea]], allow for clones to be created, but due to a lack of [[loading zone]]s, the clones fill up the game's [[object slot]]s. Due to this, there is a limitation on the number of coins that can be collected within these three courses.

In the table below, 999 coins represent stages with infinite coin glitches available that does not have clones occupy object slots making the game crash.

{|class="wikitable"
|-
!Course
!Available coins
!Maximum possible coins
!Strategy
|-
!colspan=4|Save-able courses
|-
|[[Bob-omb Battlefield]]||146 coins||999 coins||Breaking/Disappearing cork box glitch Ride cancel (Cloning is possible but limited)
|-
|[[Whomp's Fortress]]||141 coins||999 coins||Breaking/Disappearing cork box glitch
|-
|[[Jolly Roger Bay]]||104 coins||104 coins||
|-
|[[Cool, Cool Mountain]]||154 coins||154 coins||
|-
|[[Big Boo's Haunt]]||151 coins||151 coins||
|-
|[[Hazy Maze Cave]]||139 coins||139 coins||
|-
|[[Lethal Lava Land]]||133 coins||133 coins||
|-
|[[Shifting Sand Land]]||136 coins||999 coins||Breaking/Disappearing cork box glitch (Cloning is possible but limited)
|-
|[[Dire, Dire Docks]]||106 coins||999 coins||Water shell cloning, loading area reset
|-
|[[Snowman's Land]]||127 coins||999 coins||Moneybag duplication Time stop coin collection, loading zone
|-
|[[Wet-Dry World]]||152 coins||999 coins||Chuckya cloning, loading area reset
|-
|[[Tall, Tall Mountain]]||137 coins||999 coins||Bob-omb cloning, loading area reset Time stop coin collection, loading zone
|-
|[[Tiny-Huge Island]]||192 coins*||999 coins||Piranha plant glitch Time stop coin collection, loading zone Cloning using chuckya Ride cancel
|-
|[[Tick Tock Clock]]||128 coins||279 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Rainbow Ride]]||146 coins||290 coins**||Bob-omb cloning, with limit due to object slots
|-
!colspan=4|Non-saveable courses
|-
|[[Bowser in the Dark World]]||80 coins||999 coins||Infinite coins from Bowser's fire
|-
|[[Bowser in the Fire Sea]]||80 coins||250 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Bowser in the Sky]]||76 coins||999 coins||Infinite coins from Bowser's fire
|-
|colspan=4|*Including [[the impossible coin]], underground, to the left of the line of 3 coins **Maximum number of objects allowed: 239 for TTC, and 227 in RR.
|}

==Unbounded Coin Limit Glitch (Japanese version)==
In the Japanese version, there is no coin limit within the courses. When the coin counter reaches a value of 1,000, the game runs a few lines of code wherein there is a typo:

if(coin_counter > 999) {
lives_counter := 999;
}

This should be the following:

if(coin_counter > 999) {
coin_counter := 999;
}

Because the lives counter is a signed short, the value of 999 overflows to -25. This is displayed in the HUD as "M25." (The "M" presumably means "minus.")

After reaching a value of 32,767, the ''coin display'' remains at that value. After that, only the hidden ''coin count'' keeps incrementing. That is because the coin count is a signed short, so if the player collects more coins, the coin counter will overflow to -32,768. Since -32768 is not greater than 32,767, the coin display will not increment any further. If one were to collect a 65,636th coin (65,536 for the overflow and 100 for the star), a second 100 coin star would spawn. This was a part of a strategy that could have been applied to collect "To the Top of the Fortress" in 0x A presses<ref>https://youtu.be/GMOxYVtJhOI</ref>, but it wasn't because a faster 0xA strategy was discovered for that star<ref>https://youtu.be/M4M_OyUorRQ</ref>.

==References==
<references/>

Coin limit

2018-11-19T07:23:09Z

Bad boot: /* Coin limit for each course */

Note: Code shown in this section is recreated and may not be the exact code used by the game

A '''coin limit''' is the maximum number of coins that can be collected or saved in a given area. Some courses allow infinite coins to be collected. However, in the NTSC (American) version, the coin counter is programmed to stay at the maximum of 999.

There are two types of coin limits - the 999 coin limit within the course (except Japanese version), and the 255 coin limit that is saved in the save-able records.

==The 999 coin limit==
The limit is intentionally put in by the programmers to prevent the game to count up coins greater than 999:

if(coin_counter > 999) {
coin_counter := 999;
}

==The 255 coin limit==
Separately, there is an unintentional coin limit involving the saved coin score. This value overflows and is set to 0 if the number of coins Mario collected in the course is a multiple of 256. (Not within the course, but when recording the saved coin score after Mario exits the course.) Thus, the easiest way to obtain the highest possible saved coin score in a level is to simply collect 255 coins. 511 and 767 also produce a saved coin score of 255, but collecting more than 255 coins is not as efficient as collecting a star when 255 coins have been collected. 1,023, 1,279, etc. also save as 255, but these coin scores cannot be obtained in the NTSC version.

==Coin limit for each course==
Normally, the number of available coins in the course prevents the player from getting an excess number of coins to reach either of the coin limits. Nonetheless, there are ways for a player to perform infinite coin glitches such as moneybag duplication, [[cloning]] or utilizing certain exploits of the game, allowing infinite coin glitches in certain courses.

Some courses have only a finite number of coins; in these courses, [[cloning]] is impossible and there are no infinite coin glitches. The three courses that don't fall into either of these categories, namely [[Tick Tock Clock]], [[Rainbow Ride]], and [[Bowser in the Fire Sea]], allow for clones to be created, but due to a lack of [[loading zone]]s, the clones fill up the game's [[object slot]]s. Due to this, there is a limitation on the number of coins that can be collected within these three courses.

In the table below, 999 coins represent stages with infinite coin glitches available that does not have clones occupy object slots making the game crash.

{|class="wikitable"
|-
!Course
!Available coins
!Maximum possible coins
!Strategy
|-
!colspan=4|Save-able courses
|-
|[[Bob-omb Battlefield]]||146 coins||999 coins||Breaking/Disappearing cork box glitch Ride cancel (Cloning is possible but limited)
|-
|[[Whomp's Fortress]]||141 coins||999 coins||Breaking/Disappearing cork box glitch
|-
|[[Jolly Roger Bay]]||104 coins||104 coins||
|-
|[[Cool, Cool Mountain]]||154 coins||154 coins||
|-
|[[Big Boo's Haunt]]||151 coins||151 coins||
|-
|[[Hazy Maze Cave]]||139 coins||139 coins||
|-
|[[Lethal Lava Land]]||133 coins||133 coins||
|-
|[[Shifting Sand Land]]||136 coins||999 coins||Breaking/Disappearing cork box glitch (Cloning is possible but limited)
|-
|[[Dire, Dire Docks]]||106 coins||999 coins||Water shell cloning, loading area reset
|-
|[[Snowman's Land]]||127 coins||999 coins||Moneybag duplication Time stop coin collection, loading zone
|-
|[[Wet-Dry World]]||152 coins||999 coins||Chuckya cloning, loading area reset
|-
|[[Tall, Tall Mountain]]||137 coins||999 coins||Bob-omb cloning, loading area reset
|-
|[[Tiny-Huge Island]]||192 coins*||999 coins||Piranha plant glitch Time stop coin collection, loading zone Cloning using chuckya Ride cancel
|-
|[[Tick Tock Clock]]||128 coins||279 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Rainbow Ride]]||146 coins||290 coins**||Bob-omb cloning, with limit due to object slots
|-
!colspan=4|Non-saveable courses
|-
|[[Bowser in the Dark World]]||80 coins||999 coins||Infinite coins from Bowser's fire
|-
|[[Bowser in the Fire Sea]]||80 coins||250 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Bowser in the Sky]]||76 coins||999 coins||Infinite coins from Bowser's fire
|-
|colspan=4|*Including [[the impossible coin]], underground, to the left of the line of 3 coins **Maximum number of objects allowed: 239 for TTC, and 227 in RR.
|}

==Unbounded Coin Limit Glitch (Japanese version)==
In the Japanese version, there is no coin limit within the courses. When the coin counter reaches a value of 1,000, the game runs a few lines of code wherein there is a typo:

if(coin_counter > 999) {
lives_counter := 999;
}

This should be the following:

if(coin_counter > 999) {
coin_counter := 999;
}

Because the lives counter is a signed short, the value of 999 overflows to -25. This is displayed in the HUD as "M25." (The "M" presumably means "minus.")

After reaching a value of 32,767, the ''coin display'' remains at that value. After that, only the hidden ''coin count'' keeps incrementing. That is because the coin count is a signed short, so if the player collects more coins, the coin counter will overflow to -32,768. Since -32768 is not greater than 32,767, the coin display will not increment any further. If one were to collect a 65,636th coin (65,536 for the overflow and 100 for the star), a second 100 coin star would spawn. This was a part of a strategy that could have been applied to collect "To the Top of the Fortress" in 0x A presses<ref>https://youtu.be/GMOxYVtJhOI</ref>, but it wasn't because a faster 0xA strategy was discovered for that star<ref>https://youtu.be/M4M_OyUorRQ</ref>.

==References==
<references/>

Coin limit

2018-11-19T07:19:03Z

Bad boot:

Note: Code shown in this section is recreated and may not be the exact code used by the game

A '''coin limit''' is the maximum number of coins that can be collected or saved in a given area. Some courses allow infinite coins to be collected. However, in the NTSC (American) version, the coin counter is programmed to stay at the maximum of 999.

There are two types of coin limits - the 999 coin limit within the course (except Japanese version), and the 255 coin limit that is saved in the save-able records.

==The 999 coin limit==
The limit is intentionally put in by the programmers to prevent the game to count up coins greater than 999:

if(coin_counter > 999) {
coin_counter := 999;
}

==The 255 coin limit==
Separately, there is an unintentional coin limit involving the saved coin score. This value overflows and is set to 0 if the number of coins Mario collected in the course is a multiple of 256. (Not within the course, but when recording the saved coin score after Mario exits the course.) Thus, the easiest way to obtain the highest possible saved coin score in a level is to simply collect 255 coins. 511 and 767 also produce a saved coin score of 255, but collecting more than 255 coins is not as efficient as collecting a star when 255 coins have been collected. 1,023, 1,279, etc. also save as 255, but these coin scores cannot be obtained in the NTSC version.

==Coin limit for each course==
Normally, the number of available coins in the course prevents the player from getting an excess number of coins to reach either of the coin limits. Nonetheless, there are ways for a player to perform infinite coin glitches such as moneybag duplication, [[cloning]] or utilizing certain exploits of the game, allowing infinite coin glitches in certain courses.

Some courses have only a finite number of coins; in these courses, [[cloning]] is impossible and there are no infinite coin glitches. The three courses that don't fall into either of these categories, namely [[Tick Tock Clock]], [[Rainbow Ride]], and [[Bowser in the Fire Sea]], allow for clones to be created, but due to a lack of [[loading zone]]s, the clones fill up the game's [[object slot]]s. Due to this, there is a limitation on the number of coins that can be collected within these three courses.

In the table below, 999 coins represent stages with infinite coin glitches available that does not have clones occupy object slots making the game crash.

{|class="wikitable"
|-
!Course
!Available coins
!Maximum possible coins
!Strategy
|-
!colspan=4|Save-able courses
|-
|[[Bob-omb Battlefield]]||146 coins||999 coins||Breaking/Disappearing cork box glitch Ride cancel (Cloning is possible but limited)
|-
|[[Whomp's Fortress]]||141 coins||999 coins||Breaking/Disappearing cork box glitch
|-
|[[Jolly Roger Bay]]||104 coins||104 coins||
|-
|[[Cool, Cool Mountain]]||154 coins||154 coins||
|-
|[[Big Boo's Haunt]]||151 coins||151 coins||
|-
|[[Hazy Maze Cave]]||139 coins||139 coins||
|-
|[[Lethal Lava Land]]||133 coins||133 coins||
|-
|[[Shifting Sand Land]]||136 coins||999 coins||Breaking/Disappearing cork box glitch (Cloning is possible but limited)
|-
|[[Dire, Dire Docks]]||106 coins||999 coins||Shell cloning, loading area reset
|-
|[[Snowman's Land]]||127 coins||999 coins||Moneybag duplication
|-
|[[Wet-Dry World]]||152 coins||999 coins||Chuckya cloning, loading area reset
|-
|[[Tall, Tall Mountain]]||137 coins||999 coins||Bob-omb cloning, loading area reset
|-
|[[Tiny-Huge Island]]||192 coins*||999 coins||Piranha plant glitch Time stop coin collection Cloning using chuckya Ride cancel
|-
|[[Tick Tock Clock]]||128 coins||279 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Rainbow Ride]]||146 coins||290 coins**||Bob-omb cloning, with limit due to object slots
|-
!colspan=4|Non-saveable courses
|-
|[[Bowser in the Dark World]]||80 coins||999 coins||Infinite coins from Bowser's fire
|-
|[[Bowser in the Fire Sea]]||80 coins||250 coins**||Bob-omb cloning, with limit due to object slots
|-
|[[Bowser in the Sky]]||76 coins||999 coins||Infinite coins from Bowser's fire
|-
|colspan=4|*Including [[the impossible coin]], underground, to the left of the line of 3 coins **Maximum number of objects allowed: 239 for TTC, and 227 in RR.
|}

==Unbounded Coin Limit Glitch (Japanese version)==
In the Japanese version, there is no coin limit within the courses. When the coin counter reaches a value of 1,000, the game runs a few lines of code wherein there is a typo:

if(coin_counter > 999) {
lives_counter := 999;
}

This should be the following:

if(coin_counter > 999) {
coin_counter := 999;
}

Because the lives counter is a signed short, the value of 999 overflows to -25. This is displayed in the HUD as "M25." (The "M" presumably means "minus.")

After reaching a value of 32,767, the ''coin display'' remains at that value. After that, only the hidden ''coin count'' keeps incrementing. That is because the coin count is a signed short, so if the player collects more coins, the coin counter will overflow to -32,768. Since -32768 is not greater than 32,767, the coin display will not increment any further. If one were to collect a 65,636th coin (65,536 for the overflow and 100 for the star), a second 100 coin star would spawn. This was a part of a strategy that could have been applied to collect "To the Top of the Fortress" in 0x A presses<ref>https://youtu.be/GMOxYVtJhOI</ref>, but it wasn't because a faster 0xA strategy was discovered for that star<ref>https://youtu.be/M4M_OyUorRQ</ref>.

==References==
<references/>

Unsolved single-goal challenges

2018-10-22T15:51:26Z

Bad boot: Reverted edits by Nitrusgamer (talk) to last revision by JoshDuMan

This is a list of single goal challenges that are incredibly difficult/impossible with current knowledge. None of these have been completed.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Collecting [[Wing Mario over the Rainbow]] Capless and/or Cannonless
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch and living
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Crashing the game by triggering death barrier before activating the TotWC starting textbox
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating 4 or 5 stars at once in BoB
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)
* Get back on the platform after falling off in the Bowser 2 fight
* Moving during timestop in JRB (to get shell clones)

==Former challenges on this list which have been accomplished==
* Beating SA in one irl breath
:* https://youtu.be/3BueQSrscks
* Picking up the cannon bob-omb on the same frame as leaving its radius
:* https://youtu.be/uFuC5DcbsjU
* Putting the Ukiki that steals your hat on the monkey cage
:* https://www.youtube.com/watch?v=oErcSAAwy4U
* Collecting Mystery of the Monkey Cage without changing the HOLP
:* https://youtu.be/UhchV2Kr_ig

Unsolved single-goal challenges

2018-10-19T02:24:36Z

Bad boot:

This is a list of single goal challenges that are incredibly difficult/impossible with current knowledge. None of these have been completed.

* Clipping from the bottom area of Wiggler's cave to the top area, or vice versa
* Grabbing Ukiki without pressing B (useful for the BBC)
* Collecting Mystery of the Monkey Cage without changing the HOLP for an arbitrary HOLP
* Collecting [[Wing Mario over the Rainbow]] Capless and/or Cannonless
* Transport cloning with Wiggler or Skeeter
* Performing a transport clone with 4 simultaneous pushers
* Picking up the cannon bob-omb on the same frame as leaving its radius
* Collecting the new impossible coin (THI)
* Killing the mystery goomba and collecting its coin
* Collecting the red coin in BitDW at the start without using the ! Switch
* Getting infinite coins in CCM
* Cloning in LLL (maybe with fall damage instant release via falling from HSF)
* Reproducing the TTC upwarp
* Grab a bob-omb fake during boiling
* Vertical PU death in LLL
* HSWK between towers in TotWC
* Crashing the game by triggering death barrier before activating the TotWC starting textbox
* Survive in a vertical PU with a shell clone released in it
* Collecting the BitDW key from underneath the ground, causing you to collect the key on the death floor
* Collect a star during a demo sequence
* Activating 4 or 5 stars at once in BoB
* Activating more than 4 stars at once anywhere
* Reversing the one-way teleport in [[THI]]
* Ground-pounding [[Chain Chomp]]'s post without interacting with the red coin (e.g. collecting its two coin value)
* Escaping from one of the fish tanks in the JRB room (starting with zero speed and damage counter)

A Button Challenge

2018-10-14T20:29:51Z

Bad boot:

{{A Button Challenge infobox}}
The '''A Button Challenge''', '''ABC''' for short, is a [[challenge]] in which the number of presses of the [[A button]] is minimized, whether on a per-mission or a per-file basis. Because the A button makes Mario jump, great creativity and precision are required to progress in the game without using this "vital" function. The ABC is often connected to the discoveries of new glitches and techniques that can be used more generally throughout the game. Much of the material on the [https://www.youtube.com/user/pannenkoek2012 pannenkoek2012] and [https://www.youtube.com/user/pannenkeok2012 UncommentatedPannen] channels is related to the A Button Challenge, with only 21 remaining A presses (15 unique A presses) left to optimize.

== History ==
Although much of the progress in the ABC has been made since 2013, the ABC existed for over a decade earlier. Pieces of what would become the ABC were present in different terms, as early as 2001 on Walton Dell's site on multiple level pages.<ref>https://web.archive.org/web/20020614010118/http://www.wdell.com/videogames/sm64/course01/</ref> Curtis Bright, who runs sm64.com, was keeping track of ABC at least as early as December of 2006.<ref>https://web.archive.org/web/20061209073313/http://www.student.cs.uwaterloo.ca/~cbright/sm64/a-presses.html</ref> Thiago Trujillo had what is the earliest, nearly complete count for the game (that we have access to) with a total count of about 263 presses.<ref>http://www.oocities.org/thiagotrujillo/abut.html</ref> (This list is missing all navigation presses, two of the [[DDD]] stars, three of the [[TTC]] stars, one star in [[RR]], and [[BitS]].)

Pannenkoek's first ABC video was for 5 Itty Bitty Secrets, and was released in August 2013.<ref>https://www.youtube.com/watch?v=Xy7XDStV5WE</ref> The count at this point was about 212 presses, although this number dropped fairly quickly. Within the first 4 months, the count had fallen nearly 100 presses, and was down to 118. Over the next five years, many different people have worked on removing as many counts as possible, and the number has dropped to only 21 A presses in a 120 star run (as well as 0 in any%).

== A Presses Left ==
A '''unique A press''' refers to a single circumstance under which the A button must be pressed during a run. This circumstance may occur multiple times, leading to multiple A presses; if a workaround is found for the unique A press, all of those individual A presses may be saved.

For example, if entering a course requires an A press, the case of entering the course is a unique A press, even if said course must be visited multiple times over the course of a run.

Below is a table of unique A presses in the [[A Button Challenge]].<ref>https://www.youtube.com/watch?v=RHU1BdDCClE</ref>

{|class="wikitable sortable" border="0" cellpadding="1" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|JRB
|To collect the chest star
|-
|#2
|1
|LLL
|To get to the Elevator Tour star platform
|-
|#3
|2
|SSL
|To get out of the pyramid elevator
|-
|#4, #5
|1
|THI
|To collect red coins
|-
|#6
|3
|TTC
|To get out of the treadmill grinding spot
|-
|#7
|1
|TTC
|To get out of the pendulum box pedro spot with vertical speed
|-
|#8
|1
|TTC
|To get past the thwomp
|-
|#9
|1
|PSS
|
To collect the star
|-
|#10, #11
|1
|WMotR
|
To collect red coins
|-
|#12
|1
|BitFS
|To get past the pole (saved on Wii VC)
|-
|#13
|4
|Castle
|To enter TTC (6 except on JP N64)
|-
|#14
|1
|Castle
|To go to RR
|-
|#15
|1
|Castle
|To go to WMotR
|}

Additionally, some levels require the A button to be held for the level, but not started on that specific star necessarily. These presses can be tied to earlier presses to lower counts in longer runs.

Below is a table of all levels that require half an A-Press.
{|class="wikitable sortable" border="0" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|HMC
|To do kicks on the elevator
|-
|#2
|1
|DDD
|To clone the whirlpool and poles
|-
|#3
|1
|DDD
|To clone coin spawners for 100 coins
|}

== References ==
<references />

A Button Challenge

2018-10-14T20:25:18Z

Bad boot:

{{A Button Challenge infobox}}
The '''A Button Challenge''', '''ABC''' for short, is a [[challenge]] in which the number of presses of the [[A button]] is minimized, whether on a per-mission or a per-file basis. Because the A button makes Mario jump, great creativity and precision are required to progress in the game without using this "vital" function. The ABC is often connected to the discoveries of new glitches and techniques that can be used more generally throughout the game. Much of the material on the [https://www.youtube.com/user/pannenkoek2012 pannenkoek2012] and [https://www.youtube.com/user/pannenkeok2012 UncommentatedPannen] channels is related to the A Button Challenge, with only 21 remaining A presses (17 unique A presses) left to optimize.

== History ==
Although much of the progress in the ABC has been made since 2013, the ABC existed for over a decade earlier. Pieces of what would become the ABC were present in different terms, as early as 2001 on Walton Dell's site on multiple level pages.<ref>https://web.archive.org/web/20020614010118/http://www.wdell.com/videogames/sm64/course01/</ref> Curtis Bright, who runs sm64.com, was keeping track of ABC at least as early as December of 2006.<ref>https://web.archive.org/web/20061209073313/http://www.student.cs.uwaterloo.ca/~cbright/sm64/a-presses.html</ref> Thiago Trujillo had what is the earliest, nearly complete count for the game (that we have access to) with a total count of about 263 presses.<ref>http://www.oocities.org/thiagotrujillo/abut.html</ref> (This list is missing all navigation presses, two of the [[DDD]] stars, three of the [[TTC]] stars, one star in [[RR]], and [[BitS]].)

Pannenkoek's first ABC video was for 5 Itty Bitty Secrets, and was released in August 2013.<ref>https://www.youtube.com/watch?v=Xy7XDStV5WE</ref> The count at this point was about 212 presses, although this number dropped fairly quickly. Within the first 4 months, the count had fallen nearly 100 presses, and was down to 118. Over the next five years, many different people have worked on removing as many counts as possible, and the number has dropped to only 21 A presses in a 120 star run (as well as 0 in any%).

== A Presses Left ==
A '''unique A press''' refers to a single circumstance under which the A button must be pressed during a run. This circumstance may occur multiple times, leading to multiple A presses; if a workaround is found for the unique A press, all of those individual A presses may be saved.

For example, if entering a course requires an A press, the case of entering the course is a unique A press, even if said course must be visited multiple times over the course of a run.

Below is a table of unique A presses in the [[A Button Challenge]].<ref>https://www.youtube.com/watch?v=RHU1BdDCClE</ref>

{|class="wikitable sortable" border="0" cellpadding="1" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|JRB
|To collect the chest star
|-
|#2
|1
|LLL
|To get to the Elevator Tour star platform
|-
|#3
|2
|SSL
|To get out of the pyramid elevator
|-
|#4, #5
|1
|THI
|To collect red coins
|-
|#6
|3
|TTC
|To get out of the treadmill grinding spot
|-
|#7
|1
|TTC
|To get out of the pendulum box pedro spot with vertical speed
|-
|#8
|1
|TTC
|To get past the thwomp
|-
|#9
|1
|PSS
|
To collect the star
|-
|#10, #11
|1
|WMotR
|
To collect red coins
|-
|#12
|1
|BitFS
|To get past the pole (saved on Wii VC)
|-
|#13
|4
|Castle
|To enter TTC (6 except on JP N64)
|-
|#14
|1
|Castle
|To go to RR
|-
|#15
|1
|Castle
|To go to WMotR
|}

Additionally, some levels require the A button to be held for the level, but not started on that specific star necessarily. These presses can be tied to earlier presses to lower counts in longer runs.

Below is a table of all levels that require half an A-Press.
{|class="wikitable sortable" border="0" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|HMC
|To do kicks on the elevator
|-
|#2
|1
|DDD
|To clone the whirlpool and poles
|-
|#3
|1
|DDD
|To clone coin spawners for 100 coins
|}

== References ==
<references />

A Button Challenge

2018-10-14T20:23:53Z

Bad boot: /* History */

{{A Button Challenge infobox}}
The '''A Button Challenge''', '''ABC''' for short, is a [[challenge]] in which the number of presses of the [[A button]] is minimized, whether on a per-mission or a per-file basis. Because the A button makes Mario jump, great creativity and precision are required to progress in the game without using this "vital" function. The ABC is often connected to the discoveries of new glitches and techniques that can be used more generally throughout the game. Much of the material on the [https://www.youtube.com/user/pannenkoek2012 pannenkoek2012] and [https://www.youtube.com/user/pannenkeok2012 UncommentatedPannen] channels is related to the A Button Challenge, with only 21 remaining A presses (17 unique A presses) left to optimize.

== History ==
Although much of the progress in the ABC has been made since 2013, the ABC existed for over a decade earlier. Pieces of what would become the ABC were present in different terms, as early as 2001 on Walton Dell's site on multiple level pages.<ref>https://web.archive.org/web/20020614010118/http://www.wdell.com/videogames/sm64/course01/</ref> Curtis Bright, who runs sm64.com, was keeping track of ABC at least as early as December of 2006.<ref>https://web.archive.org/web/20061209073313/http://www.student.cs.uwaterloo.ca/~cbright/sm64/a-presses.html</ref> Thiago Trujillo had what is the earliest, nearly complete count for the game (that we have access to) with a total count of about 263 presses.<ref>http://www.oocities.org/thiagotrujillo/abut.html</ref> (This list is missing all navigation presses, two of the [[DDD]] stars, three of the [[TTC]] stars, one star in [[RR]], and [[BitS]].)

Pannenkoek's first ABC video was for 5 Itty Bitty Secrets, and was released in August 2013.<ref>https://www.youtube.com/watch?v=Xy7XDStV5WE</ref> The count at this point was about 212 presses, although this number dropped fairly quickly. Within the first 4 months, the count had fallen nearly 100 presses, and was down to 118. Over the next five years, many different people have worked on removing as many counts as possible, and the number has dropped to only 21 A presses in a 100% run (as well as 0 in any%).

== A Presses Left ==
A '''unique A press''' refers to a single circumstance under which the A button must be pressed during a run. This circumstance may occur multiple times, leading to multiple A presses; if a workaround is found for the unique A press, all of those individual A presses may be saved.

For example, if entering a course requires an A press, the case of entering the course is a unique A press, even if said course must be visited multiple times over the course of a run.

Below is a table of unique A presses in the [[A Button Challenge]].<ref>https://www.youtube.com/watch?v=RHU1BdDCClE</ref>

{|class="wikitable sortable" border="0" cellpadding="1" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|JRB
|To collect the chest star
|-
|#2
|1
|LLL
|To get to the Elevator Tour star platform
|-
|#3
|2
|SSL
|To get out of the pyramid elevator
|-
|#4, #5
|1
|THI
|To collect red coins
|-
|#6
|3
|TTC
|To get out of the treadmill grinding spot
|-
|#7
|1
|TTC
|To get out of the pendulum box pedro spot with vertical speed
|-
|#8
|1
|TTC
|To get past the thwomp
|-
|#9
|1
|PSS
|
To collect the star
|-
|#10, #11
|1
|WMotR
|
To collect red coins
|-
|#12
|1
|BitFS
|To get past the pole (saved on Wii VC)
|-
|#13
|4
|Castle
|To enter TTC (6 except on JP N64)
|-
|#14
|1
|Castle
|To go to RR
|-
|#15
|1
|Castle
|To go to WMotR
|}

Additionally, some levels require the A button to be held for the level, but not started on that specific star necessarily. These presses can be tied to earlier presses to lower counts in longer runs.

Below is a table of all levels that require half an A-Press.
{|class="wikitable sortable" border="0" cellspacing="1" style="width: 50%;"
|-
! scope="col"|A Press #
! scope="col"|Multiplicity
! scope="col"|Stage
! scope="col"|Purpose
|-
|#1
|1
|HMC
|To do kicks on the elevator
|-
|#2
|1
|DDD
|To clone the whirlpool and poles
|-
|#3
|1
|DDD
|To clone coin spawners for 100 coins
|}

== References ==
<references />

Instant warp

2018-10-03T16:10:48Z

Bad boot:

An '''instant warp''' is a special [[Surfaces|floor]] that, when passed above, causes Mario to instantly move without interrupting normal gameplay. In the case of '''loading zones''', Mario enters a different area in the level and a different set of objects loads. In the case of the '''endless staircase''', Mario instantly changes position but not area. Because normal gameplay is not interrupted when triggering an instant warp, interesting side effects can occur.

When an instant warp displaces Mario, it moves the camera as well to maintain its position relative to Mario. If the camera is locked and Mario gets displaced a large distance, the camera can enter a PU, causing the Nintendo 64 versions of the game to crash. This is possible by repeatedly displacing Mario using the endless staircase<ref>https://www.youtube.com/watch?v=M9UPeSpZZPw</ref> or the TTM slide<ref>https://www.youtube.com/watch?v=Be_RbwFWh30</ref>.

If the warp displaces Mario out of bounds, then the [[OoB Failsafe|OoB failsafe]] mechanism triggers, effectively canceling the displacement<ref>https://www.youtube.com/watch?v=gvQMNQlgu3s&feature=youtu.be&t=558</ref>.

==Locations==
*[[Castle]]: The endless staircase is an instant warp that is not a loading zone. It displaces Mario by -205 in the y direction and 410 in the z direction.
*[[Dire, Dire Docks]]: There is a two-way loading zone at the midpoint of the tunnel. It displaces Mario by 8192 in the x direction.
*[[Shifting Sand Land]]: There is a two-way loading zone inside the pyramid in the entrance to the [[Eyerok]] boss fight.
*[[Tall, Tall Mountain]]: There are two one-way loading zones along the slide. These displace Mario by (10240, 7168, 10240) and (-11264, 13312, 3072). They are located inside tunnels, which prevent Mario from activating them from above.
*[[Wet Dry World]]: There is a two-way loading zone in the tunnel leading to the town.

== Glitches ==
=== Cloning ===
When passing through a loading zone, all objects unload in order to make room for the objects in the new area. If Mario is holding an object when he passes through a loading zone, he will be holding either a vacant object slot or an object from the new area.

=== New Area Not Loading ===
If Mario gets past a loading zone without activating it (either by passing it with hyperspeed or clipping behind it in some other way), then the new area does not load and the old one does not unload.

==References==

Hyperspeed

2018-09-18T18:24:10Z

Bad boot:

Hyperspeed is a term that refers to an abnormally large amount of speed, usually for [[Mario]]. This speed is often obtained via [[Glitches|glitches]] or physics exploits. Hyperspeed is often helpful in speedruns because it allows quicker movement, as well as the ability to clip through walls. It helps in some [[Challenge|challenges]].

List of hyperspeed methods:
* [[Backward Long Jump]]
* [[Hyperspeed Walking]]
* [[Hyperspeed Wall Kicks]]
* [[Hyperspeed Water Sliding]]
* [[C^ Hyperspeed]]
* [[Hyperspeed Punching]]
* [[Hyperspeed Grinding]]
* [[Subframe Grinding]]
* [[Hyperspeed Turnaround]]
* [[Hyperspeed Jump Kicking]]
* [[Hyperspeed Slide Kicking]]
* [[Hyperspeed Braking]]
* [[Backward Shell Hyperspeed]]
* [[10k Glitch]]

Some techniques cause Mario's position to change quickly, without technically changing his speed:
* [[Shell Mario]]
* [[Bloated Bob-Omb]]

Hyperspeed

2018-09-18T18:23:36Z

Bad boot: Reverted edits by JoshDuMan (talk) to last revision by Sunky

Hyperspeed is a term that refers to an abnormally large amount of speed, usually for [[Mario]]. This speed is often obtained via [[Glitches|glitches]] or physics exploits. Hyperspeed is often helpful in speedruns because it allows quicker movement, as well as the ability to clip through walls. It helps in some [[Challenge|challenges]].

List of hyperspeed methods:
* [[Backward Long Jump]]
* [[Hyperspeed Walking]]
* [[Hyperspeed Wall Kicks]]
* [[Hyperspeed Water Sliding]]
* [[C^ Hyperspeed]]
* [[Hyperspeed Punching]]
* [[Hyperspeed Grinding]]
* [[Subframe Grinding]]
* [[Hyperspeed Turnaround]]
* [[Hyperspeed Jump Kicking]]
* [[Hyperspeed Slide Kicking]]
* [[Hyperspeed Braking]]
* [[Backward Shell Hyperspeed]]
* [[10.000 Glitch]]

Some techniques cause Mario's position to change quickly, without technically changing his speed:
* [[Shell Mario]]
* [[Bloated Bob-Omb]]

Template:RTA Button Challenge Infobox

2018-09-09T03:16:02Z

Bad boot: Merry go around and THI 100 should be blue

{{Challenge_infobox
|title= Real Time A Button Challenge
|abbreviation= RTABC
|stars=62
|stars-overall=59
|beatable=No
|button-presses-any=21
|button-presses-full=228
|bob1=1|bob2=1|bob3=0|bob4=0.5|bob5=0|bob6=1|bob7=1
|wf1=0|wf2=0|wf3=1|wf4=1|wf5=0.5|wf6=1|wf7=1
|jrb1=1|jrb2=1|jrb3=0|jrb4=0|jrb5=0|jrb6=0|jrb7=0
|ccm1=1|ccm2=1|ccm3=1|ccm4=1|ccm5=1|ccm6=1|ccm7=1
|bbh1=1|bbh2=0|bbh3=0|bbh4=0|bbh5=0|bbh6=0|bbh7=1
|hmc1=1|hmc2=0|hmc3=0|hmc4=0|hmc5=0|hmc6=0|hmc7=0
|lll1=1|lll2=1|lll3=1|lll4=1|lll5=0|lll6=0|lll7=1
|ssl1=1|ssl2=1|ssl3=0|ssl4=0|ssl5=0.5|ssl6=0|ssl7=0
|ddd1=0.5|ddd2=0.5|ddd3=0|ddd4=0.5|ddd5=1|ddd6=0.5|ddd7=0
|sl1=0|sl2=1|sl3=1|sl4=1|sl5=1|sl6=1|sl7=1
|wdw1=1|wdw2=0|wdw3=1|wdw4=0|wdw5=0|wdw6=0|wdw7=1
|ttm1=1|ttm2=1|ttm3=1|ttm4=1|ttm5=1|ttm6=1|ttm7=1
|thi1=1|thi2=1|thi3=1|thi4=1|thi5=0|thi6=1|thi7=0
|ttc1=0|ttc2=0|ttc3=0|ttc4=0|ttc5=0|ttc6=0|ttc7=0
|rr1=0|rr2=0|rr3=0|rr4=0|rr5=0|rr6=0|rr7=0
|slide1=0|slide2=1
|aquarium=1
|totwc=1|cotmc=1|vcutm=1
|wmotr=0
|mips1=1|mips2=1
|toad1=1|toad2=1|toad3=1
|bitdw=0|bitfs=0|bits=0
}}

Time stop

2018-09-02T19:15:15Z

Bad boot:

Time Stop (also known as Timestop) is a game mechanic present in all versions of SM64. There is a trick exclusive to the [[J 1.0]] version, which allows [[Mario]] to move around when objects are frozen due to a text box that is supposed to appear.

== Intended Behavior ==
The intended behavior of the Time Stop mechanism is to freeze everything except [[Mario]] and the talking object when Mario is in a textbox. Alternatively, during a star spawning cutscene all objects are frozen (including Mario) aside from any stars that are spawning.

== Glitch ==
On the [[J 1.0]] version of SM64, queueing a textbox immediately stops time for everything besides the talking object and Mario, ''regardless if Mario is actually in a state to see the textbox''. This can be exploited to move around stages with everything besides Mario and the talking object frozen. There are two ways to activate the Time Stop trick, proximity textboxes and textboxes from holdable objects. Neither way works with all textboxes of either type.

=== Proximity Textboxes ===
"Proximity Textboxes" are defined as textboxes that appear when Mario is near an object. If [[Mario]] jumps right when the textbox is about to activate, then Mario will be able to move in midair until he touches ground again, after which the textbox will start. While Mario is in the air, time will be stopped.

=== Holdable Object Textboxes ===
By picking up an object that normally triggers a text box and then dropping it before it can display the textbox, time stop can be activated. Mario can safely touch the ground and move around at this point without restarting time. The only known example of this type of Time Stop is the lower [[Ukiki]] in Tall Tall Mountain.

Time is not stopped for the object that was used to stop it in either case.

== Effects ==
Objects (in most cases) stay inanimate, and keep the exact same state they were in when time was stopped. If an object was intangible due to being far from Mario, it will stay intangible even when Mario comes near it until time is started again, because objects do not update in time stop.

== Other Versions of SM64 ==
The developers patched this glitch in all versions of the game besides J 1.0, by making sure that time does not stop until a textbox is in the process of being displayed. Time still stops for textboxes on other versions, but there is no known way to move around during this state.

The proximity method for Time Stop is still possible in other versions, but time does not stop and the textbox does not appear until Mario touches the ground. This allows for tricks such as getting a 0.0 time on [[Koopa the Quick]] in both of their races.

'Impossible' Single-Goal Challenges

2018-09-02T18:36:11Z

Bad boot: Redirected page to "Impossible" Single-Goal Challenges

#REDIRECT [["Impossible" Single-Goal Challenges]]

10k glitch

2018-08-24T05:27:37Z

Bad boot:

{{stub}}
{{rewrite}}

The '''10k glitch''' is a [[glitch]] in which speed is increased by a multiplier that increases by 1 for every 10,000 speed you have (hence the name). It is used in the [[A Button Challenge]].
==Execution==
To do it, you must be in a braking state (holding backwards on the analog stick as if you were about to sideflip) with high forward speed (at least 20k) and then touch a [[slippery slope]]. Since the [[List of Courses|course]] will often be too small to move into the slope with >20k speed, the simplest way to do it is with PU speed.

10k glitch

2018-08-24T05:26:32Z

Bad boot:

{{stub}}

The '''10k glitch''' is a [[glitch]] in which speed is increased by a multiplier that increases by 1 for every 10,000 speed you have (hence the name). It is used in the [[A Button Challenge]].
==Execution==
To do it, you must be in a braking state (holding backwards on the analog stick as if you were about to sideflip) with high forward speed (at least 20k) and then touch a [[slippery slope]]. Since the [[List of Courses|course]] will often be too small to move into the slope with >20k speed, the simplest way to do it is with PU speed.

10.000 Glitch

2018-08-24T05:25:58Z

Bad boot: Bad boot moved page 10.000 Glitch to 10k Glitch

#REDIRECT [[10k Glitch]]

10k glitch

2018-08-24T05:25:57Z

Bad boot: Bad boot moved page 10.000 Glitch to 10k Glitch

{{stub}}

The '''10.000 glitch''' is a [[glitch]] in which speed is increased by a multiplier that increases by 1 for every 10k speed you have (hence the name). It is used in the [[A Button Challenge]].
==Execution==
To do it, you must be in a braking state (holding backwards on the analog stick as if you were about to sideflip) with high forward speed (at least 20k) and then touch a [[slippery slope]]. Since the [[List of Courses|course]] will often be too small to move into the slope with >20k speed, the simplest way to do it is with PU speed.

Wii VC Round-to-Zero

2018-08-23T05:25:43Z

Bad boot:

[[File:WiiVC BitFS.png|thumb|300px|right|Stream by Switchpalacecorner, after 71.5 hours of raising in Wii Virtual Console]]
[[File:WiiVC BitFS 146hr.png|thumb|300px|right|After 146.5 hours (6 days 2.5 hrs)]]
'''Wii VC Round-to-Zero''' refers to an emulation inaccuracy in the [[Virtual Console|Wii Virtual Console]] (Wii VC). When converting a double precision floating point number (a "double") to a single precision floating point number (a "float"), the N64 typically uses the round-to-nearest rounding mode. This means that if the double is not exactly equal to a float, it will round up or down to the float that is closest in value to the original number. While this behavior is accurately emulated by most emulators and the Wii U VC, the Wii VC instead uses the round-to-zero mode. This mode will always round the double up if it is negative, and round it down if it is positive.

While the programmers did not intentionally use doubles very often, favoring single precision floats instead, they occasionally used them accidentally.

<syntaxhighlight lang="c">
y -= sins(t) * 0.58;
t += 0x100;
</syntaxhighlight>

In the above code sample, <code>y</code> and <code>sins(t)</code> are both single precision floats. However, in C, the numeric literal <code>0.58</code> is a double since it lacks a trailing <code>f</code>, as in <code>0.58f</code>. This causes the expression to evaluate to a double, which is then converted to a float before being stored in <code>y</code>. Examples such as this one arise in many places in the game's source code, and over time they result in large discrepancies between the N64 and Wii VC versions of the game. For this reason, TASes produced for one of these platforms cannot generally be played back on the other without desync.

The example given above is taken from the code controlling the oscillation of the platforms at the beginning of [[Bowser in the Fire Sea]]. Using the N64's rounding mode, the <code>y</code> variable, which represents the platform's height, will repeatedly return to its original value and continue oscillating with fixed maximum height. Even though each double to single conversion produces a small amount of error, this error balances out over the course of the platform's cycle. On the Wii VC, however, the error always accumulates in the same direction (upward if the platform is below ''y'' = 0, and downward if the platform is above ''y'' = 0), and so the platform slowly drifts in the vertical direction. This is known as '''Wii VC platform drift'''.

The platforms at the beginning of the level are below ''y'' = 0, and so they gradually rise upward. Over the course of several days, they become high enough that they can be used to reach the elevator past the pole, which previously required one A press to get past. It takes eight days for the platform to get high enough to dive recover into the elevator shaft, but using [[Vertical Speed Conservation|VSC]] with a lava boost, this time is reduced to just under three days.

The glitch was discovered by '''Andru!''' when he left his Wii powered on overnight while in Bowser in the Fire Sea, and noticed that the oscillating platforms had left their original positions.<ref>https://www.youtube.com/watch?v=MFxJuq3FRgI</ref>

==Applications==
After several failed attempts by various players, the A press save in Bowser in the Fire Sea was console verified RTA on 20 Jun 2018 by ethanwhitesm64,<ref>[https://youtu.be/B1m-5LWOxW0]https://youtu.be/B1m-5LWOxW0</ref>. Six days later, pannenkoek2012 TASed the red coin star in zero A presses using a modified N64 emulator that replicated the rounding error.<ref>[https://youtu.be/Aa_CciaM4aM]https://youtu.be/Aa_CciaM4aM</ref>

No other console or emulator is known to reproduce this rounding inaccuracy, including the Wii U VC. At the time of its discovery, the bug did not occur on the Dolphin emulator, but has since been corrected.

No other objects are known to have similarly exploitable behavior, though the rounding bug does cause many discrepancies between the original and Wii VC versions of the game, including slightly different surface normals.

==References==
<references/>

Wii VC Round-to-Zero

2018-08-15T06:00:07Z

Bad boot:

[[File:WiiVC BitFS.png|thumb|300px|right|Stream by Switchpalacecorner, after 71.5 hours of raising in Wii Virtual Console]]
[[File:WiiVC BitFS 146hr.png|thumb|300px|right|After 146.5 hours (6 days 2.5 hrs)]]
'''Wii VC Round-to-Zero''' refers to an emulation inaccuracy in the [[Virtual Console|Wii Virtual Console]] (Wii VC). When converting a double precision floating point number (a "double") to a single precision floating point number (a "float"), the N64 typically uses the round-to-nearest rounding mode. This means that if the double is not exactly equal to a float, it will round up or down to the float that is closest in value to the original number. While this behavior is accurately emulated by most emulators and the Wii U VC, the Wii VC instead uses the round-to-zero mode. This mode will always round the double up if it is negative, and round it down if it is positive.

While the programmers did not intentionally use doubles very often, favoring single precision floats instead, they occasionally used them accidentally.

<syntaxhighlight lang="c">
y -= sins(t) * 0.58;
t += 0x100;
</syntaxhighlight>

In the above code sample, <code>y</code> and <code>sins(t)</code> are both single precision floats. However, in C, the numeric literal <code>0.58</code> is a double since it lacks a trailing <code>f</code>, as in <code>0.58f</code>. This causes the expression to evaluate to a double, which is then converted to a float before being stored in <code>y</code>. Examples such as this one arise in many places in the game's source code, and over time they result in large discrepancies between the N64 and Wii VC versions of the game. For this reason, TASes produced for one of these platforms can not generally be played back on the other without desync.

The example given above is taken from the code controlling the oscillation of the platforms at the beginning of [[Bowser in the Fire Sea]]. Using the N64's rounding mode, the <code>y</code> variable, which represents the platform's height, will repeatedly return to its original value and continue oscillating with fixed maximum height. Even though each double to single conversion produces a small amount of error, this error balances out over the course of the platform's cycle. On the Wii VC, however, the error always accumulates in the same direction (upward if the platform is below ''y'' = 0, and downward if the platform is above ''y'' = 0), and so the platform slowly drifts in the vertical direction. This is known as '''Wii VC platform drift'''.

The platforms at the beginning of the level are below ''y'' = 0, and so they gradually rise upward. Over the course of several days, they become high enough that they can be used to reach the elevator past the pole, which previously required one A press to get past. It takes eight days for the platform to get high enough to dive recover into the elevator shaft, but using [[Vertical Speed Conservation|VSC]] with a lava boost, this time is reduced to just under three days.

The glitch was discovered by '''Andru!''' when he left his Wii powered on overnight while in Bowser in the Fire Sea, and noticed that the oscillating platforms had left their original positions.<ref>https://www.youtube.com/watch?v=MFxJuq3FRgI</ref>

==Applications==
After several failed attempts by various players, the A press save in Bowser in the Fire Sea was console verified RTA on 20 Jun 2018 by ethanwhitesm64,<ref>[https://youtu.be/B1m-5LWOxW0]https://youtu.be/B1m-5LWOxW0</ref>. Six days later, pannenkoek2012 TASed the red coin star in zero A presses using a modified N64 emulator that replicated the rounding error.<ref>[https://youtu.be/Aa_CciaM4aM]https://youtu.be/Aa_CciaM4aM</ref>

No other console or emulator is known to reproduce this rounding inaccuracy, including the Wii U VC. At the time of its discovery, the bug did not occur on the Dolphin emulator, but has since been corrected.

No other objects are known to have similarly exploitable behavior, though the rounding bug does cause many discrepancies between the original and Wii VC versions of the game, including slightly different surface normals.

==References==
<references/>

Same Input Challenge

2018-07-27T07:27:00Z

Bad boot: /* Rules */

The '''Same Input Challenge''''s goal is collecting as many different stars from a single set of inputs as possible, while only varying the savestate for the TAS. The Mario 64 variant was originally created by [https://www.youtube.com/channel/UCla5Eru3DbPgxz6LwSBOyaw Sidney], with the goal of "making a .m64 that can collect two completely different stars with the same .m64, but different .st." The current world record is six stars.

== Rules ==

* Must start from star select (if the level has one), pause exit (if a castle star), or on the first frame of level.
* No leaving a level (including Bowser death)
* In level warps are fine, as long as they do not exit the course (No DDD exit, Bowser death, TotWC death, etc.)
* Only one star per save state, 100 coin stars/castle stars must be collected separately
* Save states must be achievable without the use of hacks (No impossible RNG, impossible HOLP, etc.)
* Stars must be yellow when collected
* May not press the start button

Action

2018-07-25T06:10:04Z

Bad boot:

An '''action''' is a particular state that Mario can be in. [[Long jumping]], [[crouching]], and [[walking]] are examples of actions. Each action has code controlling high level behavior such as Mario's movement while in the action, as well as transitions to other actions.

It is likely the game developers referred to actions as "states", as evidenced by the "STA" label on one of the debug menus. The name "action" was chosen by the community as a less ambiguous alternative.

If Mario's current action is hacked to be an invalid action value, the game will either freeze or softlock, since such an action lacks associated code. There are 230 valid actions in the game, but some of these are accessible only through hacking. In addition to these, there are two "pseudo-actions", 0x050 and 0x051, that immediately transition to another action. Specifically, they are "begin sliding" actions, and they transition into either butt slide or stomach slide, depending on whether Mario is facing uphill or downhill. There is evidence of one action, action 0x00E, that was defined but whose code was never implemented.

== Action groups ==

An action is represented as a 32-bit value. The lowest nine bits are a unique ID for the action, ranging in value from 0x000 to 0x192. Not all action IDs in this range are used by an action.

These IDs are divided into seven ranges, called action groups. These roughly categorize the behavior of each action, but are primarily used for organizational purposes in the code.

{| class="wikitable"
! Name !! Range start !! Range end !! Number of actions !! Description
|-
| stationary || 0x001 || 0x03F || 36 || stopped while on ground
|-
| moving || 0x040 || 0x07F || 40 || moving while on ground
|-
| airborne || 0x080 || 0x0BF || 45 || moving in air
|-
| submerged || 0x0C0 || 0x0FF || 32 || in water, including with metal cap
|-
| cutscene || 0x100 || 0x13F || 51 || no control of mario
|-
| automatic || 0x140 || 0x17F || 17 || restricted control of mario
|-
| object || 0x180 || 0x1BF || 10 || relating to picking up or releasing objects
|}

The "uninitialized" action with ID 0x000 is not considered to be a part of any group. Despite being a valid action, it overrides much of Mario's behavior and is implemented differently than regular actions.

Action groups, while largely used for organization, do sometimes define shared properties of the actions contained in them. For example, the code for dying in quicksand is shared among the stationary, moving, and object action groups, so it is impossible to die from quicksand while in one of the other action groups.

== Action flags ==

Most properties of actions are defined by action flags, which make up the remaining bits of the 32-bit action value. While there are 23 bits left after excluding the 9-bit ID, bit 30 is both unused by the game and unset by any action, so there are effectively only 22 action flags.

{| class="wikitable"
! Bit !! Name !! Example properties
|-
| 9 || stationary || increases deceleration in water
|-
| 10 || moving || affects buoyancy in water, push speed of horizontal wind
|-
| 11 || airborne || allows stomping on enemies, affects knockback behavior, disallows lava boost
|-
| 12 || intangible || disallows object interaction
|-
| 13 || swimming || affects knockback behavior
|-
| 14 || metal water || affects knockback behavior, lessens gravity and terminal velocity
|-
| 15 || short hitbox || shortens Mario's object hitbox from 160 to 100
|-
| 16 || riding shell || makes water surface a tangible floor, allows attacking objects
|-
| 17 || invulnerable || disables certain interactions involving damage or knockback
|-
| 18 || butt/stomach slide || Klepto checks this flag; details not yet known
|-
| 19 || diving || determines which picking-up action is used, affects water entry
|-
| 20 || on pole || cannot grab pole when previous action has this flag set
|-
| 21 || hanging || affects knockback behavior
|-
| 22 || idle || animation plays when collecting cap, allows reading signs
|-
| 23 || attacking || slightly affects whether an object can pick Mario up
|-
| 24 || interruptable by wind || allows entering the vertical wind action
|-
| 25 || control jump height || strengthens gravity when not holding A on ascent
|-
| 26 || allow first person || allows C-up to affect action behavior
|-
| 27 || pause exit || the level exit option is shown in the pause menu
|-
| 28 || swimming/flying || unused by the game
|-
| 29 || water/text || unused by the game
|-
| 31 || throwing || something to do with particle effects; details not yet known
|}

Note that the first three flags have the same name as the first three action groups. While most actions in these groups have the corresponding flag set, the converse is typically not true. Actions in the cutscene group, for example, may have the airborne flag set if they take place while Mario is in the air. There also exist unintuitive cases, such as action 0x036, air throw landing, which has the airborne flag set despite being a grounded stationary action, leading to strange behavior in some circumstances<ref>https://www.youtube.com/watch?v=c8iD58RQ1nw</ref>.

== References ==

Action

2018-07-25T05:24:54Z

Bad boot:

An '''action''' is a particular state that Mario can be in. [[Long jumping]], [[crouching]], and [[walking]] are examples of actions. Each action has code controlling high level behavior such as Mario's movement while in the action, as well as transitions to other actions.

It is likely the game developers referred to actions as "states", as evidenced by the "STA" label on one of the debug menus. The name "action" was chosen by the community as a less ambiguous alternative.

If Mario's current action is hacked to be an invalid action value, the game will freeze, since such an action lacks associated code. There are 230 valid actions in the game, but some of these are accessible only through hacking. In addition to these, there are two "pseudo-actions", 0x050 and 0x051, that immediately transition to another action. Specifically, they are "begin sliding" actions, and they transition into either butt slide or stomach slide, depending on whether Mario is facing uphill or downhill. There is evidence of one action, action 0x00E, that was defined but whose code was never implemented.

== Action groups ==

An action is represented as a 32-bit value. The lowest nine bits are a unique ID for the action, ranging in value from 0x000 to 0x192. Not all action IDs in this range are used by an action.

These IDs are divided into seven ranges, called action groups. These roughly categorize the behavior of each action, but are primarily used for organizational purposes in the code.

{| class="wikitable"
! Name !! Range start !! Range end !! Number of actions !! Description
|-
| stationary || 0x001 || 0x03F || 36 || stopped while on ground
|-
| moving || 0x040 || 0x07F || 40 || moving while on ground
|-
| airborne || 0x080 || 0x0BF || 45 || moving in air
|-
| submerged || 0x0C0 || 0x0FF || 32 || in water, including with metal cap
|-
| cutscene || 0x100 || 0x13F || 51 || no control of mario
|-
| automatic || 0x140 || 0x17F || 17 || restricted control of mario
|-
| object || 0x180 || 0x1BF || 10 || relating to picking up or releasing objects
|}

The "uninitialized" action with ID 0x000 is not considered to be a part of any group. Despite being a valid action, it overrides much of Mario's behavior and is implemented differently than regular actions.

Action groups, while largely used for organization, do sometimes define shared properties of the actions contained in them. For example, the code for dying in quicksand is shared among the stationary, moving, and object action groups, so it is impossible to die from quicksand while in one of the other action groups.

== Action flags ==

Most properties of actions are defined by action flags, which make up the remaining bits of the 32-bit action value. While there are 23 bits left after excluding the 9-bit ID, bit 30 is both unused by the game and unset by any action, so there are effectively only 22 action flags.

{| class="wikitable"
! Bit !! Name !! Example properties
|-
| 9 || stationary || increases deceleration in water
|-
| 10 || moving || affects buoyancy in water, push speed of horizontal wind
|-
| 11 || airborne || allows stomping on enemies, affects knockback behavior, disallows lava boost
|-
| 12 || intangible || disallows object interaction
|-
| 13 || swimming || affects knockback behavior
|-
| 14 || metal water || affects knockback behavior, lessens gravity and terminal velocity
|-
| 15 || short hitbox || shortens Mario's object hitbox from 160 to 100
|-
| 16 || riding shell || makes water surface a tangible floor, allows attacking objects
|-
| 17 || invulnerable || disables certain interactions involving damage or knockback
|-
| 18 || butt/stomach slide || Klepto checks this flag; details not yet known
|-
| 19 || diving || determines which picking-up action is used, affects water entry
|-
| 20 || on pole || cannot grab pole when previous action has this flag set
|-
| 21 || hanging || affects knockback behavior
|-
| 22 || idle || animation plays when collecting cap, allows reading signs
|-
| 23 || attacking || slightly affects whether an object can pick Mario up
|-
| 24 || interruptable by wind || allows entering the vertical wind action
|-
| 25 || control jump height || strengthens gravity when not holding A on ascent
|-
| 26 || allow first person || allows C-up to affect action behavior
|-
| 27 || pause exit || the level exit option is shown in the pause menu
|-
| 28 || swimming/flying || unused by the game
|-
| 29 || water/text || unused by the game
|-
| 31 || throwing || something to do with particle effects; details not yet known
|}

Note that the first three flags have the same name as the first three action groups. While most actions in these groups have the corresponding flag set, the converse is typically not true. Actions in the cutscene group, for example, may have the airborne flag set if they take place while Mario is in the air. There also exist unintuitive cases, such as action 0x036, air throw landing, which has the airborne flag set despite being a grounded stationary action, leading to strange behavior in some circumstances<ref>https://www.youtube.com/watch?v=c8iD58RQ1nw</ref>.

== References ==

Parallel Universe

2018-07-24T07:07:05Z

Bad boot:

[[File:ParallelUniverseViews.jpg|thumb|A diagram of Parallel Universe movement in [[Hazy Maze Cave]], after [[Mario]] has returned to the main map.]]

A '''Parallel Universe''', or '''PU''', is a region of space located far outside the intended map boundaries that reflects certain aspects, especially the floors and/or ceilings, of the main map. When the game looks for floors below (or ceilings above) a given object, it first "truncates" the object's position from a floating point value to a 16-bit integer value. While the range of a floating point value is infinite, the range of a 16-bit integer value is -215 = -32,768 to 215 - 1 = 32,767. If a coordinate of the object's position falls outside this range, it "wraps around". For example, if one of these floating point values is 40,000, then 40,000 - 65,536 = -25,536 will be used when determining if the object is aligned with a floor or ceiling. This gives the illusion that the floors and ceilings of the main level map are "copied" repeatedly in a uniform 3D grid, at a spacing of 65,536 units.

[[File:Visible PU.png|thumb|184x184px|Frame of [[Peter Fedak|Peter Fedak's]] video where he turns Parallel Universes visible using hacks; notice the lack of [[objects]]|left]]

The truncation responsible for the existence of parallel universes is only performed when determining alignment with floors and ceilings. This means that walls and objects, both of which use floating point arithmetic to determine collision, do not "exist" in PUs, unless they are brought there.

== Vertical parallel universes ==

Though usually the term "PU" refers to a horizontal PU (i.e. one caused by truncation of the ''x'' and/or ''z'' coordinates of an object's position), vertical PUs (where the ''y'' coordinate is truncated) also exist. However, these behave completely differently to horizontal PUs. While truncated coordinates are used to ''find'' the floor below the object and the ceiling above the object, the original floating point values are used to determine what ''effect'' these surfaces have on the object.

For example, when Mario is less than 160 units below the nearest ceiling, he is considered to be "above" the ceiling, his vertical speed is killed, and he bonks. If Mario moves to a positive (upward) vertical PU, the "nearest" ceiling will be determined based on truncated coordinates, and will therefore be in the main map. But when checking whether he is above this ceiling, floating point coordinates are used instead, and so Mario behaves as though he is stuck in a ceiling. This behavior results in positive vertical PUs appearing to be filled entirely with ceilings.

On the other hand, when Mario is below his "nearest" floor, he will snap up to it. This means that if Mario moves to a negative vertical PU, he will, in certain circumstances, upwarp back to the main map. This is called an '''overflow jump'''.

It is typically difficult to get to a vertical PU. In the positive direction, there is a ceiling at ''y'' = 20,000 that prevents upward movement. We can bypass this ceiling by pressing against OoB, for example by using [[Hyperspeed Flying|hyperspeed flying]]. We can also use [[Platform Displacement|platform displacement]] or [[Indefinite Owl Flight|indefinite owl flight]] to reach a positive vertical PU.

In the negative direction, we can use a [[Negative Jump|negative jump]] to jump downward with large amounts of negative speed, or platform displacement.

==Travel and movement==

[[File:Mario looking from a PU.png|thumb|251x251px|Mario looking to the original map from a PU]]

Parallel universes have found uses in both speed TASes and the [[A Button Challenge]] since they allow greater control of movement through a level. PU routing is comparable to movement through a five-dimensional space, as Mario can be modelled as travelling along five axes: three "relative" axes describing his position within the map, and two integers to specify which PU he is currently in. Mario can adjust his [[speed]] and [[angle]] to move relatively around the stage regardless of how many PUs he moves in the ''x'' or ''z'' dimensions.

Mario's movement is split up into four [[Movement Steps|quarter steps]], and if any of these quarter steps attempts to place Mario out of bounds, his movement is cancelled. Therefore in order to move to a PU, Mario's speed must be a multiple of four times the distance between PUs. If Mario takes all four quarter steps, then he will move four PUs in a single frame. This distance is called the '''Quadruple Parallel Universe''', or '''QPU''', distance.

If one of Mario's quarter steps (other than the first one) ends out of bounds, the game will cut his movement short. In this case, Mario does not travel the full QPU distance, and instead ends at whichever PU he made it to before his intended quarter step became out of bounds. This is referred to as a '''misaligned QPU'''.

As travelling to PUs involves moving very far from the origin, floating point imprecision can begin to have a significant affect on Mario's position, angle, and collision.

== Floating point truncation crash ==

While in theory the grid of PUs extends indefinitely, the behavior of the truncation operation becomes "undefined" when the floating point value is outside the range -231 to 231 - 1. The Nintendo 64 versions of the game crash when such a truncation is attempted. The Wii and Wii U virtual console versions of the game do not crash, though it is not currently known whether they wrap around the 32-bit integer range, or cap to the endpoints of the range. Nothing is currently known about iQue version's behavior in this case, since the usual RTA-viable methods of triggering this crash ([[BLJ]] and getting a bully stuck out of bounds) were patched in this version. Most emulators do not properly emulate the crash, except for a specific version of Mupen64, modded to crash correctly.

While movement to PUs at coordinates this large is rarely useful, this crash can occur due to other instances of truncation in the game, even in PUs close to the main map. For example, when determining Mario's tilt while walking, the game multiples Mario's speed by 16,384 and then truncates this value. This means that the game can crash in certain conditions when Mario has a speed of about 131,000, which is below QPU speed.

While not all conditions for these types of crashes are known, there are some that come up frequently. These are when:
* The camera enters a PU
* Mario bonks while in a PU
* Mario's quarter step gets cancelled while on the ground
* Mario collides with a wall head-on with PU speed

== Miscellaneous behavior ==

Certain objects and graphics behave interestingly while in parallel universes. For example:
* Shadows and coin twinkle effects are glitchy
* Spawning a 100 coin star will [[Softlock|softlock]] the game

Instant warp

2018-07-22T01:23:15Z

Bad boot:

An '''instant warp''' is a special [[floor]] that, when passed above, causes Mario to instantly move without interrupting normal gameplay. In the case of '''loading zones''', Mario enters a different area in the level and a different set of objects loads. In the case of the '''endless staircase''', Mario instantly changes position but not area.

Because normal gameplay is not interrupted when triggering an instant warp, interesting side effects can occur. For example, if Mario passes through a loading zone while holding an object or climbing on a pole, objects in the new area can be [[Cloning|cloned]].

When an instant warp displaces Mario, it moves the camera as well to maintain its position relative to Mario. If the camera is locked and Mario gets displaced a large distance, the camera can enter a PU, causing the Nintendo 64 versions of the game to crash. This is possible by repeatedly displacing Mario using the endless staircase<ref>https://www.youtube.com/watch?v=M9UPeSpZZPw</ref> or the TTM slide<ref>https://www.youtube.com/watch?v=Be_RbwFWh30</ref>.

If the warp displaces Mario out of bounds, then the [[OoB Failsafe|OoB failsafe]] mechanism triggers, effectively cancelling the displacement<ref>https://www.youtube.com/watch?v=gvQMNQlgu3s&feature=youtu.be&t=558</ref>.

==Locations==
*[[Castle]]: The endless staircase is an instant warp that is not a loading zone. It displaces Mario by -205 in the y direction and 410 in the z direction.
*[[Dire, Dire Docks]]: There is a two-way loading zone at the midpoint of the tunnel. It displaces Mario by 8192 in the x direction.
*[[Shifting Sand Land]]: There is a two-way loading zone inside the pyramid in the entrance to the [[Eyerok]] boss fight.
*[[Tall, Tall Mountain]]: There are two one-way loading zones along the slide. These displace Mario by (10240, 7168, 10240) and (-11264, 13312, 3072). They are located inside tunnels, which prevent Mario from activating them from above.
*[[Wet Dry World]]: There is a two-way loading zone in the tunnel leading to the town.

==References==

Instant warp

2018-07-22T00:21:40Z

Bad boot:

An '''instant warp''' is a special [[floor]] that, when passed above, causes Mario to instantly move without interrupting normal gameplay. In the case of '''loading zones''', Mario enters a different area in the level and a different set of objects loads. In the case of the '''endless staircase''', Mario instantly changes position but not area.

Because normal gameplay is not interrupted when triggering an instant warp, interesting side effects can occur. For example, if Mario passes through a loading zone while holding an object or climbing on a pole, objects in the new area can be [[Cloning|cloned]].

When an instant warp displaces Mario, it moves the camera as well to maintain its position relative to Mario. If the camera is locked and Mario gets displaced a large distance, the camera can enter a PU, causing the Nintendo 64 versions of the game to crash. This is possible by repeatedly displacing Mario using the endless staircase<ref>https://www.youtube.com/watch?v=M9UPeSpZZPw</ref> or the TTM slide<ref>https://www.youtube.com/watch?v=Be_RbwFWh30</ref>.

==Locations==
*[[Castle]]: The endless staircase is an instant warp that is not a loading zone. It displaces Mario by -205 in the y direction and 410 in the z direction.
*[[Dire, Dire Docks]]: There is a two-way loading zone at the midpoint of the tunnel. It displaces Mario by 8192 in the x direction.
*[[Shifting Sand Land]]: There is a two-way loading zone inside the pyramid in the entrance to the [[Eyerok]] boss fight.
*[[Tall, Tall Mountain]]: There are two one-way loading zones along the slide. These displace Mario by (10240, 7168, 10240) and (-11264, 13312, 3072). They are located inside tunnels, which prevent Mario from activating them from above.
*[[Wet Dry World]]: There is a two-way loading zone in the tunnel leading to the town.

==References==

Talk:Whomp's Fortress

2018-07-21T18:27:31Z

Bad boot: Created page with "Course version section is inaccurate; it doesn't depend entirely on which star is selected like the article implies. Someone should work out the correct conditions and update...."

Course version section is inaccurate; it doesn't depend entirely on which star is selected like the article implies. Someone should work out the correct conditions and update. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 18:27, 21 July 2018 (UTC)

Object slot

2018-07-15T06:47:16Z

Bad boot:

{{rewrite}}
{{stub}}

Super Mario 64 objects are stored in "object slots." There are 240 object slots that are either occupied or unoccupied. The objects that are occupied are stored first, and the objects that are unoccupied are stored second. If a player is able to hold an unoccupied object slot, a glitch known as [[Cloning]] occurs and the player is able to hold objects that usually cannot be held if an object loads into the slot. If all the object slots are filled up and one tries to load, the game will crash, unless the object is an [[Unimportant Object]] such as a dust particle.

Action

2018-07-12T19:00:24Z

Bad boot: /* Action groups */

An action is a particular state that Mario can be in. Long jumping, crouching, and walking are examples of actions. Each action has code controlling high level behavior such as Mario's movement while in the action, as well as transitions to other actions.

It is likely the game developers referred to actions as "states", as evidenced by the "STA" label on one of the debug menus. The name "action" was chosen by the community as a less ambiguous alternative.

If Mario's current action is hacked to be an invalid action value, the game will freeze, since such an action lacks associated code. There are 232 valid actions in the game, but some of these are accessible only through hacking. There is evidence of one action, action 0x00E, that was defined but whose code was never implemented.

== Action groups ==

An action is represented as a 32-bit value. The lowest nine bits are a unique ID for the action, ranging in value from 0x000 to 0x192. Not all action IDs in this range are used by an action.

These IDs are divided into seven ranges, called action groups. These roughly categorize the behavior of each action, but are primarily used for organizational purposes in the code.

{| class="wikitable"
! Name !! Range start !! Range end !! Number of actions !! Description
|-
| stationary || 0x001 || 0x03F || 36 || stopped while on ground
|-
| moving || 0x040 || 0x07F || 40 || moving while on ground
|-
| airborne || 0x080 || 0x0BF || 45 || moving in air
|-
| submerged || 0x0C0 || 0x0FF || 32 || in water, including with metal cap
|-
| cutscene || 0x100 || 0x13F || 51 || no control of mario
|-
| automatic || 0x140 || 0x17F || 17 || restricted control of mario
|-
| object || 0x180 || 0x1BF || 10 || relating to picking up or releasing objects
|}

The "uninitialized" action with ID 0x000 is not considered to be a part of any group. Despite being a valid action, it overrides much of Mario's behavior and is implemented differently than regular actions.

Action groups, while largely used for organization, do sometimes define shared properties of the actions contained in them. For example, the code for dying in quicksand is shared among the stationary, moving, and object action groups, so it is impossible to die from quicksand while in one of the other action groups.

== Action flags ==

Most properties of actions are defined by action flags, which make up the remaining bits of the 32-bit action value. While there are 23 bits left after excluding the 9-bit ID, bit 30 is both unused by the game and unset by any action, so there are effectively only 22 action flags.

{| class="wikitable"
! Bit !! Name !! Example properties
|-
| 9 || stationary || increases deceleration in water
|-
| 10 || moving || affects buoyancy in water, push speed of horizontal wind
|-
| 11 || airborne || allows stomping on enemies, affects knockback behavior, disallows lava boost
|-
| 12 || intangible || disallows object interaction
|-
| 13 || swimming || affects knockback behavior
|-
| 14 || metal water || affects knockback behavior, lessens gravity and terminal velocity
|-
| 15 || short hitbox || shortens Mario's object hitbox from 160 to 100
|-
| 16 || riding shell || makes water surface a tangible floor, allows attacking objects
|-
| 17 || invulnerable || disables certain interactions involving damage or knockback
|-
| 18 || butt/stomach slide || Klepto checks this flag; details not yet known
|-
| 19 || diving || determines which picking-up action is used, affects water entry
|-
| 20 || on pole || cannot grab pole when previous action has this flag set
|-
| 21 || hanging || affects knockback behavior
|-
| 22 || idle || animation plays when collecting cap, allows reading signs
|-
| 23 || attacking || slightly affects whether an object can pick Mario up
|-
| 24 || interruptable by wind || allows entering the vertical wind action
|-
| 25 || control jump height || strengthens gravity when not holding A on ascent
|-
| 26 || allow first person || allows C-up to affect action behavior
|-
| 27 || pause exit || the level exit option is shown in the pause menu
|-
| 28 || swimming/flying || unused by the game
|-
| 29 || water/text || unused by the game
|-
| 31 || throwing || something to do with particle effects; details not yet known
|}

Note that the first three flags have the same name as the first three action groups. While most actions in these groups have the corresponding flag set, the converse is typically not true. Actions in the cutscene group, for example, may have the airborne flag set if they take place while Mario is in the air. There also exist unintuitive cases, such as action 0x036, air throw landing, which has the airborne flag set despite being a grounded stationary action, leading to strange behavior in some circumstances<ref>https://www.youtube.com/watch?v=c8iD58RQ1nw</ref>.

== References ==

Action

2018-07-12T18:47:51Z

Bad boot: /* Action flags */

An action is a particular state that Mario can be in. Long jumping, crouching, and walking are examples of actions. Each action has code controlling high level behavior such as Mario's movement while in the action, as well as transitions to other actions.

It is likely the game developers referred to actions as "states", as evidenced by the "STA" label on one of the debug menus. The name "action" was chosen by the community as a less ambiguous alternative.

If Mario's current action is hacked to be an invalid action value, the game will freeze, since such an action lacks associated code. There are 232 valid actions in the game, but some of these are accessible only through hacking. There is evidence of one action, action 0x00E, that was defined but whose code was never implemented.

== Action groups ==

An action is represented as a 32-bit value. The lowest nine bits are a unique ID for the action, ranging in value from 0x000 to 0x192. Not all action IDs in this range are used by an action.

These IDs are divided into seven ranges, called action groups. These roughly categorize the behavior of each action, but are primarily used for organizational purposes in the code.

{| class="wikitable"
! Name !! Range start !! Range end !! Number of actions !! Description
|-
| stationary || 0x001 || 0x03F || 36 || stopped while on ground
|-
| moving || 0x040 || 0x07F || 40 || moving while on ground
|-
| airborne || 0x080 || 0x0BF || 45 || moving in air
|-
| submerged || 0x0C0 || 0x0FF || 32 || moving in water, including with metal cap
|-
| cutscene || 0x100 || 0x13F || 51 || no control of mario
|-
| automatic || 0x140 || 0x17F || 17 || restricted control of mario
|-
| object || 0x180 || 0x1BF || 10 || relating to picking up or releasing objects
|}

The "uninitialized" action with ID 0x000 is not considered to be a part of any group. Despite being a valid action, it overrides much of Mario's behavior and is implemented differently than regular actions.

Action groups, while largely used for organization, do sometimes define shared properties of the actions contained in them. For example, the code for dying in quicksand is shared among the stationary, moving, and object action groups, so it is impossible to die from quicksand while in one of the other action groups.

== Action flags ==

Most properties of actions are defined by action flags, which make up the remaining bits of the 32-bit action value. While there are 23 bits left after excluding the 9-bit ID, bit 30 is both unused by the game and unset by any action, so there are effectively only 22 action flags.

{| class="wikitable"
! Bit !! Name !! Example properties
|-
| 9 || stationary || increases deceleration in water
|-
| 10 || moving || affects buoyancy in water, push speed of horizontal wind
|-
| 11 || airborne || allows stomping on enemies, affects knockback behavior, disallows lava boost
|-
| 12 || intangible || disallows object interaction
|-
| 13 || swimming || affects knockback behavior
|-
| 14 || metal water || affects knockback behavior, lessens gravity and terminal velocity
|-
| 15 || short hitbox || shortens Mario's object hitbox from 160 to 100
|-
| 16 || riding shell || makes water surface a tangible floor, allows attacking objects
|-
| 17 || invulnerable || disables certain interactions involving damage or knockback
|-
| 18 || butt/stomach slide || Klepto checks this flag; details not yet known
|-
| 19 || diving || determines which picking-up action is used, affects water entry
|-
| 20 || on pole || cannot grab pole when previous action has this flag set
|-
| 21 || hanging || affects knockback behavior
|-
| 22 || idle || animation plays when collecting cap, allows reading signs
|-
| 23 || attacking || slightly affects whether an object can pick Mario up
|-
| 24 || interruptable by wind || allows entering the vertical wind action
|-
| 25 || control jump height || strengthens gravity when not holding A on ascent
|-
| 26 || allow first person || allows C-up to affect action behavior
|-
| 27 || pause exit || the level exit option is shown in the pause menu
|-
| 28 || swimming/flying || unused by the game
|-
| 29 || water/text || unused by the game
|-
| 31 || throwing || something to do with particle effects; details not yet known
|}

Note that the first three flags have the same name as the first three action groups. While most actions in these groups have the corresponding flag set, the converse is typically not true. Actions in the cutscene group, for example, may have the airborne flag set if they take place while Mario is in the air. There also exist unintuitive cases, such as action 0x036, air throw landing, which has the airborne flag set despite being a grounded stationary action, leading to strange behavior in some circumstances<ref>https://www.youtube.com/watch?v=c8iD58RQ1nw</ref>.

== References ==

Action

2018-07-12T18:29:52Z

Bad boot: Created page with " An action is a particular state that Mario can be in. Long jumping, crouching, and walking are examples of actions. Each action has code controlling high level behavior such..."

An action is a particular state that Mario can be in. Long jumping, crouching, and walking are examples of actions. Each action has code controlling high level behavior such as Mario's movement while in the action, as well as transitions to other actions.

It is likely the game developers referred to actions as "states", as evidenced by the "STA" label on one of the debug menus. The name "action" was chosen by the community as a less ambiguous alternative.

If Mario's current action is hacked to be an invalid action value, the game will freeze, since such an action lacks associated code. There are 232 valid actions in the game, but some of these are accessible only through hacking. There is evidence of one action, action 0x00E, that was defined but whose code was never implemented.

== Action groups ==

An action is represented as a 32-bit value. The lowest nine bits are a unique ID for the action, ranging in value from 0x000 to 0x192. Not all action IDs in this range are used by an action.

These IDs are divided into seven ranges, called action groups. These roughly categorize the behavior of each action, but are primarily used for organizational purposes in the code.

{| class="wikitable"
! Name !! Range start !! Range end !! Number of actions !! Description
|-
| stationary || 0x001 || 0x03F || 36 || stopped while on ground
|-
| moving || 0x040 || 0x07F || 40 || moving while on ground
|-
| airborne || 0x080 || 0x0BF || 45 || moving in air
|-
| submerged || 0x0C0 || 0x0FF || 32 || moving in water, including with metal cap
|-
| cutscene || 0x100 || 0x13F || 51 || no control of mario
|-
| automatic || 0x140 || 0x17F || 17 || restricted control of mario
|-
| object || 0x180 || 0x1BF || 10 || relating to picking up or releasing objects
|}

The "uninitialized" action with ID 0x000 is not considered to be a part of any group. Despite being a valid action, it overrides much of Mario's behavior and is implemented differently than regular actions.

Action groups, while largely used for organization, do sometimes define shared properties of the actions contained in them. For example, the code for dying in quicksand is shared among the stationary, moving, and object action groups, so it is impossible to die from quicksand while in one of the other action groups.

== Action flags ==

Most properties of actions are defined by action flags, which make up the remaining bits of the 32-bit action value. While there are 23 bits left after excluding the 9-bit ID, bit 30 is both unused by the game and unset by any action, so there are effectively only 22 action flags.

{| class="wikitable"
! Bit !! Name !! Example properties
|-
| 9 || stationary || increased deceleration in water
|-
| 10 || moving || affects buoyancy in water, push speed of horizontal wind
|-
| 11 || airborne || allows stomping on enemies, knockback behavior, disallows lava boost
|-
| 12 || intangible || disallows object interaction
|-
| 13 || swimming || affects knockback behavior
|-
| 14 || metal water || affects knockback behavior, lessens gravity and terminal velocity
|-
| 15 || short hitbox || shortens Mario's object hitbox from 160 to 100
|-
| 16 || riding shell || makes water surface a tangible floor, allows attacking objects
|-
| 17 || invulnerable || disables certain interactions involving damage or knockback
|-
| 18 || butt/stomach slide || Klepto checks this flag; details not yet known
|-
| 19 || diving || determines which picking-up action is used, affects water entry
|-
| 20 || on pole || cannot grab pole when previous action has this flag set
|-
| 21 || hanging || affects knockback behavior
|-
| 22 || idle || animation plays when collecting cap, allows reading signs
|-
| 23 || attacking || slightly affects whether an object can pick Mario up
|-
| 24 || interruptable by wind || allows entering the vertical wind action
|-
| 25 || control jump height || strengthens gravity when not holding A on ascent
|-
| 26 || allow first person || allows C-up to affect action behavior
|-
| 27 || pause exit || the level exit option is shown in the pause menu
|-
| 28 || swimming/flying || unused by the game
|-
| 29 || water/text || unused by the game
|-
| 31 || throwing || something to do with particle effects; details not yet known
|}

Note that the first three flags have the same name as the first three action groups. While most actions in these groups have the corresponding flag set, the converse is typically not true. Actions in the cutscene group, for example, may have the airborne flag set if they take place while Mario is in the air. There also exist unintuitive cases, such as action 0x036, air throw landing, which has the airborne flag set despite being a grounded stationary action, leading to strange behavior in some circumstances<ref>https://www.youtube.com/watch?v=c8iD58RQ1nw</ref>.

== References ==

User:Bad boot

2018-07-12T16:41:23Z

Bad boot:

Not to brag, but I've watched dozens of WR TASes

Action table testing:

{| class="wikitable"
|-
! ID !! Name !! Value !! Stationary !! Moving !! Air !! Intangible !! Swimming !! Metal !! Short !! Riding !! Invulnerable !! Slide !! Diving !! Pole !! Hanging !! Idle !! Attacking !! Wind !! Control !! First !! Pause !! Flying !! Water !! Throwing
|-
| 0x000 || uninitialized || 0x00000000
|-
| 0x001 || idle || 0x0C400201
|-
| 0x002 || start sleeping || 0x0C400202
|-
| 0x003 || sleeping || 0x0C000203
|-
| 0x004 || waking up || 0x0C000204
|-
| 0x005 || panting || 0x0C400205
|-
| 0x006 || unknown 006 || 0x08000206
|-
| 0x007 || unknown 007 || 0x08000207
|-
| 0x008 || unknown 008 || 0x08000208
|-
| 0x009 || standing against wall || 0x0C400209
|-
| 0x00A || coughing || 0x0C40020A
|-
| 0x00B || shivering || 0x0C40020B
|-
| 0x00D || in quicksand || 0x0002020D
|-
| 0x020 || crouching || 0x0C008220
|-
| 0x021 || start crouching || 0x0C008221
|-
| 0x022 || unknown 022 || 0x0C008222
|-
| 0x023 || start crawling || 0x0C008223
|-
| 0x024 || unknown 024 || 0x0C008224
|-
| 0x025 || slide kick slide stop || 0x08000225
|-
| 0x026 || unknown 026 || 0x00020226
|-
| 0x027 || first person || 0x0C000227
|-
| 0x02F || backflip land stop || 0x0800022F
|-
| 0x030 || jump land stop || 0x0C000230
|-
| 0x031 || double jump land stop || 0x0C000231
|-
| 0x032 || freefall land stop || 0x0C000232
|-
| 0x033 || side flip land stop || 0x0C000233
|-
| 0x034 || unknown 034 || 0x08000234
|-
| 0x035 || unknown 035 || 0x08000235
|-
| 0x036 || air throw land || 0x80000A36
|-
| 0x038 || twirl land || 0x18800238
|-
| 0x039 || lava boost land || 0x08000239
|-
| 0x03A || triple jump land stop || 0x0800023A
|-
| 0x03B || long jump land stop || 0x0800023B
|-
| 0x03C || ground pound land || 0x0080023C
|-
| 0x03D || braking stop || 0x0C00023D
|-
| 0x03E || butt slide stop || 0x0C00023E
|-
| 0x03F || unknown 03f || 0x0800043F
|-
| 0x040 || walking || 0x04000440
|-
| 0x042 || hold walking || 0x00000442
|-
| 0x043 || turning around || 0x00000443
|-
| 0x044 || finish turning around || 0x00000444
|-
| 0x045 || braking || 0x04000445
|-
| 0x046 || riding shell ground || 0x20810446
|-
| 0x047 || hold heavy walking || 0x00000447
|-
| 0x048 || crawling || 0x04008448
|-
| 0x049 || burning ground || 0x00020449
|-
| 0x04A || decelerating || 0x0400044A
|-
| 0x04B || hold decelerating || 0x0000044B
|-
| 0x050 || begin sliding || 0x00000050
|-
| 0x051 || hold begin sliding || 0x00000051
|-
| 0x052 || butt slide || 0x00840452
|-
| 0x053 || stomach slide || 0x008C0453
|-
| 0x054 || hold butt slide || 0x00840454
|-
| 0x055 || hold stomach slide || 0x008C0455
|-
| 0x056 || dive slide || 0x00880456
|-
| 0x057 || move punching || 0x00800457
|-
| 0x059 || crouch slide || 0x04808459
|-
| 0x05A || slide kick slide || 0x0080045A
|-
| 0x060 || hard backward ground kb || 0x00020460
|-
| 0x061 || hard forward ground kb || 0x00020461
|-
| 0x062 || backward ground kb || 0x00020462
|-
| 0x063 || forward ground kb || 0x00020463
|-
| 0x064 || soft backward ground kb || 0x00020464
|-
| 0x065 || soft forward ground kb || 0x00020465
|-
| 0x066 || ground bonk || 0x00020466
|-
| 0x067 || death exit land || 0x00020467
|-
| 0x070 || jump land || 0x04000470
|-
| 0x071 || freefall land || 0x04000471
|-
| 0x072 || double jump land || 0x04000472
|-
| 0x073 || side flip land || 0x04000473
|-
| 0x074 || hold jump land || 0x00000474
|-
| 0x075 || hold freefall land || 0x00000475
|-
| 0x076 || quicksand jump land || 0x00000476
|-
| 0x077 || hold quicksand jump land || 0x00000477
|-
| 0x078 || triple jump land || 0x04000478
|-
| 0x079 || long jump land || 0x00000479
|-
| 0x07A || backflip land || 0x0400047A
|-
| 0x080 || jump || 0x03000880
|-
| 0x081 || double jump || 0x03000881
|-
| 0x082 || triple jump || 0x01000882
|-
| 0x083 || backflip || 0x01000883
|-
| 0x085 || steep jump || 0x03000885
|-
| 0x086 || wall kick air || 0x03000886
|-
| 0x087 || side flip || 0x01000887
|-
| 0x088 || long jump || 0x03000888
|-
| 0x089 || water jump || 0x01000889
|-
| 0x08A || dive || 0x0188088A
|-
| 0x08C || freefall || 0x0100088C
|-
| 0x08D || top of pole jump || 0x0300088D
|-
| 0x08E || butt slide air || 0x0300088E
|-
| 0x094 || flying triple jump || 0x03000894
|-
| 0x098 || shot from cannon || 0x00880898
|-
| 0x099 || flying || 0x10880899
|-
| 0x09A || riding shell jump || 0x0281089A
|-
| 0x09B || riding shell fall || 0x0081089B
|-
| 0x09C || vertical wind || 0x1008089C
|-
| 0x0A0 || hold jump || 0x030008A0
|-
| 0x0A1 || hold freefall || 0x010008A1
|-
| 0x0A2 || hold butt slide air || 0x010008A2
|-
| 0x0A3 || hold water jump || 0x010008A3
|-
| 0x0A4 || twirling || 0x108008A4
|-
| 0x0A6 || forward rollout || 0x010008A6
|-
| 0x0A7 || air hit wall || 0x000008A7
|-
| 0x0A8 || riding hoot || 0x000004A8
|-
| 0x0A9 || ground pound || 0x008008A9
|-
| 0x0AA || slide kick || 0x018008AA
|-
| 0x0AB || air throw || 0x830008AB
|-
| 0x0AC || jump kick || 0x018008AC
|-
| 0x0AD || backward rollout || 0x010008AD
|-
| 0x0AE || crazy box bounce || 0x000008AE
|-
| 0x0AF || special triple jump || 0x030008AF
|-
| 0x0B0 || backward air kb || 0x010208B0
|-
| 0x0B1 || forward air kb || 0x010208B1
|-
| 0x0B2 || hard forward air kb || 0x010208B2
|-
| 0x0B3 || hard backward air kb || 0x010208B3
|-
| 0x0B4 || burning jump || 0x010208B4
|-
| 0x0B5 || burning fall || 0x010208B5
|-
| 0x0B6 || soft bonk || 0x010208B6
|-
| 0x0B7 || lava boost || 0x010208B7
|-
| 0x0B8 || getting blown || 0x010208B8
|-
| 0x0BD || thrown forward || 0x010208BD
|-
| 0x0BE || thrown backward || 0x010208BE
|-
| 0x0C0 || water idle || 0x380022C0
|-
| 0x0C1 || hold water idle || 0x380022C1
|-
| 0x0C2 || water action end || 0x300022C2
|-
| 0x0C3 || hold water action end || 0x300022C3
|-
| 0x0C4 || drowning || 0x300032C4
|-
| 0x0C5 || backward water kb || 0x300222C5
|-
| 0x0C6 || forward water kb || 0x300222C6
|-
| 0x0C7 || water death || 0x300032C7
|-
| 0x0C8 || water shocked || 0x300222C8
|-
| 0x0D0 || breaststroke || 0x300024D0
|-
| 0x0D1 || swimming end || 0x300024D1
|-
| 0x0D2 || flutter kick || 0x300024D2
|-
| 0x0D3 || hold breaststroke || 0x300024D3
|-
| 0x0D4 || hold swimming end || 0x300024D4
|-
| 0x0D5 || hold flutter kick || 0x300024D5
|-
| 0x0D6 || water shell swimming || 0x300024D6
|-
| 0x0E0 || water throw || 0x300024E0
|-
| 0x0E1 || water punch || 0x300024E1
|-
| 0x0E2 || water plunge || 0x300022E2
|-
| 0x0E3 || caught in whirlpool || 0x300222E3
|-
| 0x0F0 || metal water standing || 0x080042F0
|-
| 0x0F1 || hold metal water standing || 0x080042F1
|-
| 0x0F2 || metal water walking || 0x000044F2
|-
| 0x0F3 || hold metal water walking || 0x000044F3
|-
| 0x0F4 || metal water falling || 0x000042F4
|-
| 0x0F5 || hold metal water falling || 0x000042F5
|-
| 0x0F6 || metal water fall land || 0x000042F6
|-
| 0x0F7 || hold metal water fall land || 0x000042F7
|-
| 0x0F8 || metal water jump || 0x000044F8
|-
| 0x0F9 || hold metal water jump || 0x000044F9
|-
| 0x0FA || metal water jump land || 0x000044FA
|-
| 0x0FB || hold metal water jump land || 0x000044FB
|-
| 0x100 || disappeared || 0x00001300
|-
| 0x101 || intro cutscene || 0x04001301
|-
| 0x102 || star dance exit || 0x00001302
|-
| 0x103 || star dance water || 0x00001303
|-
| 0x104 || fall after star grab || 0x00001904
|-
| 0x105 || unknown 105 || 0x20001305
|-
| 0x106 || unknown 106 || 0x20001306
|-
| 0x107 || star dance no exit || 0x00001307
|-
| 0x108 || reading sign || 0x00001308
|-
| 0x109 || grabbed grand star || 0x00001909
|-
| 0x10A || unknown 10a || 0x0000130A
|-
| 0x10F || unknown 10f || 0x0000130F
|-
| 0x111 || standing death || 0x00021311
|-
| 0x112 || quicksand death || 0x00021312
|-
| 0x113 || electrocution || 0x00021313
|-
| 0x114 || suffocation || 0x00021314
|-
| 0x115 || death on stomach || 0x00021315
|-
| 0x116 || death on back || 0x00021316
|-
| 0x117 || eaten by bubba || 0x00021317
|-
| 0x118 || peach cutscene || 0x00001918
|-
| 0x119 || credits || 0x00001319
|-
| 0x11A || waving || 0x0000131A
|-
| 0x120 || pulling door || 0x00001320
|-
| 0x121 || pushing door || 0x00001321
|-
| 0x122 || unknown 122 || 0x00001322
|-
| 0x123 || emerge from pipe || 0x00001923
|-
| 0x124 || unknown 124 || 0x00001924
|-
| 0x125 || unknown 125 || 0x00001325
|-
| 0x126 || unknown 126 || 0x00001926
|-
| 0x127 || unknown 127 || 0x00001327
|-
| 0x128 || unknown 128 || 0x00001928
|-
| 0x129 || unknown 129 || 0x00001929
|-
| 0x12A || unknown 12a || 0x0000192A
|-
| 0x12B || unknown 12b || 0x0000192B
|-
| 0x12C || unknown 12c || 0x0000192C
|-
| 0x12D || unknown 12d || 0x0000192D
|-
| 0x12E || unlocking key door || 0x0000132E
|-
| 0x12F || unknown 12f || 0x0000132F
|-
| 0x131 || entering star door || 0x00001331
|-
| 0x132 || unknown 132 || 0x00001932
|-
| 0x133 || unknown 133 || 0x00001333
|-
| 0x134 || bbh enter jump || 0x00001934
|-
| 0x135 || bbh enter spin || 0x00001535
|-
| 0x136 || teleport fade out || 0x00001336
|-
| 0x137 || teleport fade in || 0x00001337
|-
| 0x138 || shocked || 0x00020338
|-
| 0x139 || squished || 0x00020339
|-
| 0x13A || head stuck in ground || 0x0002033A
|-
| 0x13B || butt stuck in ground || 0x0002033B
|-
| 0x13C || feet stuck in ground || 0x0002033C
|-
| 0x13D || putting on cap || 0x0000133D
|-
| 0x140 || holding pole || 0x08100340
|-
| 0x141 || grab pole slow || 0x00100341
|-
| 0x142 || grab pole fast || 0x00100342
|-
| 0x143 || climbing pole || 0x00100343
|-
| 0x144 || top of pole transition || 0x00100344
|-
| 0x145 || top of pole || 0x00100345
|-
| 0x148 || start hanging || 0x08200348
|-
| 0x149 || hanging || 0x00200349
|-
| 0x14A || hang moving || 0x0020054A
|-
| 0x14B || ledge grab || 0x0800034B
|-
| 0x14C || ledge climb slow 1 || 0x0000054C
|-
| 0x14D || ledge climb slow 2 || 0x0000054D
|-
| 0x14E || ledge climb down || 0x0000054E
|-
| 0x14F || ledge climb fast || 0x0000054F
|-
| 0x170 || grabbed || 0x00020370
|-
| 0x171 || in cannon || 0x00001371
|-
| 0x172 || tornado twirling || 0x10020372
|-
| 0x180 || punching || 0x00800380
|-
| 0x183 || unknown 183 || 0x00000383
|-
| 0x185 || unknown 185 || 0x00000385
|-
| 0x186 || unknown 186 || 0x00000386
|-
| 0x187 || unknown 187 || 0x00000387
|-
| 0x188 || throwing || 0x80000588
|-
| 0x189 || unknown 189 || 0x80000589
|-
| 0x190 || unknown 190 || 0x00000390
|-
| 0x191 || holding bowser || 0x00000391
|-
| 0x192 || releasing bowser || 0x00000392
|}

User:Bad boot

2018-07-12T16:37:21Z

Bad boot:

Not to brag, but I've watched dozens of WR TASes

Action table testing:

{| class="wikitable"
|-
! ID !! Name !! Value !! Stationary !! Moving !! Air !! Intangible !! Swimming !! Metal water !! Short hitbox !! Riding shell !! Invulnerable !! Butt/stomach slide !! Diving !! On pole !! Hanging !! Idle !! Attacking !! Allow vertical wind action !! Control jump height !! Allow first person !! Pause exit !! Swimming/flying !! Water/text !! Throwing
|-
| 0x000 || uninitialized || 0x00000000
|-
| 0x001 || idle || 0x0C400201
|-
| 0x002 || start sleeping || 0x0C400202
|-
| 0x003 || sleeping || 0x0C000203
|-
| 0x004 || waking up || 0x0C000204
|-
| 0x005 || panting || 0x0C400205
|-
| 0x006 || unknown 006 || 0x08000206
|-
| 0x007 || unknown 007 || 0x08000207
|-
| 0x008 || unknown 008 || 0x08000208
|-
| 0x009 || standing against wall || 0x0C400209
|-
| 0x00A || coughing || 0x0C40020A
|-
| 0x00B || shivering || 0x0C40020B
|-
| 0x00D || in quicksand || 0x0002020D
|-
| 0x020 || crouching || 0x0C008220
|-
| 0x021 || start crouching || 0x0C008221
|-
| 0x022 || unknown 022 || 0x0C008222
|-
| 0x023 || start crawling || 0x0C008223
|-
| 0x024 || unknown 024 || 0x0C008224
|-
| 0x025 || slide kick slide stop || 0x08000225
|-
| 0x026 || unknown 026 || 0x00020226
|-
| 0x027 || first person || 0x0C000227
|-
| 0x02F || backflip land stop || 0x0800022F
|-
| 0x030 || jump land stop || 0x0C000230
|-
| 0x031 || double jump land stop || 0x0C000231
|-
| 0x032 || freefall land stop || 0x0C000232
|-
| 0x033 || side flip land stop || 0x0C000233
|-
| 0x034 || unknown 034 || 0x08000234
|-
| 0x035 || unknown 035 || 0x08000235
|-
| 0x036 || air throw land || 0x80000A36
|-
| 0x038 || twirl land || 0x18800238
|-
| 0x039 || lava boost land || 0x08000239
|-
| 0x03A || triple jump land stop || 0x0800023A
|-
| 0x03B || long jump land stop || 0x0800023B
|-
| 0x03C || ground pound land || 0x0080023C
|-
| 0x03D || braking stop || 0x0C00023D
|-
| 0x03E || butt slide stop || 0x0C00023E
|-
| 0x03F || unknown 03f || 0x0800043F
|-
| 0x040 || walking || 0x04000440
|-
| 0x042 || hold walking || 0x00000442
|-
| 0x043 || turning around || 0x00000443
|-
| 0x044 || finish turning around || 0x00000444
|-
| 0x045 || braking || 0x04000445
|-
| 0x046 || riding shell ground || 0x20810446
|-
| 0x047 || hold heavy walking || 0x00000447
|-
| 0x048 || crawling || 0x04008448
|-
| 0x049 || burning ground || 0x00020449
|-
| 0x04A || decelerating || 0x0400044A
|-
| 0x04B || hold decelerating || 0x0000044B
|-
| 0x050 || begin sliding || 0x00000050
|-
| 0x051 || hold begin sliding || 0x00000051
|-
| 0x052 || butt slide || 0x00840452
|-
| 0x053 || stomach slide || 0x008C0453
|-
| 0x054 || hold butt slide || 0x00840454
|-
| 0x055 || hold stomach slide || 0x008C0455
|-
| 0x056 || dive slide || 0x00880456
|-
| 0x057 || move punching || 0x00800457
|-
| 0x059 || crouch slide || 0x04808459
|-
| 0x05A || slide kick slide || 0x0080045A
|-
| 0x060 || hard backward ground kb || 0x00020460
|-
| 0x061 || hard forward ground kb || 0x00020461
|-
| 0x062 || backward ground kb || 0x00020462
|-
| 0x063 || forward ground kb || 0x00020463
|-
| 0x064 || soft backward ground kb || 0x00020464
|-
| 0x065 || soft forward ground kb || 0x00020465
|-
| 0x066 || ground bonk || 0x00020466
|-
| 0x067 || death exit land || 0x00020467
|-
| 0x070 || jump land || 0x04000470
|-
| 0x071 || freefall land || 0x04000471
|-
| 0x072 || double jump land || 0x04000472
|-
| 0x073 || side flip land || 0x04000473
|-
| 0x074 || hold jump land || 0x00000474
|-
| 0x075 || hold freefall land || 0x00000475
|-
| 0x076 || quicksand jump land || 0x00000476
|-
| 0x077 || hold quicksand jump land || 0x00000477
|-
| 0x078 || triple jump land || 0x04000478
|-
| 0x079 || long jump land || 0x00000479
|-
| 0x07A || backflip land || 0x0400047A
|-
| 0x080 || jump || 0x03000880
|-
| 0x081 || double jump || 0x03000881
|-
| 0x082 || triple jump || 0x01000882
|-
| 0x083 || backflip || 0x01000883
|-
| 0x085 || steep jump || 0x03000885
|-
| 0x086 || wall kick air || 0x03000886
|-
| 0x087 || side flip || 0x01000887
|-
| 0x088 || long jump || 0x03000888
|-
| 0x089 || water jump || 0x01000889
|-
| 0x08A || dive || 0x0188088A
|-
| 0x08C || freefall || 0x0100088C
|-
| 0x08D || top of pole jump || 0x0300088D
|-
| 0x08E || butt slide air || 0x0300088E
|-
| 0x094 || flying triple jump || 0x03000894
|-
| 0x098 || shot from cannon || 0x00880898
|-
| 0x099 || flying || 0x10880899
|-
| 0x09A || riding shell jump || 0x0281089A
|-
| 0x09B || riding shell fall || 0x0081089B
|-
| 0x09C || vertical wind || 0x1008089C
|-
| 0x0A0 || hold jump || 0x030008A0
|-
| 0x0A1 || hold freefall || 0x010008A1
|-
| 0x0A2 || hold butt slide air || 0x010008A2
|-
| 0x0A3 || hold water jump || 0x010008A3
|-
| 0x0A4 || twirling || 0x108008A4
|-
| 0x0A6 || forward rollout || 0x010008A6
|-
| 0x0A7 || air hit wall || 0x000008A7
|-
| 0x0A8 || riding hoot || 0x000004A8
|-
| 0x0A9 || ground pound || 0x008008A9
|-
| 0x0AA || slide kick || 0x018008AA
|-
| 0x0AB || air throw || 0x830008AB
|-
| 0x0AC || jump kick || 0x018008AC
|-
| 0x0AD || backward rollout || 0x010008AD
|-
| 0x0AE || crazy box bounce || 0x000008AE
|-
| 0x0AF || special triple jump || 0x030008AF
|-
| 0x0B0 || backward air kb || 0x010208B0
|-
| 0x0B1 || forward air kb || 0x010208B1
|-
| 0x0B2 || hard forward air kb || 0x010208B2
|-
| 0x0B3 || hard backward air kb || 0x010208B3
|-
| 0x0B4 || burning jump || 0x010208B4
|-
| 0x0B5 || burning fall || 0x010208B5
|-
| 0x0B6 || soft bonk || 0x010208B6
|-
| 0x0B7 || lava boost || 0x010208B7
|-
| 0x0B8 || getting blown || 0x010208B8
|-
| 0x0BD || thrown forward || 0x010208BD
|-
| 0x0BE || thrown backward || 0x010208BE
|-
| 0x0C0 || water idle || 0x380022C0
|-
| 0x0C1 || hold water idle || 0x380022C1
|-
| 0x0C2 || water action end || 0x300022C2
|-
| 0x0C3 || hold water action end || 0x300022C3
|-
| 0x0C4 || drowning || 0x300032C4
|-
| 0x0C5 || backward water kb || 0x300222C5
|-
| 0x0C6 || forward water kb || 0x300222C6
|-
| 0x0C7 || water death || 0x300032C7
|-
| 0x0C8 || water shocked || 0x300222C8
|-
| 0x0D0 || breaststroke || 0x300024D0
|-
| 0x0D1 || swimming end || 0x300024D1
|-
| 0x0D2 || flutter kick || 0x300024D2
|-
| 0x0D3 || hold breaststroke || 0x300024D3
|-
| 0x0D4 || hold swimming end || 0x300024D4
|-
| 0x0D5 || hold flutter kick || 0x300024D5
|-
| 0x0D6 || water shell swimming || 0x300024D6
|-
| 0x0E0 || water throw || 0x300024E0
|-
| 0x0E1 || water punch || 0x300024E1
|-
| 0x0E2 || water plunge || 0x300022E2
|-
| 0x0E3 || caught in whirlpool || 0x300222E3
|-
| 0x0F0 || metal water standing || 0x080042F0
|-
| 0x0F1 || hold metal water standing || 0x080042F1
|-
| 0x0F2 || metal water walking || 0x000044F2
|-
| 0x0F3 || hold metal water walking || 0x000044F3
|-
| 0x0F4 || metal water falling || 0x000042F4
|-
| 0x0F5 || hold metal water falling || 0x000042F5
|-
| 0x0F6 || metal water fall land || 0x000042F6
|-
| 0x0F7 || hold metal water fall land || 0x000042F7
|-
| 0x0F8 || metal water jump || 0x000044F8
|-
| 0x0F9 || hold metal water jump || 0x000044F9
|-
| 0x0FA || metal water jump land || 0x000044FA
|-
| 0x0FB || hold metal water jump land || 0x000044FB
|-
| 0x100 || disappeared || 0x00001300
|-
| 0x101 || intro cutscene || 0x04001301
|-
| 0x102 || star dance exit || 0x00001302
|-
| 0x103 || star dance water || 0x00001303
|-
| 0x104 || fall after star grab || 0x00001904
|-
| 0x105 || unknown 105 || 0x20001305
|-
| 0x106 || unknown 106 || 0x20001306
|-
| 0x107 || star dance no exit || 0x00001307
|-
| 0x108 || reading sign || 0x00001308
|-
| 0x109 || grabbed grand star || 0x00001909
|-
| 0x10A || unknown 10a || 0x0000130A
|-
| 0x10F || unknown 10f || 0x0000130F
|-
| 0x111 || standing death || 0x00021311
|-
| 0x112 || quicksand death || 0x00021312
|-
| 0x113 || electrocution || 0x00021313
|-
| 0x114 || suffocation || 0x00021314
|-
| 0x115 || death on stomach || 0x00021315
|-
| 0x116 || death on back || 0x00021316
|-
| 0x117 || eaten by bubba || 0x00021317
|-
| 0x118 || peach cutscene || 0x00001918
|-
| 0x119 || credits || 0x00001319
|-
| 0x11A || waving || 0x0000131A
|-
| 0x120 || pulling door || 0x00001320
|-
| 0x121 || pushing door || 0x00001321
|-
| 0x122 || unknown 122 || 0x00001322
|-
| 0x123 || emerge from pipe || 0x00001923
|-
| 0x124 || unknown 124 || 0x00001924
|-
| 0x125 || unknown 125 || 0x00001325
|-
| 0x126 || unknown 126 || 0x00001926
|-
| 0x127 || unknown 127 || 0x00001327
|-
| 0x128 || unknown 128 || 0x00001928
|-
| 0x129 || unknown 129 || 0x00001929
|-
| 0x12A || unknown 12a || 0x0000192A
|-
| 0x12B || unknown 12b || 0x0000192B
|-
| 0x12C || unknown 12c || 0x0000192C
|-
| 0x12D || unknown 12d || 0x0000192D
|-
| 0x12E || unlocking key door || 0x0000132E
|-
| 0x12F || unknown 12f || 0x0000132F
|-
| 0x131 || entering star door || 0x00001331
|-
| 0x132 || unknown 132 || 0x00001932
|-
| 0x133 || unknown 133 || 0x00001333
|-
| 0x134 || bbh enter jump || 0x00001934
|-
| 0x135 || bbh enter spin || 0x00001535
|-
| 0x136 || teleport fade out || 0x00001336
|-
| 0x137 || teleport fade in || 0x00001337
|-
| 0x138 || shocked || 0x00020338
|-
| 0x139 || squished || 0x00020339
|-
| 0x13A || head stuck in ground || 0x0002033A
|-
| 0x13B || butt stuck in ground || 0x0002033B
|-
| 0x13C || feet stuck in ground || 0x0002033C
|-
| 0x13D || putting on cap || 0x0000133D
|-
| 0x140 || holding pole || 0x08100340
|-
| 0x141 || grab pole slow || 0x00100341
|-
| 0x142 || grab pole fast || 0x00100342
|-
| 0x143 || climbing pole || 0x00100343
|-
| 0x144 || top of pole transition || 0x00100344
|-
| 0x145 || top of pole || 0x00100345
|-
| 0x148 || start hanging || 0x08200348
|-
| 0x149 || hanging || 0x00200349
|-
| 0x14A || hang moving || 0x0020054A
|-
| 0x14B || ledge grab || 0x0800034B
|-
| 0x14C || ledge climb slow 1 || 0x0000054C
|-
| 0x14D || ledge climb slow 2 || 0x0000054D
|-
| 0x14E || ledge climb down || 0x0000054E
|-
| 0x14F || ledge climb fast || 0x0000054F
|-
| 0x170 || grabbed || 0x00020370
|-
| 0x171 || in cannon || 0x00001371
|-
| 0x172 || tornado twirling || 0x10020372
|-
| 0x180 || punching || 0x00800380
|-
| 0x183 || unknown 183 || 0x00000383
|-
| 0x185 || unknown 185 || 0x00000385
|-
| 0x186 || unknown 186 || 0x00000386
|-
| 0x187 || unknown 187 || 0x00000387
|-
| 0x188 || throwing || 0x80000588
|-
| 0x189 || unknown 189 || 0x80000589
|-
| 0x190 || unknown 190 || 0x00000390
|-
| 0x191 || holding bowser || 0x00000391
|-
| 0x192 || releasing bowser || 0x00000392
|}

Talk:Hurtbox

2018-07-12T15:06:32Z

Bad boot: Created page with "This doesn't exist. The game doesn't differentiate between regular hitboxes and "hurtboxes". Some objects do damage, and others don't. ~~~~"

This doesn't exist. The game doesn't differentiate between regular hitboxes and "hurtboxes". Some objects do damage, and others don't. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 15:06, 12 July 2018 (UTC)

Backflip

2018-07-12T05:08:15Z

Bad boot: Backflips give 62 VS, not 58.

{{stub}}

Backflips, also known as Backward Somersaults, are a jump Mario can do that causes him to move upwards and backward. You can perform a backflip by pressing and holding Z and pressing A. Holding forwards during the backflip can cause Mario to have a net forwards movement. The [[Vertical Speed]] (VS) value that a backflip starts with is 62. With all of the vertical speed combined, you can get 512 units up from where you started the backflip.

== C^ Backflip ==
The [[C^ Backflip]] trick allows you to backflip facing any direction without having to turn first, saving a few frames in some TASes.

Quarter Steps

2018-06-19T22:32:12Z

Bad boot: Redirected page to Movement Steps

#redirect [[Movement Steps]]

Quarter Frames

2018-06-19T22:31:46Z

Bad boot: Redirected page to Movement Steps

#redirect [[Movement Steps]]

Talk:C^ backflip

2018-06-19T22:25:03Z

Bad boot: Created page with "I think our policy regarding attributing glitches to specific people should be to only do it when the history is interesting or relevant to the glitch itself. For example, som..."

I think our policy regarding attributing glitches to specific people should be to only do it when the history is interesting or relevant to the glitch itself. For example, someone who visits the Pedro spot page will want to know where the name comes from, so we should give a very brief explanation. Here, it's not important or interesting that Plush discovered the glitch, so I don't think we should attribute it. Thoughts? [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 22:24, 19 June 2018 (UTC)

Movement steps

2018-06-19T22:17:40Z

Bad boot: Created page with "Typically, Mario's position is updated incrementally using his velocity. These increments are called '''steps''', and they behave differently when Mario is on the ground, in t..."

Typically, Mario's position is updated incrementally using his velocity. These increments are called '''steps''', and they behave differently when Mario is on the ground, in the air, in water, hanging, and climbing a pole. When on the ground or in the air, these steps typically occur four times per frame, and are commonly referred to as '''quarter steps''' or sometimes '''quarter frames'''.

Steps are also responsible for detecting collision with [[surfaces]], updating Mario's [[referenced surfaces]], and updating Mario's [[Water|water level]].

Talk:Object slot

2018-06-19T22:07:27Z

Bad boot:

This info already exists in (slightly) more detail at [[Memory]]. However "Memory" is a dumb name, so the content should be moved from there to here. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 22:07, 19 June 2018 (UTC)
: After taking another look at the Memory article, it contained a lot of false or misleading info, so I just deleted it. [[User:Bad boot|Bad boot]] ([[User talk:Bad boot|talk]]) 22:07, 19 June 2018 (UTC)