Editing Glitches in Pikmin 2

{{spoiler}}

{{game help|p2|Analyze and document [[Talk:Glitches in Pikmin 2#Glitches to analyze|these]].}}

{{TOC right}}

This is a collection of '''[[glitch]]es''' possible in {{p2}}, as well as in {{npcp2}} and {{p2s}}.

===Crushing glitch===

{{glitch | reproducibility = Low | consequences = Harmful | p2 = Yes | npcp2 = Yes | youtube = RXlmnr_IpBA | vcaption = Demonstration of the glitch, at 3:20. | other = Crushing glitch with the Science Project: [https://www.youtube.com/watch?v=6oJGPO8yN4w 1], [https://www.youtube.com/watch?v=g0Gzf1XbeM8 2]

| effects = Makes a Pikmin vanish instantly by being crushed.

| howto = When an enemy is defeated and falls to the ground, there is a chance that a nearby Pikmin will mysteriously vanish without leaving a [[soul]] or making a sound. There are several enemies that have this happen more frequently than others, and it also happens with more regularity when [[swarm]]ing enemies rather than [[throw]]ing Pikmin at them. It can also happen with [[pellet]]s and [[treasure]]s.

| notes = [[Glitches in Pikmin#Crushing glitch|This glitch can also happen in ''Pikmin'']].

| explanation = When falling down, enemies will push any nearby Pikmin downwards and to the side. If the collision is just right, there's a chance that the downward push is too strong and the Pikmin falls to the ground, where it instantly dies shortly after.

===Drowning reset===

{{glitch | reproducibility = Low | consequences = Helpful | p2 = Yes | npcp2 = Yes

| notes = A [[Glitches in Pikmin#Drowning reset|similar glitch]] can also be done in ''Pikmin'', but the method is different.

{{main|Throw#High ledge glitch}}

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | demonstration = [http://speeddemosarchive.com/demo.pl?Pikmin2_BestEnding_310 13:10 of part 3 of the current Speed Demos Archive speedrun, by Charles Griffin]

| effects = Makes a bridge's 2^nd+ sections be constructed instantly.

| prerequisites = You should not have visited this area before.

| howto = Simply enter a cave and get out, or end the day and come back to the area on a later day. When you then issue Pikmin to work on the bridge, the current stage the bridge is in will be worked on as normal, but all other stages will be built instantly.

| explanation = When the area is exited, the game [[Saved game|saves]] some information about it, including the current stage of each bridge. When the area is entered again, it loads the saved data, and changes the bridge to match the saved stage. However, it gives that stage's health a value of 3000 and all other stages are left with 0 health. Even at 0 health, the game only updates the stage of the bridge once Pikmin attack it during that stage.

===Napsack warp===

{{glitch | reproducibility = High | consequences = Depends | p2 = Yes | npcp2 = Yes

| effects = Makes a leader warp to the nearest carrying path waypoint.

| prerequisites = Have the [[Upgrade#Napsack|Napsack]], and have a way to fall underneath the map such as by going [[out of bounds]] with a [[Glitches in Pikmin 2#Seesaw block clip|seesaw block clip]].

| howto = Fall underneath the map and [[lie down]] while falling. If done correctly, this will warp you to the nearest carrying path waypoint.

| normal = When falling out of bounds, the intended behavior is that you will be warped to the default failsafe location, which is always near the ship. This will also happen if the leader touches the pit without lying down.

| explanation = When a leader has used the Napsack, they are treated as if they are a treasure for certain interactions. There's another invisible plane underneath every level that warps treasures back in-bounds in case they fall into the void, and triggering this interaction on a leader is what causes this glitch.

| notes = There's an invisible plane underneath every level that kills any enemies or Pikmin that fall into the [[pit]]. Due to the erratic nature of how a leader falls when lying down, it is possible that the leader will touch this plane instead of just the plane that relocates treasures. If this happens, the leader will become [[#Frozen leader glitch|frozen]]. This happens deterministically depending on the fall speed and exact position of your leader when the respective planes are touched, but given the precision involved it's generally regarded as impossible to avoid this happening with 100% consistency. Roughly 20% of the time this will occur when performing Napsack Warps regardless of location.

===Seesaw block clip===

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | demonstration = [http://speeddemosarchive.com/demo.pl?Pikmin2_BestEnding_310 2:20 and 5:25 of part 7 of the current Speed Demos Archive speedrun, by Charles Griffin]

| effects = Allows a leader to clip inside a [[seesaw block]], after which they can go [[out of bounds]].

| prerequisites = Have an available [[cutscene]] that can be triggered, for example a treasure collection cutscene or a Pikmin hazard introduction cutscene.

| howto = Place a leader on a lowered seesaw block. Then throw some Pikmin onto the other block and trigger a cutscene while the blocks are still moving. After the cutscene is over, the leader that was standing on the block will be inside of it. You can also clip into the seesaw blocks in [[Perplexing Pool]] near [[Glutton's Kitchen]] without the use of a cutscene by [[lying down]] on top of the southern block of the pair, while against its southern edge, while it is raised.{{cite youtube|NYcSyL-DpP0|of a player clipping through the seesaw block by lying down on its edge|h=1|m=49|s=40}} This is the only known location where you can clip inside a seesaw block this way.

| notes = You must let the cutscene play out for about one second – if you skip the cutscene immediately, the clip won't work. This glitch can be used to get out of bounds in nearly every location where a seesaw block is present. When used in combination with a [[Glitches in Pikmin 2#Napsack warp|Napsack warp]] you can reach unintended locations such as the Blue Onion area before breaking the electric gate blocking it.

| explanation = During most cutscenes, leaders and non-treasure-related Pikmin are frozen in place so disasters can't happen while the player is unable to take action. Some objects continue to move though, such as the seesaw blocks. Because the leader's position doesn't move while the block does, it engulfs the leader and places them inside it after the cutscene is finished.

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | p2s = Yes |

| effects = Makes a leader [[punch]] twice as fast.

===Spray duplication===

 

==Pikmin-related==

===Cave death count glitch===

{{glitch | reproducibility = Medium | consequences = Harmful | p2 = Yes | npcp2 = Yes | youtube = 7mu5dfuqa4k

| effects = Increases the number of Pikmin deaths without killing the corresponding Pikmin.

| prerequisites = Be in a cave that has [[water]], [[poison]] or [[fire]] hazards, and have Pikmin that are not immune to those hazards.

| howto = When your Pikmin are drowning, choking or burning due to a water, poison or fire hazard, their deaths are accounted for exactly when they make their last scream. While they are too far gone to save by the [[whistle]] at this point, they aren't exactly dead yet. If you go into a [[geyser]] or hole, you can see them jump into it with the bubbles, gas, or flames on them, albeit alive. On the next sublevel, they'll be perfectly normal. However, when you complete the cave, you'll notice that their deaths were accounted for in the number of total deaths. If you do it several times throughout the sublevels, you can even have over 100 deaths in a single cave run.

| notes = This glitched number of deaths in the cave will also add to your Pikmin death [[Saved game|save file]] total. It's also possible for a Pikmin to catch on fire during the cutscene, if there's a geyser nearby. But this will neither kill the Pikmin or change the death count. This can also rarely happen if Pikmin die from falling off an abyss.{{cite youtube|e3QmXfhKPUs|showing Pikmin falling into the pit whilst on the sublevel jump cutscene}}

| explanation = The game counts a death when a Pikmin makes its last cry, even though the creature's object still exists on the map. Normally, it's impossible to save it when it's doing its last cry, though. But when entering a hole or a geyser, the game forces all Pikmin objects to jump in, regardless of their state. When loading the next sublevel, the game creates new Pikmin objects, basing itself on the previous objects' maturity, color, etc., but not their state (choking/burning).

===Crushed Pikmin in cutscene===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | image = Crushed Pikmin jumping in hole.jpg | icaption = Demonstration of the glitch. The Pikmin on the bottom-left are very flat.

| effects = Causes [[crush]]ed Pikmin to appear in the sublevel transition cutscene.

| prerequisites = Have something that is able to crush Pikmin on the sublevel, such as the [[Armored Cannon Larva]] in sublevel 3 of [[Subterranean Complex]].

| howto = Be near a hole to the next sublevel in a cave, and have something on the floor that is able to squish Pikmin, such as a boulder. Have the Pikmin be squished by the object (or enemy) and enter the hole right afterwards. If you enter quickly enough, the squished Pikmin will be there in the cutscene, and will appear squished.

| notes = The crushed Pikmin will not die when you arrive at the next sublevel, nor will they be counted for the total of deaths.

| explanation = In caves, when the player enters the next sublevel, all living Pikmin that are not buried in the ground are automatically teleported to the leader. And, because Pikmin do not die instantly after they are crushed, there is a small window where the game considers them alive, which can be used to keep them alive in the cutscene. And because the cutscene doesn't expect the Pikmin to be different from normal, it doesn't fix the fact that they are squashed, thus, making them appear flat in the cutscene.

===Disappearance without death===

{{glitch | reproducibility = High | consequences = Harmful | p2 = Yes | npcp2 = Yes | demonstration = [https://www.youtube.com/watch?v=HMitMEfZUGU&t=4m33s YouTube video (at 4:33)]

| effects = Causes a Pikmin to disappear without being counted as a death.

| howto = Be near a [[cave]] entrance hole, and have a Pikmin ready to be captured by an enemy. It can be a simple capture like a [[Swooping Snitchbug]]'s grab, or something more lethal, like a [[Bulborb|Red Bulborb]]'s bite. As soon as the Pikmin squeals, and before the Pikmin dies, enter the cave. The Pikmin will still be shown entering the cave in the cutscene, but will not be really present inside. When the day is over, the Pikmin count reveals that that Pikmin is gone, but not counted as a death.

| notes = A similar glitch can happen in caves; if the player throws a non-yellow Pikmin onto an electric wire, and quickly exits from the cave as it jolts back, but before dying, the Pikmin will disappear, but will not add to the death count.

===Fake Pikmin extinction===

{{glitch | reproducibility = Medium | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Makes the game announce a Pikmin extinction, without any single Pikmin death.

| howto = Go near the entrance of a [[cave]] with Pikmin on your party. When you're ready, press {{button|gc|x|wii|c|switch|x}} and {{button|gc|a|wii|a|switch|a}} at the same time, preferably the [[dismiss]] button slightly before. The cave chart will say you have all the Pikmin with you, but they should be idle. Confirm that you wish to enter the cave. After the falling cutscene, the game should announce a Pikmin extinction.

| notes = Because no Pikmin died, it will not affect the total number of Pikmin deaths. When you return to the overworld, all the Pikmin will be inside the Onions and Ship.

| normal = The game should recognize that no Pikmin will enter, and claim it's too dangerous to go in without any Pikmin.

| explanation = For each [[frame]], the code to dismiss the Pikmin comes after the code that updates their counter. As such, when the game is paused by the cave entering confirmation dialog box, it processes only what happened on that frame. And on that frame, the game tried to update the counter: all Pikmin are still in the party, so the counter indicates over 0 Pikmin (and the message box uses this value as well). However, after the counter updater code comes the dismiss code. Because the dismiss button was pressed on that frame as well, the game runs the code that dismisses all Pikmin and turns them pale. Normally, the game would update the counter on the next frame, but because the game is paused by the message box, the counter is only updated when the game returns to normal, i.e. when the cave exploration starts. When this happens, the game realizes there are 0 Pikmin and the player is inside a cave, so it triggers a Pikmin extinction.

===Lifeguards through the bridge===

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Makes a Blue Pikmin save a drowning non-Blue, through a bridge.

| prerequisites = Have a built bridge and Blue Pikmin.

| howto = Leave some Blue Pikmin idle on top of a bridge. Then, [[throw]] some non-Blues under the Blue Pikmin. After a bit, the Blues will grab the drowning Pikmin through the bridge, and throw them to safety.

| explanation = Normally, lifeguard Blue Pikmin that are close to drowning Pikmin don't have anything in between. As such, the check for whether a Blue Pikmin should rescue a drowning one doesn't take into account walls, objects or bridges. All that's needed is for the Blue and the drowning Pikmin to be close enough to one another.

===Negative Pikmin born===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = ? | p2s = Yes

| effects = Saves a negative number of Pikmin born to the high scores menu.

| prerequisites = Have not lost five or more Pikmin of the type you're saving the score for.

| howto = Convert all but one of your Red, Yellow, or Blue Pikmin to another type using [[Candypop family|Candypop Buds]], and then either repay the debt or collect the final treasure. A negative value will be saved to your high score of Pikmin born for that type.

| notes = The number is displayed the same way as a blank entry but can be differentiated in that it will be displayed above other records instead of being replaced. This glitch does not work with Purple or White Pikmin.

| explanation = The five wild Pikmin you get when unlocking a type do not count towards the high score. When you convert a Pikmin to another type, the number of Pikmin born of its original type is reduced by 1. By converting more Pikmin to other types than the number you sprouted yourself, the number of Pikmin born becomes negative.

===Non-Blue Pikmin underwater during cutscenes===

{{glitch | reproducibility = Medium | consequences = Helpful | p2 = Yes | npcp2 = Yes | youtube = AmqzPQkyvFo

|effects = Makes non Blue Pikmin survive in water for a few seconds, allowing the player to retrieve treasures without Blues.

|howto = Simply trigger a cutscene that does not pause the game (like the [[sunset]] warning or a new cave). While the cutscene is playing, non-Blue Pikmin will ignore water. If timed right, you can retrieve treasures without Blues. The effects continue for a few seconds after the cutscene ends. If you trigger several cutscenes at once, you can keep the glitch going for longer.

| explanation = The waterboxes might be unloaded during cutscenes.

===Pikmin stuck under bridge===

{{glitch | reproducibility = Medium | consequences = Harmful | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = LTy9zsrwotc

| effects = Makes a Pikmin become stuck under a bridge, without dying.

| prerequisites = Have a partially built bridge that's close to the water, such as the one in the [[Awakening Wood]] near the [[Unmarked Spectralids]] or the one in the [[Perplexing Pool]], near the [[Citadel of Spiders]].

| howto = There are two ways for the glitch to happen. One way is to throw Purple Pikmin on top of [[Sheargrub]]s (Awakening Wood) or a [[Cloaking Burrow-nit]] ([[Wistful Wild]]) that are chewing at a bridge that is not fully constructed. If you did it right, the Pikmin and carcass will fall through the bridge and onto the water, sometimes the former will stand on top of the latter, and not drown. Something similar can also happen with a [[Yellow Wollywog]], on the Perplexing Pool, though the creature will remain on top of the bridge. The second way to pull off the glitch is when a non-Blue Pikmin "swims" underneath a bridge, or if the bridge is constructed on top of them.

| notes = To release the stuck Pikmin, you should push them with your leader, as they cannot be whistled, or go into a cave. [[Wollywog]]s and Yellow Wollywogs can also get stuck under bridges in the same way; this too is rare.

| explanation = Deconstructed bridge sections have collision data that's sub-optimal, because they're meant to be temporary things. As such, collisions that involve bridge sections sometimes fail. Pikmin can survive drowning because, again, the bridge section's poor collision makes the game consider them as being out of the water.

===Pikmin vanish through the bridge===

{{glitch | reproducibility = Medium | consequences = Harmful | p2 = Yes | npcp2 = Yes

| effects = Makes a Pikmin vanish, but not die, by going through a bridge.

| prerequisites = Have a built [[bridge]] being eaten by [[Mandiblard|Sheargrubs]].

| howto = Throw a Pikmin onto a bridge that's being deconstructed by Sheargrubs. If you're lucky, it might mysteriously disappear from the screen.

| notes = The Pikmin will still be counted on the counter and appear on the [[radar]] as their respective colors, but will not appear above or below the bridge. Corpses and pellets, however, will still be on the bridge, to fix the glitch, enter a cave and leave it quickly.

| explanation = As with other bridge-related glitches, bridges are objects, not level geometry, so their collision detection is inferior. In addition, by having the Sheargrubs eat the bridge, it's possible for ground that used to be under the Pikmin to suddenly stop existing, which makes the game behave erratically.

===Remote Purple Pikmin===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = mQ-tOp5Q9lA

| effects = Makes a Purple Pikmin stuck to a Dwarf Bulborb teleport to the leader's hand, or be thrown while still stuck to the enemy.

| howto = Simply throw a Purple Pikmin at a [[Dwarf Bulborb|Dwarf Red Bulborb]], [[Dwarf Orange Bulborb]], [[Snow Bulborb]], or [[Dwarf Bulbear]] such that it crushes the enemy instantly. The Purple Pikmin will stay stuck to the enemy for a couple of seconds. During this time, whistle the Pikmin, get close to it, and hold {{button|gc|a|wii|a|switch|a}} to grab it. The Pikmin will be grabbed, as evidenced by the sound, but will not be in the leader's hand. The Pikmin will teleport to the leader's hand when the enemy's [[soul]] shows up. This means that the player can keep the enemy [[Camera#Off-camera|off-camera]], and only when the enemy is visible again will the Pikmin teleport to the leader. While the Pikmin is stuck, you can also release the button to throw it, but this will just make it spin in place on top of the enemy, and land right near it after a bit. This glitch also works if you switch to a different Pikmin in your group, and then use {{button|gc|padlr|wii|b|switch|r}} to switch to a Purple Pikmin, while making sure that the stuck Purple is the closest one in the group.

===Untouchable dead Pikmin===

{{glitch | reproducibility = Low | consequences = Harmful | p2 = Yes | npcp2 = ? | youtube = 1lIIQSkPB6E

| effects = Makes a Pikmin that should have died stay alive, but untouchable and invincible.

| prerequisites = Have a sublevel with a hazardous [[obstacle]] near the Research Pod and uncollected treasure. Have never seen the cutscene that plays for a suffering Pikmin of that hazard's type, in the current save file.

| howto = Collect a treasure, and during the cutscene, have the Pikmin touch a hazard whose cutscene has never played before. If you close the treasure collection cutscene at the right time, before the suffering Pikmin die, the game will resume to the Pikmin suffering cutscene, and afterwards, the Pikmin will stay alive, and impossible to interact with.

| notes = The Pikmin will still count as a death, even though it still counts as existing, as proven by the Pikmin counter, and by the Pikmin that appear on the next sublevel or on the surface.

 

===Beetle flip glitch===

{{glitch | reproducibility = Low | consequences = Harmful | p2 = Yes | npcp2 = ? | youtube = BLYxdnYPToE

|effects = Makes an [[Anode Beetle]], [[Iridescent Flint Beetle]], [[Iridescent Glint Beetle]], or [[Doodlebug]] that gets attacked ignore the attack and continue what it was going to do. Anode Beetles instantly enter the "flip upright" animation and start turning to zap, whereas other beetles do the squash effects, scurry off in another direction, and fail to drop anything; this will not advance the list of spoils, so the player can hit again and get the reward they were meant to have obtained.

|howto = Throw a Pikmin at one of the aforementioned enemies while it is idling. The glitch will happen if the Pikmin lands on the same frame in which the creature would begin turning. In the Anode Beetle's case, this is when it would begin turning to face a zapping partner, and for the other beetles, when it would begin turning to face a new direction to scuttle into.

|notes = If the player triggers this glitch accidentally, they could end up not reacting to the enemy's unexpected behavior in time, and could lose Pikmin or treasure. To rectify this, they can throw two Pikmin in a row, so the second one hits after the first one causes the glitch.

|normal = The creature would get flipped, and enter a vulnerable state or drop a spoil.

|explanation = The variable that controls how much time is left until a flipped beetle returns to normal is set to zero every time it enters the state where it is turning. If the beetle enters that state at the same time it enters the "flip upside-down" state, the enemy will be successfully flipped, but the "time remaining" variable will be set to zero, and the enemy will flip upright straight after.

===Blowhog stuck above water===

{{glitch | reproducibility = Medium | consequences = Helpful | p2 = Yes | npcp2 = Yes | youtube = JLmGOM9Yhec

|effects = Makes a [[Withering Blowhog]] stuck between the ground and water, endlessly repeating its falling animation.

|howto = Go to the [[Shower Room]], and make it so that the Withering Blowhog near the landing site hovers between the ground and water as it stops to inhale. Then, make it fall. It should permanently repeat its falling animation.

|notes = This can be used to defeat the enemy without it being able to shake the Pikmin off.

|explanation = The enemy only performs its landing animation when certain spots of its underside detect a ground.

===Dud bomb-rocks===

{{glitch | reproducibility = Low | consequences = Helpful| p2 = Yes | npcp2 = ? | youtube = HffrdnfsmNg

|effects = Makes a [[bomb-rock]] thrown by a [[Careening Dirigibug]] stay in place without detonating, and eventually disappearing.

|howto = Go on sublevel 6 of the [[Subterranean Complex]] and lure a Careening Dirigibug to you. Walk to the exit [[geyser]], and stand between it and the ledge. With luck, the enemy will throw a bomb, but it will stay in place without exploding, between you and the geyser.

|explanation = If the bomb is lodged between a geyser and a leader, it will stay there and won't touch the ground. The bombs are programmed to only explode when they touch the ground. Possibly as a safety measure to prevent object flooding, for scenarios like this, bomb-rocks were made to despawn after some seconds.

===Empty Pellet Posy===

{{glitch | reproducibility = Low | consequences = Harmless| p2 = Yes | npcp2 = ? | youtube = vz69NhFNmtA

|effects = Makes a [[Pellet Posy]] appear without its pellet.

|howto = Go to Awakening Wood between days 11 and 30 inclusive on a file where the blue Pellet Posies by [[Decorative Goo]] are still there. Kill every enemy that drops pellets before every Pellet Posy matures. With luck, if each enemy drops their maximum number of pellets, then when all the Pellet Posies mature, 2 of them will have missing pellets.

|explanation = The game caps the number of pellet objects to 48 at all times. This cap includes the pellets on Pellet Posies. When the Pellet Posies mature, there would be 50 pellets if this cap didn't exist. Therefore, once there are 48 pellets, 2 Pellet Posies do not create a pellet.

===Floating enemies===

{{glitch | reproducibility = Low | consequences = Harmless | p2 = Yes | npcp2 = Yes | youtube = ShWBvyyWKpM | vcaption = The glitch in question manifests itself at 1:18

| effects = Makes an enemy float in mid-air.

| howto = This glitch happens mostly randomly. When you are close to an area where an enemy will fall down, it may fall on a dead enemy or treasure. This will make the enemy float in mid-air, but it counts as being on the ground. This can also be triggered by throwing Purple Pikmin at the enemy as it falls – the Purple Pikmin's pound attack will cause enemies to lose their falling momentum. An identical effect can be achieved by using Purple Pikmin to stun an enemy, most commonly an airborne one such as a [[Swooping Snitchbug]], on top of a [[gate]] and then working on destroying it; the enemy will remain at the same altitude at which it was stunned at despite the gate's top moving down.

| notes = Using a dose of [[ultra-bitter spray]] on the floating enemy fixes the glitch. If this glitch happens with an Armored Cannon Beetle Larva, the boulders it shoots will fall down as if it was on a cliff.

| explanation = For collision purposes, enemies have long vertical hitboxes, probably a universal height. Normally, it's not possible to have an enemy fall on top of another, and the tall hitboxes are to make sure the enemy that's falling from above slides out of the way at a comfortable distance. If, however, the falling enemy is spot-on on the grounded enemy's center, it will have no direction to slide into, so it takes the collision as landing on solid ground.

===Invincible Wollywog===

{{glitch | reproducibility = Low | consequences = Depends | p2 = Yes | npcp2 = ? | p2s = Yes | demonstration = [https://clips.twitch.tv/KitschyImpartialPepperoniCorgiDerp Twitch video]

| effects = Makes a Wollywog be stuck in the ground, and invincible. Helpful for those who want to avoid the creature, harmful for those who want the [[Poko]]s it yields.

| howto = The timing is strict, but you must hit a [[Wollywog]] with a Purple Pikmin right as it starts jumping up. If done correctly, it should get trapped underground and become unable to move, as well as become invincible. Wollywogs can also become stuck for a variety of reasons, especially if their jumps make them land on top of other objects or oddly-shaped structures; this too makes them invincible unless they manage to land.

| explanation = Wollywogs are only programmed to detect that they died when they're on the floor. Hitting a jumping Wollywog with a Purple Pikmin before it has left the ground makes it enter the "impact bounce" state, nullifying the jump. Because of the animation, the Wollywog gets slightly embedded under the ground, and is considered airborne. Because its momentum has stopped due to the Purple Pikmin stomps, it never lands, and so can never register the fact that it died.

===Leader stuck in pipe===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = ? | npcp2 = Yes | other = [https://www.youtube.com/watch?v=SI0KDTwJW7k&t=13m45s The glitch in question happens at 13:45]{{dead link|May|2020}}

| effects = Causes the active leader to be stuck on a pipe and makes the player unable to switch leaders or move, until the [[Bumbling Snitchbug]] frees them.

| prerequisites = Be in a sublevel with a Bumbling Snitchbug and fully-covered pipes (such as the corridor in the 6th sublevel of the [[Shower Room]]).

| howto = Walk into a fully-covered metal pipe where a Bumbling Snitchbug is flying under, and let the Bumbling Snitchbug catch you and throw you inside the pipe.

| notes = The glitch cannot be undone unless the Bumbling Snitchbug picks up the leader again.

===Non-Reds on a Fiery Bulblax===

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes

|effects = Makes non-Red Pikmin ignore a Fiery Bulblax's flames.

|howto = Lure the enemy into the water, and when its fire goes out, toss non-Red Pikmin at its back. When it walks out of the water, its fire should return, but the Pikmin on its back should take no mind to the fire.

|explanation = When the Bulblax leaves the water, there is no code to alert the Pikmin that the object they're attacking has changed its elemental properties, so the Pikmin keep the old behavior – attacking, instead of the new one – being set ablaze.

===Petrified Volatile Dweevil suicide===

{{glitch | reproducibility = Medium | consequences = Helpful | p2 = Yes | npcp2 = Yes | youtube = 0cNUbwxEEtE | other = [https://youtube.com/watch?v=2DKvQoqUzBw YouTube video showing what happens if this glitch is performed on the Japanese version's Piklopedia]

| effects = Makes a petrified Volatile Dweevil kill itself, yielding normal petrification death spoils.

| prerequisites = Have at least one [[ultra-bitter spray]].

| howto = Approach a [[Volatile Dweevil]]. Just as it's about to die, petrify it; the timing isn't too strict. If you did it correctly, the creature will have exploded, but the game will still have recognized your petrification, giving out a nectar or some sprays as a result. This removes the need to use Pikmin in order to kill a petrified Volatile Dweevil, but carries some danger, seeing as the explosion might cause damage.

| notes = This can be done on the Piklopedia, but seeing as no nectars ever come out, it is as if the glitch hadn't happened at all. In the Japanese [[Region|version]]'s Piklopedia, the game freezes instead.

| explanation = There's a point on the bomb-rock's explosion where it can no longer be petrified and has to explode; this happens a few [[frame]]s before a normal explosion. During this point, petrification attempts will only turn the Dweevil into stone, but not the bomb-rock. Seeing as the explosive destroys the Dweevil, and seeing as the Dweevil is considered to be petrified, even if its petrification animation has just barely started, the game gives out nectars or sprays.

===Sped up Dwarf Red Bulborb===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = Yes | npcp2 = Yes

| effects = Makes a Dwarf Red Bulborb's animations temporarily speed up.

| howto = Make the Dwarf Red Bulborb shake, kill it, or crush it with a Pikmin throw while it is in the middle of turning on the spot. You can also do that while the enemy is walking forward, although the effect won't be as noticeable.

| notes = When the Dwarf Red Bulborb is in the <code>turn</code> state, its animations are sped up to double speed. In the <code>walk</code> state, they are sped up around 1.3 times. Interrupting the enemy during one of these states will not restore its animation speed to normal.{{cite web|https://cdn.discordapp.com/attachments/177496240035069962/903697187228225536/Dolphin_5.0-15421___JIT64_SC___Vulkan___HLE___FPS__30_-_VPS__60_-_100___GPVE01_2021-10-29_13-28-57.mp4|Discord video|Discord|published={{date|29|October|2021}}|retrieved={{date|5|November|2021}}}}

===Sped up reviving enemies===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = Yes | youtube = ciY7fbGqvbY | other = {{cite youtube|xt6cEMqt-YQ|of a Gatling Groink's animations being sped up after a revival, in [[Secret Testing Range]]|published={{date|8|May|2017}}|retrieved={{date|24|April|2020}}}}{{cite youtube|p18zntLYpiU|m=3|s=38|of a Gatling Groink's moving animations speeding up after a revival, in [[Cavern of Chaos]]|published={{date|22|April|2020}}|retrieved={{date|23|April|2020}}}}

| prereq = Be in a sublevel with at least two of the enemy in question.

| howto = Kill the enemies and retrieve one of the corpses while the others are reviving. If the order you chose is correct, which is not something possible to determine while playing normally, the revived enemies will be sped up.

===Sped up spawned enemies===

{{glitch | reproducibility = High | consequences = Depends | p2 = Yes | youtube = ciY7fbGqvbY

| effects = Makes it so a [[Mitite]] or [[Unmarked Spectralids]]'s animations are sped up. This also makes them die quicker.

| prereq = Be in an area or sublevel where you can spawn multiple of the enemy at will. For Mitites, there should be enough [[egg]]s to spawn one group and then spawn another (or for one group to be buried in the ground), and for Unmarked Spectralids there should be enough [[vegetation]] that spawns them when bumped against such as the [[Margaret]] and [[Figwort]] near the base of [[Awakening Wood]].

| howto = Collect carcasses of the enemies in question. Then, spawn some more of that enemy, and some of them will be sped up. For every one carcass you collect, the number of enemies that will be sped up increases by one, and decreases whenever a sped up enemy spawns.

| notes =<br>

** For Mitites that spawn from the ground, one of the Mitites will always be at normal speed.

** A [[#Sped up reviving enemies|similar glitch]] also affects Spotty Bulbears and Gatling Groinks.

| explanation = In memory, there is a list with data about all of the Mitites that can be loaded at once and another for all the Spectralids. When the area or sublevel is loaded, the data on this list is cleared. Whenever a new enemy needs to spawn, it occupies one slot of this list and initializes its data. When that enemy is defeated and its carcass is being beamed up by the Onion, its animation speeds up, which is controlled by one variable in that enemy's slot in memory. Once the enemy is completely absorbed by the Onion, its object vanishes from the game world, and its slot in memory is marked as vacant. When a new enemy is spawned, it takes up the first available slot in memory and initializes some data. The problem comes from the fact that the data that gets initialized does not include the variable that controls the animation speed, and so it just uses whatever was left behind in memory at that point. The reason buried Mitites always have one enemy that is not sped up is because when the area loads, the Mitite responsible for the group is already created and exists as an object in the game world, meaning it uses the regular cleared data in the list.

===Stuck Waterwraith===

{{glitch | reproducibility = High | consequences = Depends | p2 = Yes | npcp2 = Yes | youtube = h7fS9k6_fvo

| effects = Makes the Waterwraith's rollers unable to move, though the creature itself will still move.

| howto = Go on sublevel 4 of the [[Submerged Castle]]. Lure the Waterwraith into entering the large pipe area. It should get stuck fairly easily.

| notes = The Waterwraith's rollers can still crush Pikmin, and will harm the leaders indefinitely if they contact them.

===Titan Dweevil treasure glitch===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = Yes | npcp2 = ? | youtube = RXlmnr_IpBA | vcaption = Demonstration of the glitch, at 4:30 (unavailable video).

| effects = Makes a treasure re-appear in the [[Titan Dweevil]]'s hands.

| howto = Beat up one of the Titan Dweevil's treasures until it's nearly detached. When the creature is just about to use that treasure, [[ultra-bitter spray|petrify it]]. Attack the treasure and detach it before the boss breaks free.

===Wollywog super-jump===

{{glitch | reproducibility = High | consequences = Helpful | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = IHXSagmmcwo

| effects = Makes a Wollywog or Yellow Wollywog jump very far.

| howto = Get two leaders next to a Wollywog or Yellow Wollywog. Place them close enough that the creature will notice them, but not so close that it will jump. Keep one leader in this spot, and with the other leader, walk up to the Wollywog and spray it with ultra-bitter spray as soon as possible. The glitch will work so long as you spray the enemy before it starts its jump, but after it chose a target to jump to. Then, quickly run away with that same leader, preferably in a straight line. After enough time has passed for the petrification to wear off, switch back to the leader that's still close to the enemy. It should reactivate and perform a massive jump in the direction of the first leader. It is possible for it to travel any distance this way, but if it hits an obstacle or wall, it might stop short.

| explanation = After a Wollywog decides its attack target, it will jump to above where the target is in a straight line. Normally, there's no risk of the enemy making a large jump, since a leader or Pikmin needs to be close by to be considered a target. But by petrifying, this gives the leader enough time to run away and create distance. The player must switch to a different leader that is standing next to the Wollywog because while it is [[Camera#Off-camera objects|off-camera]], it will not be active, so it will not perform any jump.

===Zombie Dweevil===

{{glitch | reproducibility = Low | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = gaHYdGQh-0Q

| effects = Keeps a Dweevil alive, but with 0 [[health]] remaining.

| howto = You have to try to make a [[Dweevil]] run out of health just when it picks up an object. If successful, the creature will be alive and carry the object around, while supposedly dead.

| notes = To stop the glitch, make the Dweevil drop the object. A Dweevil in this state cannot be petrified, even though "normal" Dweevils that are carrying objects can. A similar "zombie" glitch also exists for the [[#Zombie Pellet Posy|Pellet Posy]].

| explanation = When the Dweevil is in the "carrying object" state, the game assumes it's alive, regardless of its health. Normally, it can only enter this state if it's alive, and while on this state, it cannot be hurt. However, with precise timing, it can pick up an object at the same time it loses its last bit of health. If so, the game doesn't kill it, because it's entering the "carrying object" state (it's crouching down to pick it up).

===Zombie Pellet Posy===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes | image = Zombie Pellet Posy NPC P2.jpg | youtube = xw1ytja45oU

| effects = Keeps a Pellet Posy alive, but with 0 [[health]] remaining.

| howto = Have a Pikmin attack a Pellet Posy from the ground. Make it so that, when the Pikmin jumps to the plant's stem, it pummels it an even number of times. If the last hit were to cause the Posy to fall, it will instead stay alive with 0 health. Whistle the Pikmin at this point to keep the plant that way, otherwise the Pikmin will kill it. A consistent way to do this is to throw a non-Red and non-Purple Pikmin near a Pellet Posy, let it attack once while on the ground, let it attack a few times after it latches on by itself, and whistle the Pikmin just as the plant's health goes to 0.

| notes = Only the number of "pummel while latched" hits counts for this. To count the number of hits, follow the health wheel's drops, and not the Pikmin's actions. A similar "zombie" glitch also exists for the [[#Zombie Dweevil|common Dweevils]].

==Aesthetic==

 

===Broken Treasure Gauge===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Makes the [[Treasure Gauge]]'s needle point directly upwards, for a split second, and gives the gauge its color, if it was previously black-and-white.

| prerequisites = Have collected the [[Prototype Detector]].

| howto = Pause the game. After you press {{button|gc|start|wii|+|switch|+}} to unpause, rapidly mash {{button|gc|y|wii|-|switch|y}} so that you switch leaders as soon as possible. If you managed to press the button at the right time, the needle will be stuck for the duration of the leader transition. If the Treasure Gauge was in black-and-white, it will have gained color.

| notes = The needle gets fixed when the leader transition ends, and the coloring gets fixed when you pause again, or when you leave the area or the game. There are {{frames|2}} frames in which pressing the leader button will trigger the glitch, and these are the first frames in which changing is possible after an unpause. If an [[Antenna Beetle]] is present, the gauge will have the needle pointing up, and will not have the purple effect, but when the needle gets unfrozen, the purple effect starts and the gauge starts acting as it should when being affected by an Antenna Beetle.

| explanation = The Treasure Gauge, along with the other normal HUD items, gets loaded and set to an initial state when the player unpauses. The Treasure Gauge's initial state is colored, and has the needle pointing directly up. The needle is updated every frame, except when a leader transition is occurring, so if the player manages to switch leaders while the Treasure Gauge is still in its initial state, it will stay that way until the transition is over. As for the coloring, it is only updated when a treasure is collected, when the area is left, when an Antenna Beetle dies, or when the game is paused and unpaused, so it stays colored until one of these updates happen.

===Cave entrance leader mixup===

===Cave hole glitch===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Makes a leader be inside the hole/geyser model.

| prerequisites = Have [[The Key]] to the current [[Challenge Mode (Pikmin 2)|Challenge Mode]] level uncollected.

| howto = Place a leader in the center of the spot where the hole to the next sublevel will appear (or the exit geyser). Then, have the Pikmin deliver the Key. If you placed him in the correct spot, he should be inside the hole (or geyser).

| notes = It's possible to walk out of the hole or geyser, but it's not possible to go back in. You can also place objects and Pikmin on the spot where the hole will spawn. [[Treasure]]s and [[Enemy|enemies]] disappear and fall back down to the sublevel on top of the structure, and [[Pikmin family|Pikmin]] are pushed out of the way. If the leader [[lie down|lies down]] where the hole will appear, he will fall from the sky above the hole after the Key's cutscene is over.

| explanation = Collision between object A and B is only detected when an object A attempts to move from a position outside object B to a position inside it. If the initial position of A is already inside, no collision is detected, and hence, object A can remain inside B.

===Double cash register===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Makes the "cash register" sound play twice, and makes the [[Poko]] value numbers pop out twice.

| howto = Enter a cave, and exit it by any means, with or without making monetary profit. On the [[Menu#Cave exited|Treasures Salvaged screen]], wait for the list to scroll entirely. When the cash register sound plays and the numbers at the bottom pop out, press {{button|gc|a|wii|a}}. The sound should play a second time, and the numbers should pop out once again.

| explanation = Pressing {{button|gc|a|wii|a}} makes the game skip the listing, and go directly to the register sound and number pop out. The code for this is simple; instead of literally skipping past the list's scrolling, it just fully scrolls the list, plays the sound and animation, and marks the listing as "complete". Erroneously, the player can still press the button a second or so after the listing is completed normally, which results in the game running the code to "skip", playing the sound and animations a second time.

===Early third day cutscene===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | youtube = 6aqkU5dZhFA

|effects = Makes [[Hocotate ship|the ship]] start the [[cutscene]]s that take place at the beginning of the third [[day]] start in the second day instead.

|prerequisites = Be on the second day.

|howto = When you first enter the [[Emergence Cave]], grow Purple Pikmin and leave the cave using the [[geyser]] without collecting the [[Sphere Chart]]. Once outside, store the Purple Pikmin in the ship's hull. Enter the cave again, and leave without collecting the Sphere Chart once more. When you reach the surface, the cutscenes that are meant to start on the third day (the ship informing about the Purple Pikmin having been stored on its hull and how Olimar should've instructed Louie about the [[controls]]) will play on the current day instead.

|explanation = When the player collects the [[Sphere Chart]], the game automatically ends the day when the player exits the Emergence Cave. But, because the treasure isn't retrieved, the game won't end the day, and the player is able to go back to the cavern. Since the Purple Pikmin hull cutscene plays when the player starts a day or reaches the surface with the Purple Pikmin stored, the cutscene will play then.

===Frozen Glowstem===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | youtube = ga_6QmokF6I | vcaption = Demonstration of the glitch at 4:29.

| effects = Makes a [[Glowstem]] temporarily stuck, not emitting light.

| howto = Have a leader and some Pikmin near a Glowstem, and another leader a bit far away, facing away from the Glowstem. Make the Pikmin on the first leader's party bump against the Glowstem. After they touch it, quickly take them away from it and switch leaders. If the other leader was positioned sufficiently far, the Glowstem will be [[Camera#Off-camera objects|off-camera]] once the focus shifts onto the other leader. Then, walk with this leader towards the Glowstem. If the timing was right, it should remain disabled until it's touched once more.

| notes = If Pikmin keep touching the Glowstem before switching to the other leader, once the Glowstem is back into view, it'll be updated.

===Floating Cupid's Grenade===

{{glitch | reproducibility = Low | consequences = Helpful | p2 = ? | npcp2 = ?

| effects = Makes a Cupid's Grenade float and go to an Onion by itself.

| howto = Go into 2-Player Battle mode. Have a Pikmin grab a [[Cupid's Grenade|Cupid's Grenade]] near a dead enemy's carcass. The Pikmin will grab the Cupid's Grenade and start to take it right through the carcass. The Pikmin will get stuck in front of the carcass, walking endlessly until the Cupid's Grenade enters the Onion. Meanwhile, the Cupid's Grenade will continue to move without any Pikmin carrying it.

===Floating nectar===

{{glitch | reproducibility = High | consequences = Harmless | p2 = ? | npcp2 = Yes

| effects = Makes nectar float in mid-air.

| howto = Cause a drop of [[nectar]], such as one from a petrified enemy, to fall on top of a pile of sticks used to build a [[bridge]]. If the sticks are removed from under the drop by building the bridge, the drop will remain suspended in the air. Pikmin can be made to drink the nectar by throwing them at it, and they will fall back to the ground once the nectar is all used up. A good place to do this is in [[Awakening Wood]] with a [[Yellow Wollywog]] near the bridges.

===Ghost leader===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | youtube = sAPGxpaEYKc| other = [https://www.youtube.com/watch?v=T_Jly5P0S3w Leader following inside a cave]

| effects = Leaves a leader's "ghost" following the active leader. This ghost can be harmed.

| prerequisites = Have both leaders alive.

| howto = Have leader B follow leader A, and knock out leader B. Then, bring an enemy to its body. Inside a cave, his body is technically in the same spot he was knocked out at, except he turns invisible. Aboveground, the knocked out leader can be found near the ship. Then, get the enemy to do its "shaking" attack. This attack will be able to hurt the knocked out leader. He will then wake up and follow the active leader around. Inside a cave, he'll still be invisible, but you'll be able to see him aboveground. Either way, you can hear him walk, you can see his dust trails, you can hear him moan while idle, and every time he's damaged with a shake attack, you'll see sparks appearing and hear him grunt. If the leader that gets killed wasn't following another one, or if you dismiss him after the zombie state, it'll be impossible to have the glitched leader follow the living leader. In addition, dismissing will make him keep walking in whatever direction he was moving.

===Half petrified Volatile Dweevil===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

| effects = Petrifies only half of the Volatile Dweevil.

| prerequisites = Have the [[Volatile Dweevil]] on the [[Piklopedia (Pikmin 2)|Piklopedia]].

| howto = Petrify the Volatile Dweevil on the Piklopedia. Right before it breaks free, petrify it again. If you did it correctly, only the [[bomb-rock]] on its back should've been petrified. An easy way to ensure the correct timing is to mash {{button|gc|z|wii|1}} when the creature is about to break free, and quickly stop the second it does. If you petrify it in this state, the creature itself will be turned into stone, but the bomb-rock will break free.

| explanation = The bomb-rock and the creature must count as two different objects. They also react to the petrification at different times. With the right timing, their petrifications can be desynchronized. A similar glitch can happen with the [[Waterwraith]] and its rollers.

===Lying down in a cutscene===

{{glitch | reproducibility = Low | consequences = Harmless | p2 = Yes | npcp2 = ? | youtube = BkYqlsomgvw

| effects = Makes a leader jump down a hole or enter the [[sunset]] cutscene whilst lying down.

| howto = If one of your leaders is knocked over by an enemy just as you are going in a hole, or the day is ending, he will enter the cutscene while lying down. This will not work if he lies down by himself with the [[Five-man Napsack]].

| explanation = When falling down the hole, the game sets the leaders' animation to be the "jump down hole" animation. However, if they're knocked down by an enemy after the animation's been set, the animation will be overwritten with the "fall down" animation. The jumping movement will still be correct, but the animation will not.

===Multiple rules closures===

 

 

 

{{todo|Find somewhere else to put this, since it's not a glitch.}}

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes

 

 

 

 

 

===Undead Ranging Bloyster===

{{glitch | reproducibility = High | consequences = Harmless | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = 5fK_oL0R-xU | other = [https://www.youtube.com/watch?v=nAbt2JJjL3w&t=2h20m56s Another demonstration]

| effects = Makes a [[Ranging Bloyster]]'s antenna flash and emit waves even after death.

| howto = Fight the Ranging Bloyster, and have it perform its death animation [[Camera#Off-camera objects|off camera]].

| explanation = none

{{glitch | reproducibility = Low | consequences = Helpful | p2 = Yes | npcp2 = Yes | youtube = 9zpNEphShKE | vcaption = Demonstration of a use of the glitch, at 8:44.

| 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.

| 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.

===Bridge corner pop-up glitch===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = Yes | npcp2 = Yes | youtube = eWCaWOqMZbI

| effects = Makes Pikmin or a leader go through a bridge, and occasionally, through the ground surrounding the bridge. Leaders that fall off the level can teleport to helpful locations, but Pikmin die.

| howto = In the corners of some bridges, like the South corner of the bridge at the West of the landing site, in the [[Awakening Wood]], if you or a Pikmin goes under the bridge and tries to press against the wall on the corner, they might pass through the bridge and be placed on top of it. In addition, throwing Pikmin while below the bridge, while near the glitchy wall, will instantly place them on top of it. Finally, there are reports of leaders and Pikmin falling through the floor when attempting to pass through the corner; this seems to be a lot rarer.

{{glitch | reproducibility = Medium | consequences = Harmless | p2 = ? | npcp2 = Yes | youtube = 9eGdHDfT9pM | vcaption = Glitch occurs at 14:18

| howto = Kill the [[Titan Dweevil]] for the first time. When you do, [[Louie]] will fall to the ground and a cutscene will start. At this point, {{button|gc|c|wii|padd}} or {{button|gc|x|wii|c}} can be used to swarm or [[dismiss]] the Pikmin underneath Louie when he lands, and the Pikmin will carry him off the screen when the cutscene starts.

| notes = Once the ship starts speaking, the Pikmin will pause.

{{glitch | reproducibility = Low | consequences = Harmless | p2 = ? | npcp2 = ?

| howto = Rarely, sublevel 7 of the [[Hole of Heroes]], where the [[Ranging Bloyster]] is, will have two gates inside one another. If it doesn't happen, you can keep resetting until it does, since reloading the [[Saved game|save file]] takes you to the same sublevel, but with a different layout.

{{glitch | reproducibility = Low | consequences = Harmful | p2 = Yes | npcp2 = Yes | demonstration = [https://clips.twitch.tv/YummyGrossWalrusCmonBruh Twitch video]

| notes = [[Glitches in Pikmin#Embed glitch|This glitch can also happen in ''Pikmin'']].

===Extended damage state===

{{glitch | reproducibility = Medium | consequences = Harmful | p2 = Yes | npcp2 = Yes | youtube = jRPe_bOqayE

| effects = Makes a leader that is taking certain kinds of damage to continue to suffer the effects until the game is unpaused. If an attack causes the leader to be knocked away (e.g. a [[Bulborb|Red Bulborb]]'s shaking attack), he will continue to do so, though he will stop if he hits certain walls. If hit by a boulder (e.g. from the [[Decorated Cannon Beetle Larva]] in the Wistful Wild), the leader continuously suffers damage from it, starting his crushing animation each time (though invulnerable while the animation is playing). If it's a normal attack, the leader will keep moving in the direction it was going (if he was moving).

| howto = Find a location where a leader can get hurt. Place one leader under an [[Onion]]'s beam, preferably facing that location, so that when you change back to this leader, the [[camera]] will be able to show what is happening. Then, leave the second leader idle in that location. Having him [[lie down]] will stop him from running away from enemies. Swap back to the leader under the Onion. As soon as the idling leader gets damaged, access the Onion's menu.

| notes = If the idle leader loses all of his health in this way, the screen will go dark, but return to normal right away. The Onion menu can still be operated, but closing it will cause the game to [[softlock]]. Entering an Onion menu while the secondary leader is running away from an enemy or chasing after the current leader can also keep them moving in the same direction. Sometimes, opening the Onion menu may even disable the secondary leader's enemy escape logic altogether.{{cite youtube|yO50dLhsA84|of a secondary leader no longer running away from enemies|published={{date|11|August|2021}}|retrieved={{date|21|August|2021}}}} A leader that is being knocked away with this glitch will speed up if he hits an object, such as an enemy, an Onion's leg, or the other leader.

}}

{{glitch | reproducibility = Medium | consequences = Harmful | p2 = Yes | npcp2 = Yes | p2s = Yes | youtube = SjkshAlRaH0 | vcaption = Falling with dweevils | other = [https://www.youtube.com/watch?v=pvHglwyXWzw Falling without dweevils]

| effects = Makes a leader frozen or unusable.

| prerequisites = Have the [[Napsack]].

| howto = First, you must get a leader ready to fall into the [[pit]]. This can be achieved by going [[out of bounds]], like with a [[#Seesaw block clip|seesaw block clip]]. Then you must time a hold of {{button|gc|x|wii|c}} such that the leader is in the middle of the lying down animation when he touches the pit. This is a bit random as explained [[#Napsack warp|here]], but if you are successful, the leader will come back but without an antenna light, and the only action you can do is leave lying down mode. This will make him stand in place with his head held low, and stuck forever. If, before touching the pit, you swap to the other leader, then you will be unable to switch back, and the frozen leader will either vanish, or be able to be carried, but frozen after being delivered. A different thing can happen if the leader touches the pit whilst carried by a Dweevil. He can be teleported to the Research Pod and become invisible, except for his antenna's light. In this state, he can be returned to normal by performing any action while controlling him, or by whistling him with another leader. If a leader is on top of the Research Pod and the other leader performs other actions (like throwing Pikmin), the first leader will eventually appear on the ground somewhere, on the same semi-frozen state with no antenna light described above.

** The glitch can be fixed by ending the day, exiting the cave (or Challenge Mode level), or by going inside a cave or down a sublevel, using the non-frozen leader.

** A leader that is lying down without his beacon light and hasn't been recovered to the Research Pod or Onion yet will be able to be picked up by Dweevils.

** Trying to force the game to switch to the frozen leader, by letting the non-frozen one's [[health]] drop, for instance, will make the frozen leader stand up and freeze again; the [[HUD]] will be gone, and only the camera can be moved.{{cite youtube|9zpNEphShKE|showing what happens when the game is forced to switch to the frozen leader|m=4|s=25}} Time still flows, and the sunset cutscene can be entered like normal.{{cite youtube|4ZGAynmcrAk|showing the frozen leader glitch during sunset}}

 

|effects = Makes the Hideous Victual slide away from its intended position, spawn partially inside the floor, etc.

|howto = There are no known ways to reproduce the glitches. Randomly, when entering sublevel 6 of the [[Glutton's Kitchen]], the treasure can behave oddly. There have been reports of it sliding as it spawns{{cite web|https://www.twitch.tv/videos/146946663|Twitch clip|Twitch|published={{date|24|May|2017}}|retrieved={{date|25|May|2017}}}}{{cite youtube|z6_pymbaxTM|of the Hideous Victual sliding away (language warning)|published={{date|16|October|2018}}|retrieved={{date|17|October|2018}}}}{{cite web|https://clips.twitch.tv/BlindingCrazyPigBigBrother-3bHP9bddKVNgwyNV|Twitch clip|Twitch|published={{date|22|March|2021}}|retrieved={{date|22|March|2021}}}}, flying off{{cite youtube|jxQNNjCc9S0|of the Hideous Victual flying off as it spawns}}, or becoming embedded in the ground{{cite youtube|nPCZhcueavQ|of the Hideous Victual embedded underground, followed by a game crash}}. When it slides, it can even end up close to the starting location{{cite web|https://clips.twitch.tv/TolerantObservantFrogYouWHY|Video|Twitter|published={{date|26|May|2017}}|retrieved={{date|26|May|2017}}}}{{cite web|https://clips.twitch.tv/PlacidSpicyYakTTours|Twitch clip|Twitch}}{{cite web|https://www.twitch.tv/videos/374071581|Video|Twitch|published={{date|2|February|2019}}|retrieved={{date|2|February|2019}}}}, or so far away that it can't be retrieved{{cite web|https://twitter.com/keisen2853/status/861528352330350592|Video|Twitter|published={{date|8|May|2017}}|retrieved={{date|25|May|2017}}}}. It is possible that the problem happens because it spawns next to the [[Meat of Champions]], even though that treasure rarely moves, and there are cases of weird Hideous Victual behavior without the Meat of Champions being involved.

 

|prerequisites = Be on day two or further.

|howto = Gather some Pikmin in your party, and whistle the other leader so that he's in your group as well. Move far away from the landing site, and wait until the day is about to end. Either time it so you switch leaders right when the sunset cutscene is about to start, or rapidly switch leaders and hope it happens. When the cutscene starts, some or all of the Pikmin in the group should count as left behind, despite being in the group.

|explanation = When switching leaders while the two are together, the game makes all Pikmin in the current leader's group idle, switches the current leader, and calls the Pikmin to the new leader right away. The fact that the Pikmin do the "got called" animation supports this. The Pikmin only count as belonging to the group when they finish that animation, so between that time, they are technically idle. If the day ends during this time, they're treated like any other idle Pikmin, and get left behind.

 

|effects = Makes the Pikmin take the wrong path when carrying a treasure.

|prerequisites = Have the [[Geographic Projection]] or [[Air Brake]] uncollected. Have the bridge to the west of the [[Awakening Wood]]'s landing site built.

|howto = Begin carrying the Geographic Projection or Air Brake. Once it reaches the middle of the bridge to the west of the landing site, whistle your Pikmin. Then, order them to carry it again. There is a chance they will start carrying it off the side of the bridge, and start climbing up walls. After a while, they eventually return to a normal path.

 

===Leader down pause glitch===

| effects = Makes it so Pikmin cannot [[carry]] items, nor be affected by explosions and [[crushing]]. Makes one [[leader]] invulnerable to being hurt.

| howto = Enter any sublevel and have a leader ready to be killed. At the same time the final hit connects, pause the game. If timed correctly (which is hard, since it is a [[frame]]-perfect glitch), the game will pause at the same time the leader takes damage. On the pause menu, choose to leave the cave. The game will then return to the action, but instead of quitting the cave, it will show the leader's knockout [[cutscene]] with the pause menu on top of it. The gameplay will continue like normal, except for the menu. Your inputs here will reflect both the in-game action and the menu. You can quit out of the menu's question and leave the menu entirely to continue playing. If you use {{button|gc|l|wii|padl}} or {{button|gc|r|wii|padr}} to switch menu pages, the game will fade and continue with the "abandon cave" command, so be careful. If you leave the menu, you'll play like normal, except Pikmin won't be able to carry things, and your remaining leader will ignore enemy attacks and hazards. Carriable objects float a bit in the air, and this includes the leader; this can be used to [[#Leave boundaries|go out of a metal cave's boundaries]] with the help of an enemy. If you do this, attempting the [[#Frozen leader glitch|frozen leader glitch]] will make the leader float above the bottomless pit, and waking him up will make him continue his fall and respawn like normal.

| explanation = Since the leader's knockout cutscene begins one [[frame]] after the leader receives the final point of damage, there is a one-frame window in which the player can pause so that the leader still takes the damage, but the cutscene doesn't start. By choosing to quit out, the game queues both the "leader is down" cutscene and the "escape the cave" command, and because this is a scenario that should never happen, the game stays in a semi-frozen state to prepare for the cave escape cutscene, where some things, like carrying, don't work.

{{glitch | reproducibility = Low | consequences = Harmless | p2 = Yes | npcp2 = Yes

| howto = Go to a sublevel that looks like an outside area (such as sublevel 2 of the [[Snagret Hole]] or the [[Brawl Yard]]), and have an enemy push you close to the boundary while you push into the same boundary. If done right, you will be flung to the outside of the walls and can explore out of bounds. The easiest way to do it is to use the [[Sniper Room]], and finding the [[Orange Bulborb]] in a dead end, if it's there. Go on the boundary of the dead end, push through, and let the Bulborb bite you. It works a lot better if you time a press of {{button|gc|x|wii|c}} so that the leader [[lie down|lies down]] just as the creature takes a bite.

| notes = If you go far enough away from the main part of the level, you will hit a massive wall with blurry images of trees and foliage painted on it, or in other cases an invisible barrier. Throwing Pikmin at this barrier will make them float in place for a while before falling to the ground.{{cite youtube|MnYc8FzIF3A|with the boundaries glitch, showing what happens to Pikmin thrown at the invisible wall}}

===Lockout skip===

{{glitch | reproducibility = Medium | consequences = Depends | p2 = Yes | npcp2 = ? | demonstration = [https://clips.twitch.tv/AttractivePrettyPhoneFloof Twitch clip] | other = [https://clips.twitch.tv/ChillyRealCarabeefTF2John Skipping the burning Pikmin cutscene]

| effects = Makes it possible to skip the partial control lockout that happens after a cutscene. In particular, when the player collects the final treasure in a sublevel and wants to enter the hole for the next sublevel, this can be used to skip the control lockout that stops the player from pressing {{button|gc|a|wii|a}} next to the hole, right after the treasure cutscene ends. This glitch can also be used with other cutscenes, like the one that plays when the first enemy is delivered to the Research Pod.

| howto = Right as a treasure is being delivered to the Research Pod, press {{button|gc|a|wii|a}} in front of the next sublevel's hole to interact with it. The screen should fade out due to the treasure's delivery, but the game will right afterwards ask if you want to delve deeper in the cave. If you say yes, the game will then continue from the treasure cutscene, and afterwards, the cutscene where the leaders and Pikmin dive inside the hole will take place, with no interval between.

| notes = At the end of the cave, the treasures that were used for this glitch will not be present on the tally, even though they will be considered collected and the all treasures ending can be achieved even if the glitch is used. In addition, because the treasures aren't tallied, the game won't consider that cave complete, which means the player can save time by not having to see the small cave completion celebration. To note however is that the player will not be given the Poko value for the treasures or objects involved with the glitch, and that there is the potential risk of the game freezing.{{cite web|https://clips.twitch.tv/SucculentOpenTermitePrimeMe|Twitch clip|Twitch}} Furthermore, it's worth mentioning that if the player pauses and escapes the cave after performing this glitch, the treasure will still count as collected, and will not reappear.

| explanation = Starting the two events at once makes the game go through both of them right away, effectively skipping the small interval where the player is locked out from interacting with the hole. Because the game is in a non-expected state when the treasure is actually recovered, the entire process of registering its collection doesn't go through.

{{glitch | reproducibility = Low | consequences = Harmless | p2 = Yes | npcp2 = ? | demonstration = [http://en.niconico.sarashi.com/?sm6552944 Video on Niconico Douga]

| explanation = The randomly generated mazes have complex algorithms, in order to create lively and balanced labyrinths. This complexity can sometimes cause minor problems, like having a gate protrude from a wall. Because from the other side of the wall, the gate is still a normal "gate" object, it can also be targeted and hit by Pikmin.

 

 

{{glitch | reproducibility = Low | consequences = Harmful | p2 = Yes | npcp2 = Yes | image = P2 Activity arouser tilt.jpg

| effects = Makes some objects become tilted. Can sometimes cause the object to fall through the map.