Editing Unused content 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 24: Line 24:
There are two unused title screen logos.
There are two unused title screen logos.
<gallery>
<gallery>
Pikmin2BetaJ.png|The word "{{j|ピクミン|Pikumin}}", in blue chrome.
Pikmin2BetaJ.png|The word "{{j|ピクミン|Pikkumin}}", in blue chrome.
Pikmin2BetaE.png|A blue, electrified "Pikmin2".
Pikmin2BetaE.png|A blue, electrified "Pikmin2".
</gallery>
</gallery>
Line 55: Line 55:
The bottom part of this texture, resembling a drain pipe clogged with grease, is located under the [[Shower Room]]'s entrance, but it cannot be fully seen because the cave entrance covers most of the texture. It can be seen in the Piklopedia in the same spot, but even then it's warped by the water texture above it and the Piklopedia's bloom filter; not to mention that the level model is actually [[Piklopedia (Pikmin 2)#Areas|an almost completely different model]].
The bottom part of this texture, resembling a drain pipe clogged with grease, is located under the [[Shower Room]]'s entrance, but it cannot be fully seen because the cave entrance covers most of the texture. It can be seen in the Piklopedia in the same spot, but even then it's warped by the water texture above it and the Piklopedia's bloom filter; not to mention that the level model is actually [[Piklopedia (Pikmin 2)#Areas|an almost completely different model]].


The top part of this texture is seen on the chipped parts of concrete/tile in the same area, but only portions of it can be seen at a time. In the two cases where it's facing upwards, the middle section is normally covered by a metal pipe, and for the chipped concrete at the landing site, the surrounding tile part is not visible. In the other case when it's used in the crack in the Shower Room's entrance, only a quarter of it is used, and part of it's at an extremely narrow slant, making it hard to look at clearly.
The top part of this texture is seen on the chipped parts of concrete/tile in the same area, but only portions of it can be seen at a time. In the two cases where it's facing upwards, the middle section is normally covered by a metal pipe. In the other case when it's used in the crack in the Shower Room's entrance, only a quarter of it is used, and part of it's at an extremely narrow slant, making it hard to look at clearly.


{{clear}}
{{clear}}
== Unused maps ==
== Unused maps ==
There is a single unused level in ''Pikmin 2'', titled [[newtest]]. It has a Piklopedia version in another file, which is missing the section of the map with footstep sounds. It has multiple unused layouts in <code>/user/Abe/map/newtest/nonloop</code>, three of which specify enemies that are planned to spawn in certain areas, as dictated by a "readme" file found in the same directory. It seems to be a test map, based on its title and its contents, which include organized slopes, water, and clusters of enemies and objects. It overall has a basic, flat garden environment similar to the [[Perplexing Pool]].
There is a single unused level in ''Pikmin 2'', titled [[newtest]]. It has a Piklopedia version in another file, which is missing the section of the map with footstep sounds. It has multiple unused layouts in <code>/user/Abe/map/newtest/nonloop</code>, three of which specify enemies that are planned to spawn in certain areas, as dictated by a "readme" file found in the same directory. It seems to be a test map, based on its title and its contents, which include organized slopes, water, and clusters of enemies and objects. It overall has a basic, flat garden environment similar to the [[Perplexing Pool]].
Line 129: Line 128:


=== Test messages ===
=== Test messages ===
Unused text, most of which appears to be test messages and debugging text.
Unused text, most of which appear to be test messages and debugging text.


<code>
<code>
Line 143: Line 142:
</code>
</code>


The following error message fires under certain conditions in the [[area selection menu]]'s code. Its meaning is unknown; it likely refers to a development in-joke.
The following error message fires under certain conditions in the world map screen's code. Its meaning is unknown; it likely refers to a development in-joke.


<code>
<code>
Line 149: Line 148:
</code>
</code>


The following error message fires under certain conditions in <code>sysShape</code> (usually when the game crashes), which is an internal manager related to preloading and setting up models in ''Pikmin 2''.
The following error message fires under certain conditions in <code>sysShape</code>(usually when it crashes), which is an internal manager related to preloading and setting up models in ''Pikmin 2.''


<code>
<code>
Line 328: Line 327:
</gallery>
</gallery>


While there are "4x4" layout IDs for letters of the alphabet up until O, there is no "4x4n" or "4x4m" shape that exists. A cave unit with a "3x4n" layout ID does exist, however, but the cave unit that uses that shape is the only lettered 3x4 cave unit. There is also a "3x3m" ID that is used in the snow and concrete sets, but that ID too is the only lettered 3x3 ID.
While there are "4x4" layout ID's for letters of the alphabet up until O, there is no "4x4n" or "4x4m" shape that exists. A cave unit with a "3x4n" layout ID does exist, however, but the cave unit that uses that shape is the only lettered 3x4 cave unit. There is also a "3x3m" ID that is used in the snow and concrete sets, but that ID too is the only lettered 3x3 ID.


Of special note is <code>room_boss_1_tsuchi</code> and <code>room_hebi12x12_1_tsuchi</code>; the ends of both units differ in texture from the rest of the unit, suggesting that the cave unit originally had an exit in line with their internal names, but then later had a dead end unit stitched onto the model.
Of special note is <code>room_boss_1_tsuchi</code> and <code>room_hebi12x12_1_tsuchi</code>; the ends of both units differ in texture from the rest of the unit, suggesting that the cave unit originally had an exit in line with their internal names, but then later had a dead end unit stitched onto the model.
Line 409: Line 408:


== Other ==
== Other ==
{{todo|1=Research [https://www.youtube.com/watch?v=udjUheeqSTc this] better.}}
* The text in the opening video is overlaid on top of the actual video in ''Pikmin 2'', leaving a small fraction of pixels in the video unused. Video without the text [https://www.youtube.com/watch?v=D1Rx5QNuMt8 here].
* The text in the opening video is overlaid on top of the actual video in ''Pikmin 2'', leaving a small fraction of pixels in the video unused. Video without the text [https://www.youtube.com/watch?v=D1Rx5QNuMt8 here].
* There is a unused feature for [[electrical wire]]s in [[2-Player Battle]] to change color and element based on the Pikmin attacking it; Red Pikmin turn the electric wire's lighting red and set Blue Pikmin on fire, while Blue Pikmin turn the electric wire's lighting blue and apply the drowning effect to Red Pikmin. This also causes them to constantly be on and never turn off.
* There is a unused feature for [[electrical wire]]s in [[2-Player Battle]] to change color and element based on the Pikmin attacking it; Red Pikmin turn the electric wire's lighting red and set Blue Pikmin on fire, while Blue Pikmin turn the electric wire's lighting blue and apply the drowning effect to Red Pikmin. This also causes them to constantly be on and never turn off.
Line 424: Line 421:
* [[Unmarked Spectralids]] have 200 health points but die on one hit. Likewise, [[Honeywisps]] have 99999 health points but also die in one hit.
* [[Unmarked Spectralids]] have 200 health points but die on one hit. Likewise, [[Honeywisps]] have 99999 health points but also die in one hit.
* In ''Pikmin'', there is an unused feature that makes Pikmin get [[throw]]n higher the longer the Pikmin is held. This feature has no effect on gameplay since the normal height values and the "fully charged" height values are the same. In ''Pikmin 2'', these values still exist, and are still the same for the normal and full charge amount, but the code for the feature itself has been removed.
* In ''Pikmin'', there is an unused feature that makes Pikmin get [[throw]]n higher the longer the Pikmin is held. This feature has no effect on gameplay since the normal height values and the "fully charged" height values are the same. In ''Pikmin 2'', these values still exist, and are still the same for the normal and full charge amount, but the code for the feature itself has been removed.
* Enemies in ''Pikmin 2'' have set ID numbers, and are spawned using the ID number that is assigned to the enemy. Four of these numbers, <code>39</code>, <code>64</code>, <code>82</code>, and <code>100</code> are never used; they crash the game when spawned. This is because the files for <code>39</code> and <code>64</code> were deleted, and ID numbers <code>82</code> (internally, <code>Pom</code>) and <code>100</code> (internally, <code>UmiMushiBase</code>) appear to be template files for variants of [[Candypop Bud]]s and enemies in the [[mollusking family]], respectively.
* Enemies in ''Pikmin 2'' have set ID numbers, and are spawned using the ID number that is assigned to the enemy. Four of these numbers, <code>39</code>, <code>64</code>, <code>82</code>, and <code>100</code> are never used; they crash the game when spawned. This is because the files for <code>39</code> and <code>64</code> were deleted, and ID numbers <code>82</code> (internally, <code>Pom</code>) and <code>100</code> (internally, <code>UmiMushiBase</code>) appear to be template files for variants of [[Candypop family|Candypop Buds]] and enemies in the [[mollusking family]], respectively.
** Interestingly, <code>82</code> appears after all of the ID numbers for the specific Candypop Buds, which are numbers <code>3</code> through <code>8</code>. The ID number for the [[Ranging Bloyster]] appears much later in the list as <code>71</code> (internally, <code>UmiMushi</code>) while the ID for [[Toady Bloyster]] is <code>101</code> (internally, <code>UmiMushiBlind</code>), so it's possible that some of the ID numbers shifted around during development. Additionally, the enemy that has the ID of <code>39</code> is set to spawn in a unused layout file for [[newtest]] and is referred to as "{{j|フエフキムシ|Fuefukimushi|Flute Player Bug}}" in comments, which is similar to the [[Antenna Beetle]]'s internal name. This enemy would be able to spawn in the [[Awakening Wood]] as dictated by a <code>readme.txt</code> file found in the same directory.
** Interestingly, <code>82</code> appears after all of the ID numbers for the specific Candypop Buds, which are numbers <code>3</code> through <code>8</code>. The ID number for the [[Ranging Bloyster]] appears much later in the list as <code>71</code> (internally, <code>UmiMushi</code>) while the ID for [[Toady Bloyster]] is <code>101</code> (internally, <code>UmiMushiBlind</code>), so it's possible that some of the ID numbers shifted around during development. Additionally, the enemy that has the ID of <code>39</code> is set to spawn in a unused layout file for [[newtest]] and is referred to as "{{j|フエフキムシ|Fuefukimushi|Flute Player Bug}}" in comments, which is similar to the [[Antenna Beetle]]'s internal name. This enemy would be able to spawn in the [[Awakening Wood]] as dictated by a <code>readme.txt</code> file found in the same directory.


Please note that all contributions to Pikipedia are considered to be released under the Attribution-ShareAlike 4.0 International 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)

This page is a member of 2 meta categories: