Editing Glitches in Pikmin 2

Jump to navigation Jump to search
You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 67: Line 67:


===Sped up punching===
===Sped up punching===
{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | p2s = Yes |
{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | p2ns = Yes |
| effects = Makes a leader [[punch]] twice as fast.
| effects = Makes a leader [[punch]] twice as fast.
| howto = Simply punch while moving. Rotating in place also works. You should attack roughly twice as fast as if you were standing still.
| howto = Simply punch while moving. Rotating in place also works. You should attack roughly twice as fast as if you were standing still.
Line 328: Line 328:


===Cave entrance leader mixup===
===Cave entrance leader mixup===
{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes | demonstration = [https://youtu.be/DtPkOwWds60&t=237 Youtube video at 3:57]
{{main|Cave#Cave entrance leader mixup}}
| effects = When entering the first sublevel of a cave in ''Pikmin 2'', the game may or may not switch the player's active leader.  
When entering the first sublevel of a cave, the game may or may not switch the player's active leader. It depends on the last leader the player used to jump to a non-first sublevel.
| prerequisites = None
| howto = Enter the last sublevel in a cave, and then enter the first sublevel of a different cave with a different leader.
| notes = This does not happen when the player goes from one sublevel to the next. [[Challenge Mode (Pikmin 2)|Challenge Mode]] uses a different behavior, without a glitch, and that the default value of the variable is 0, meaning that at the start of the game, before the player goes from one sublevel to the next, the game will make Olimar the active leader when entering a cave.
| explanation = In order to decide what leader to turn active whenever a sublevel is entered (be it the first or not), the game reads a variable in memory. This variable is also saved onto the [[Saved game|save game data]] and loaded from it. It is set whenever the player goes from one sublevel to the next, which explains why, when the next sublevel is loaded, the game selects the correct leader. However, this variable never gets set when the cave itself is entered. This means that when the first sublevel is finished loading, the game reads the variable, and uses an outdated value, last updated when a sublevel hole was entered.
}}


===Cave hole glitch===
===Cave hole glitch===
Line 500: Line 495:
| prerequisites = Have the [[Napsack]].
| prerequisites = Have the [[Napsack]].
| howto = When {{button|gc|x|wii|c}} is held, the leader makes a small bounce before lying down. If this bounce happens just as a boulder lands on the leader, there's a chance he might jump quite high in the air. The easiest way to pull it off is to enter the [[Cave of Pain]]. You should hold the button one and a half seconds after the shadow of the boulder appears. If you get hurt, that means you have to press it sooner. If you just [[lie down]], that means you pressed it too soon. For reference, check the timings on the notes.
| howto = When {{button|gc|x|wii|c}} is held, the leader makes a small bounce before lying down. If this bounce happens just as a boulder lands on the leader, there's a chance he might jump quite high in the air. The easiest way to pull it off is to enter the [[Cave of Pain]]. You should hold the button one and a half seconds after the shadow of the boulder appears. If you get hurt, that means you have to press it sooner. If you just [[lie down]], that means you pressed it too soon. For reference, check the timings on the notes.
| notes = This trick can be used to jump over some obstacles. The further away from the center of the boulder, the farther the distance of the jump. The closer to the center of the timing window you start lying down, the higher the jump. Via testing, it's concluded that the button must be pressed between the {{frames|41}}st [[frame]] after the shadow appears ({{frames|40}} frames of the shadow's existence) and the {{frames|46}}th ({{frames|45}} frames of the shadow's existence). This results in a window of {{frames|6}} frames. If you make the leader wake up, he will lose all of his momentum and fall to the ground, without you being able to control his descent.
| notes = This trick can be used to jump over some obstacles. The further away from the center of the boulder, the farther the distance of the jump. The closer to the center of the timing window you start lying down, the higher the jump. Via testing, it's concluded that the button must be pressed between the {{frames|41}}st [[frame]] after the the shadow appears ({{frames|40}} frames of the shadow's existence) and the {{frames|46}}th ({{frames|45}} frames of the shadow's existence). This results in a window of {{frames|6}} frames. If you make the leader wake up, he will lose all of his momentum and fall to the ground, without you being able to control his descent.
| explanation = The small bounce a leader makes must be programmed as an actual, physics-abiding jump, instead of a simple animation. This would explain why when something that's meant to cause knockback interferes with a jump makes a glitchy jump happen, as the game wasn't ready to handle that particular scenario. Alternately, it has to do with how the leader should've been knocked back, but the Napsack partially stops that, and blocks all damage, again, causing confusion in the physics engine.
| explanation = The small bounce a leader makes must be programmed as an actual, physics-abiding jump, instead of a simple animation. This would explain why when something that's meant to cause knockback interferes with a jump makes a glitchy jump happen, as the game wasn't ready to handle that particular scenario. Alternately, it has to do with how the leader should've been knocked back, but the Napsack partially stops that, and blocks all damage, again, causing confusion in the physics engine.
}}
}}

Please note that all contributions to Pikipedia are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see Pikipedia:Copyrights for details). Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)