Editing Unused content 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 1: | Line 1: | ||
{{ | {{DISPLAYTITLE:Unused content in ''Pikmin 2''}}{{game icons|p2=y}} | ||
{{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 24: | Line 23: | ||
There are two unused title screen logos. | There are two unused title screen logos. | ||
<gallery> | <gallery> | ||
Pikmin2BetaJ.png|The word "{{j|ピクミン| | Pikmin2BetaJ.png|The word "{{j|ピクミン|Pikkumin}}", in blue chrome. | ||
Pikmin2BetaE.png|A blue, electrified "Pikmin2". | Pikmin2BetaE.png|A blue, electrified "Pikmin2". | ||
</gallery> | </gallery> | ||
Line 46: | Line 45: | ||
[[File:Pikmin2WaterwraithDummy.png|left|thumb]] | [[File:Pikmin2WaterwraithDummy.png|left|thumb]] | ||
There is a dummy texture in the [[Waterwraith]]'s model. Its look is created with frame buffer shaders, meaning that this underlying texture is not usually seen. | There is a dummy texture in the [[Waterwraith]]'s model. Its look is created with frame buffer shaders, meaning that this underlying texture is not usually seen. | ||
{{clear}} | {{clear}} | ||
Line 93: | Line 82: | ||
== Unused text== | == Unused text== | ||
=== readme.txt === | === readme.txt === | ||
A unused <code>readme.txt</code> found in <code>/user/Abe/map/newtest/nonloop</code> indicates that the layout files for [[newtest]] found in the same directory as the file likely specify which enemies are to spawn in certain areas. | |||
Curiously, <code>2-2.txt</code> specifies that an enemy with the ID of <code>39</code> would spawn in the [[Awakening Wood]]. Attempting to spawn the enemy with the ID of 39 crashes the game, as it does not exist. Additionally, the file for the [[Perplexing Pool]], <code>3-3.txt</code> is absent. All of the objects placed in these layouts are in sloppy rows, so they are not early layouts of areas. It is unclear which of the enemies listed spawned in caves or the overworld. | Curiously, <code>2-2.txt</code> specifies that an enemy with the ID of <code>39</code> would spawn in the [[Awakening Wood]]. Attempting to spawn the enemy with the ID of 39 crashes the game, as it does not exist. Additionally, the file for the [[Perplexing Pool]], <code>3-3.txt</code> is absent. All of the objects placed in these layouts are in sloppy rows, so they are not early layouts of areas. It is unclear which of the enemies listed spawned in caves or the overworld. | ||
Line 129: | Line 118: | ||
=== Test messages === | === Test messages === | ||
Unused text, | Unused text, apparently test messages. The last seven messages appear to be titles of unknown test areas in radar screens, as the title shown for [[newtest]] in the radar is "Test Area (ID 8394_03)". | ||
<code> | <code> | ||
Line 141: | Line 130: | ||
Oh! no! | Oh! no! | ||
MOC = Mouse on Cars! | MOC = Mouse on Cars! | ||
go to hell! | go to hell! | ||
Under Construction (ID9999) | Under Construction (ID9999) | ||
Line 298: | Line 274: | ||
<gallery> | <gallery> | ||
P2CU_room_houdai2_1_metal.jpg|'''room_houdai2_1_metal''': 6 exit points. | File:P2CU_room_houdai2_1_metal.jpg|'''room_houdai2_1_metal''': 6 exit points. | ||
P2CU_room_houdai_1_metal.jpg|'''room_houdai_1_metal''': 1 exit point. | File:P2CU_room_houdai_1_metal.jpg|'''room_houdai_1_metal''': 1 exit point. | ||
P2CU_room_ike4_5_tsuchi.jpg|'''room_ike4_5_tsuchi''': 5 exit points. | File:P2CU_room_ike4_5_tsuchi.jpg|'''room_ike4_5_tsuchi''': 5 exit points. | ||
P2CU_room_kingchp_tsuchi.jpg|'''room_kingchp_tsuchi''': 3 exit points. | File:P2CU_room_kingchp_tsuchi.jpg|'''room_kingchp_tsuchi''': 3 exit points. | ||
P2CU_room_queen_c_tsuchi.jpg|'''room_queen_c_tsuchi''': 1 exit point. | File:P2CU_room_queen_c_tsuchi.jpg|'''room_queen_c_tsuchi''': 1 exit point. | ||
P2CU_room_hitode6x6_3_toy.jpg|'''room_hitode6x6_3_toy''': 3 exit points. | File:P2CU_room_hitode6x6_3_toy.jpg|'''room_hitode6x6_3_toy''': 3 exit points. | ||
P2CU_room_large_7_toy.jpg|'''room_large_7_toy''': 7 exit points. | File:P2CU_room_large_7_toy.jpg|'''room_large_7_toy''': 7 exit points. | ||
P2CU_room_mid_tower2_8_toy.jpg|'''room_mid_tower2_8_toy''': 8 exit points. | File:P2CU_room_mid_tower2_8_toy.jpg|'''room_mid_tower2_8_toy''': 8 exit points. | ||
P2CU_room_mid_tower_8_toy.jpg|'''room_mid_tower_8_toy''': 8 exit points. | File:P2CU_room_mid_tower_8_toy.jpg|'''room_mid_tower_8_toy''': 8 exit points. | ||
</gallery> | </gallery> | ||
Of special note is the last sublevel of the [[Dream Den]], which can actually show randomization in the sublevel visuals, since there are two different dead-end units that can be used for that sublevel. Normally, all of the player's attention gets diverted to defeating the [[Titan Dweevil]], carrying back the treasures, and exiting the cave, instead of the type of dead-end unit used when the sublevel was generated. | Of special note is the last sublevel of the [[Dream Den]], which can actually show randomization in the sublevel visuals, since there are two different dead-end units that can be used for that sublevel. Normally, all of the player's attention gets diverted to defeating the [[Titan Dweevil]], carrying back the treasures, and exiting the cave, instead of the type of dead-end unit used when the sublevel was generated. | ||
==Unused lighting== | ==Unused lighting== | ||
Line 409: | Line 364: | ||
== Other == | == Other == | ||
* There's a texture of what appears to be the top of a drain pipe clogged with grease surrounded by tile textures. This texture 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 obscured and distorted by a water texture 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 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 378: | ||
* [[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 | * 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 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. | ||