Unused content in Pikmin 2: Difference between revisions

Fixed the translation.
(Fixed the translation.)
 
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{page title|Unused content in ''Pikmin 2''}}{{game icons|p2=y}}
{{page title|Unused content in ''Pikmin 2''}}
{{game icons|p2=y}}
{{external|unused content in ''Pikmin 2''|[http://tcrf.net/Pikmin_2 The Cutting Room Floor]|TCRF logo.png}}
{{external|unused content in ''Pikmin 2''|[http://tcrf.net/Pikmin_2 The Cutting Room Floor]|TCRF logo.png}}
{{stub}}
{{stub}}
Line 23: Line 24:
There are two unused title screen logos.
There are two unused title screen logos.
<gallery>
<gallery>
Pikmin2BetaJ.png|The word "{{j|ピクミン|Pikkumin}}", in blue chrome.
Pikmin2BetaJ.png|The word "{{j|ピクミン|Pikumin}}", in blue chrome.
Pikmin2BetaE.png|A blue, electrified "Pikmin2".
Pikmin2BetaE.png|A blue, electrified "Pikmin2".
</gallery>
</gallery>
Line 127: Line 128:


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


<code>
<code>
Line 141: Line 142:
</code>
</code>


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


<code>
<code>
Line 147: Line 148:
</code>
</code>


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


<code>
<code>
Line 325: Line 326:
P2CU_room_queen_c_tsuchi.jpg|<code>room_queen_c_tsuchi</code>: Naming order in conjunction with <code>room_queen_b_tsuchi</code> implies the existence of <code>room_queen_a_tsuchi</code> but that unit does not exist.
P2CU_room_queen_c_tsuchi.jpg|<code>room_queen_c_tsuchi</code>: Naming order in conjunction with <code>room_queen_b_tsuchi</code> implies the existence of <code>room_queen_a_tsuchi</code> but that unit does not exist.
</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.


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 418: 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 family|Candypop Buds]] 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 Bud]]s 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.


Anonymous user