Editing Glitches in Pikmin 2
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 328: | Line 328: | ||
===Cave entrance leader mixup=== | ===Cave entrance leader mixup=== | ||
{{ | {{main|Cave#Cave entrance leader mixup}} | ||
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. | |||
===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. | ||
}} | }} |