771
edits
Pause Buffering: Difference between revisions
Jump to navigation
Jump to search
Subsections, info on PBH and global timer
m (MMMMMMMMMMMMM moved page Pause Buffer to Pause Buffering: The name "Pause Buffering" is by far the most widely used. We say "by pause buffering", not "we pause buffer" much more often.) |
(Subsections, info on PBH and global timer) |
||
| Line 2: | Line 2: | ||
==Applications== | ==Applications== | ||
Pause buffering can be used to press inputs on two or more in-game-contiguous frames. There are three parts to a button input—[[Button press|pressing]], [[Button hold|holding]], and [[Button release|releasing]]. If the game detects that the button is being inputted on two frames in a row, it will detect that the button is being held, even if there were two separate presses. Furthermore, holding a button often does nothing. | Pause buffering can be used to press inputs on two or more in-game-contiguous frames. There are three parts to a button input—[[Button press|pressing]], [[Button hold|holding]], and [[Button release|releasing]]. If the game detects that the button is being inputted on two frames in a row, it will detect that the button is being held, even if there were two separate presses. Furthermore, holding a button often does nothing, such as walking while holding the Z button and any holding of the B button. | ||
===Pause Buffering Inputs=== | |||
In situations where it would be advantageous to press the same button for two frames in a row, those two in-game frames can be separated by opening the pause menu. This provides time for the game to recognize the release of the button, and be able to detect another press once the game is unpaused. In short, pausing allows an input to be released and pressed again without changing any in-game states. For example, a dive can be followed immediately by a dive recover, which is useful while holding an object [[handsfree]] in the [[A Button Challenge]]. | In situations where it would be advantageous to press the same button for two frames in a row, those two in-game frames can be separated by opening the pause menu. This provides time for the game to recognize the release of the button, and be able to detect another press once the game is unpaused. In short, pausing allows an input to be released and pressed again without changing any in-game states. For example, a [[dive]] can be followed immediately by a [[dive recover]], which is useful while holding an object [[handsfree]] in the [[A Button Challenge]] (ABC). Notably, pause buffering is not necessary to perform this in a non-ABC setting, since B can be pressed to dive followed by A to recover. | ||
===Pause Buffering the Global Timer=== | |||
The [[global timer]] is a variable that increments every frame, even paused frames. Thus, [[objects]] that depend on the global timer can be manipulated by strategically pausing. Although many objects use the global timer, the ones that are most commonly manipulated are [[Swooper]]s and the [[Lethal Lava Land]] [[drawbridge]]. Many objects use their own [[timer]] instead of the global timer, and since objects do not update while paused, cannot be affected by pause buffering. | |||
====Pause Buffered Hitstun==== | |||
The most common use of pause buffering the global timer is Pause Buffered Hitstun, which lends itself to [[HOLP]] preservation and thus releasing objects remotely. The player can avoid updating the HOLP by taking advantage of [[Mario]]'s blinking effect after [[hitstun]], an effect that continues if Mario is inside an enemy [[Hitbox#hurtbox|hurtbox]]. After being hurt in any way but small [[fall damage]], Mario, along with a held [[ticket]], will become transparent on every second frame. His opacity depends on the parity of the [[global timer]], so he is not rendered on odd frames. Since the global timer is incremented on every frame, including paused frames, by pausing for the minimum three frames and unpausing for the minimum one frame when the timer is odd, Mario and the ticket will effectively not render until the blinking effect stops. Because the ticket does not need to render, the HOLP is not updated during that time. | |||