Cave generation parameters

In Pikmin 2, the files that define a cave's settings can be found in /user/Mukki/mapunits/caveinfo. For instance, the Emergence Cave uses tutorial_1.txt. All comments (Japanese or English statements followed by a #) are unnecessary and deleting them will save file space.

These text files must be encoded in Shift-JIS, or at least ASCII. If the file is saved as a UTF-8 text file with the EF BB BF magic word at the start, the game will not read it correctly, assuming you only have one sublevel. To avoid any issues, use Notepad++ and check the encoding in the bottom right.

Header

Each file starts with a simple block titled CaveInfo. It contains only one parameter, {c000}, which takes two values, a 4 and the number of sublevels in the cave.

After the opening block, there is a lone number. This number is, once again, the number of sublevels in the cave. After this comes a series of blocks, with each group of 5 belonging to a sublevel.

Sublevel

Each sublevel starts with a block commented with FloorInfo, where the sublevel's data is, and then four blocks that determine what objects to spawn. The process is explained in the sections for these blocks, but the general algorithm is also explained here.

The comment for the first sublevel's FloorInfo block has a number to the left of it; this is the total number of sublevels).

Object categories

Before you continue, it is important to know that objects can belong to one of five categories:

1. "Main"
   • Are defined in TekiInfo.
   • Are not treasures.
   • Are not gates.
   • Appear inside "room" units.
   • Their "type" is not "6".
2. "Decorative"
   • Same rules as the "main" category, except...
   • Their "type" is "6".
3. Dead end
   • Are defined in CapInfo.
   • Are not gates.
   • Appear inside "dead end" units.
4. Treasure
   • Are defined in ItemInfo.
   • Are exclusively treasures.
5. Gate
   • Are defined in GateInfo.
   • Are exclusively gates.

These category names are not laws, just guidelines. This is because you can have fully-functional enemies in the "decorative" category, and you can have cosmetic plants in the "main" category, for instance. What is important is understanding that the game reads objects in different categories differently, and also controls them differently.

FloorInfo

This block has a large number of parameters that determine how the sublevel works. All content in these parameters consist of two words. The first word is a number, 4 for numbers and -1 for strings. The second word is the actual value of the parameter - the one you can modify.

To do: Figure out what happens if you change {f000} and {f001}.

Parameter	Description	Japanese comment
{f000}	The sublevel number this sublevel belongs to, minus 1. For example, if this floor is sublevel 1, the value is 0. Comment translates to "floor introduction". Seems to crash the game if lower than the current sublevel.	階はじめ
{f001}	Same as above. Comment translates to "floor end". Seems to duplicate the floor and replace future sublevels. For example, if you are on sublevel 1 ({f000} is set to 0) when {f001} is set to 2, sublevels 2 and 3 will be the exact same as the first sublevel. The other sublevels will be untouched.	階おわり
{f002}	Ideal maximum number of objects in the "main" category. See #Amount for more details. If this is set to 0, absolutely no objects of the "main" category will spawn.	敵最大数
{f003}	Ideal maximum number of objects in the treasure category.	アイテム最大数
{f004}	Ideal maximum number of objects in the gate category.	ゲート最大数
{f005}	Number of "room" cave units.	ルーム数
{f006}	Corridor probability. If this number is higher, the game will spawn more corridors relative to the number of rooms.	ルートの割合
{f007}	1 if this floor has a geyser, 0 otherwise.	帰還噴水(1=あり)
{f008}	Cave unit definition file name.	使用ユニット
{f009}	Lighting definition file name.	使用ライト
{f00A}	Skybox. Valid values are: none, f010, vrbox (they all mean none), ice (ice cavern), test (cavern), build (steel), hiroba (garden), flooring (wooden floor), tatami (carpet).	VRBOX
{f010}	1 if the next sublevel hole is clogged, 0 otherwise.	階段を壊す岩で隠す(0=オフ 1=オン)
{f011}	Echo strength; 0 for longest echo, used in soil/remaining themes, 1 is normally used for metal, 2 is used for concrete, 3 is used for tile, 4 is used for garden, and 5 is an almost unnoticeable echo, used for toy themes.	α属性
{f012}	Music type; 0 for normal, 1 to mute (until a boss), 2 to use rest sublevel music	β属性
{f013}	1 if sublevel has an invisible solid plane of ground, generally used for the hiroba, flooring and tatami skyboxes. If 0, Pikmin can fall off the edge to their deaths.	隠し床
{f014}	Cap probability (0-100). E.g. if this value is 50, open doors will be set to alcoves with 50% probability.	キャップ最大数
{f015}	File format version; 1 is normal, 0 will ignore all dead end spawns (#CapInfo)	Version
{f016}	Time until the Waterwraith appears.	BlackManTimer
{f017}	0 is normal, anything else makes it spawn two (connected) seesaw blocks randomly in the level. May spawn the leaders and Pikmin inside one. Unused.	沈む壁

TekiInfo

TekiInfo determines the "main" objects and the "decorative" objects to spawn on the sublevel.

The first number in the block is the total of entries. It is commented with num. Each entry consists of two lines. The first line in an entry determines how it spawns, the object's class, what treasure it has inside, how many to spawn, and/or how likely this object is to be used to fill the free "main" object slots. The second line of each entry is the "type" of the object.

To note is that if something is wrong with the object's spawn data, the game will probably break down, but it might also trigger an error handler. If it does, the object is turned into a fully-functional Common Glowcap. Typing an invalid class name will trigger the error handler.

Class

The first word in the first line of each entry contains the object class (fire geyser, Red Bulborb, clover, etc.), using its internal name (case insensitive). Treasures will not work; use the ItemInfo block for that.

If it is an enemy and is carrying something inside it, the internal name of that object's class is also included in that word, in lowercase, after an underscore (e.g. Chappy_key for a Red Bulborb carrying The Key). In this case, the name of the enemy itself is no longer case insensitive and must be written in CamelCase, although exact casing depends on the object. Note that an underscore isn't a sure-fire way to know that one object is carrying another. If the game sees the name Wakame_s, it isn't going to think that it's an object Wakame carrying an object s, but rather that it is a small Shoot.

Spawn method

Some objects spawn from the sky, like Volatile Dweevils that only appear when you get close to their spawn position. To get an object to do this, write a dollar sign and/or a number before the name of the object, without a space in between. Example: $4BombOtakara. You have to write a specific thing to get a specific behavior, and if you write an invalid one, the game crashes:

Code	Effect	Notes
$	Always fall if a Pikmin or leader is nearby.
$0	Triggers the Common Glowcap error handler.	Unused.
$1	Identical to $.
$2	Only fall if a Pikmin is nearby, leaders are ignored.
$3	Only fall if a leader is nearby, Pikmin are ignored.	Unused.
$4	Only fall if Pikmin are carrying nearby.
$5	Only fall if a Purple causes an earthquake nearby.

Not all objects support this feature. The objects that don't support the feature completely ignore the $ sign and spawn normally. No bosses or plants (besides Candypop Buds) are changed.

Here is a list of all other known objects and whether or not they are capable of using this behavior.

Enemy	Supported	Notes
Anode Beetle	Yes
Anode Dweevil	Yes
Antenna Beetle	No
Armored Cannon Beetle Larva (Buried)	No
Armored Cannon Beetle Larva (Free)	Yes
Bomb-rock	Yes
Breadbug	No
Bulbmin	Yes
Bulborb Larva	Yes	Uses a unique falling animation, the same animation thats used when they are born from the Empress Bulblax.
Bumbling Snitchbug	Yes	Floats down from the sky.
Careening Dirigibug	Yes	Floats down from the sky.
Caustic Dweevil	Yes
Cloaking Burrow-nit	No
Creeping Chrysanthemum	No
Crimson Candypop Bud	Yes
Decorated Cannon Beetle	Yes
Doodlebug	No
Dwarf Bulbear	Yes
Dwarf Orange Bulborb	Yes
Dwarf Red Bulborb	Yes
Egg	Yes	Breaks upon hitting the ground.
Electrical Wire	No
Falling Boulder	Yes	Falling boulders sort of float in place for a bit, then fall down at a much quicker speed than normal. If multiple boulders spawn inside of each other, they will bounce off of each other at an angle when they are triggered by the player.
Female Sheargrub	No
Fiery Blowhog	Yes
Fiery Bulblax	Yes
Fiery Dweevil	Yes
Fire Geyser	No
Foxtail	No
Gas Pipe	No
Gatling Groink (Both variants)	Yes
Golden Candypop Bud	Yes
Greater Spotted Jellyfloat	Yes	Floats down from the sky.
Hairy Bulborb	Yes
Hermit Crawmad	No
Honeywisp	No
Iridescent Flint Beetle	No
Iridescent Glint Beetle	No
Ivory Candypop Bud	Yes
Lapis Lazuli Candypop Bud	Yes
Lesser Spotted Jellyfloat	Yes	Floats down from the sky
Lithopod Boulder (Unused)	Yes	The trail particles of the boulder will remain stationary in the air until the rolling boulder is triggered by the player.
Male Sheargrub	No
Mamuta	No
Mitite	No
Munge Dweevil	Yes
Orange Bulborb	Yes
Puffy Blowhog	Yes	Floats down from the sky.
Queen Candypop Bud	Yes
Ravenous Whiskerpillar	No
Red Bulborb	Yes
Shearwig	No
Skitter Leaf	No
Snow Bulborb	Yes
Spotty Bulbear	Yes
Swooping Snitchbug	Yes	Floats down from the sky.
Toady Bloyster	No
Unmarked Spectralids	No
Violet Candypop Bud	Yes
Volatile Dweevil	Yes
Water Dumple	Yes
Waterwraith Rollers (Unused)	No
Watery Blowhog	Yes
Withering Blowhog	Yes	Floats down from the sky.
Wogpole	Yes
Wollywog	Yes
Yellow Wollywog	Yes

Amount

"Main" category objects

The second word in the first line of each entry is a number, where the last digit is the filler distribution weight and the other digits are the minimum amount to spawn. This line is commented with weight. If there is only one digit, it indicates the filler distribution weight, and the minimum amount is set to 0.

The game will spawn the enemies requested in the "minimum amount" fields (provided there is enough physical space in the sublevel). After the game is done spawning all of these, provided that the enemy total isn't equal to or over {f002} yet, it will then try to fill in the remaining slots with any enemies that have a non-zero filler distribution weight, as explained here. If there are no enemies to pick for the filler distribution, then the game simply doesn't spawn any fillers. [Note from JHawk - I think this is slightly inaccurate. The game first counts the "minimum amounts" for enemies of type 0, 1, 5, and 8. Then, for each additional remaining main enemy slot not covered by the minimum amounts, the game will sum the weights of the type 0, 1, 5, and 8 enemies and allocate an additional slot for that enemy type one at a time with probability in proportion to that weight.]

Note that when trying to spawn an enemy, if there are no more vacant slots of the specified type, the game will not spawn that enemy, but will still add 1 to the counter of enemies currently in the sublevel. This means that if you have a cave with just one room, that has 4 spawn locations for type 0 and 4 for type 1, you specify 10 as the maximum of enemies ({f002}), and specify 8 Wogpoles of type 0, and then a Dwarf Red Bulborb with a filler distribution weight and type 1, the game will try to spawn the 8 mandatory Wogpoles, only spawn 4 because there are no more vacant slots, and will still count the other 4 as if they exist. This means it will only pick 2 Dwarf Red Bulborbs to reach the maximum in {f002}.

Credits: Jimble, Espyo

"Decorative" category objects

The second word in the first line of each entry is a number, which indicates the exact number of objects of that type to spawn. There are no limits to the number of objects of this type to spawn, except for the amount of spawning locations available in the sublevel's generated layout, and there is no random distribution either.

Credits: Jimble, Espyo

Type

This number controls what type of object this is (more or less), and where it spawns. The number ranges from 0 to 8, and most also correspond to a group of spawn coordinates. When spawning an instance of this object, the game picks a random coordinate from the group, if applicable.

The type is defined in the second line of each entry, and is commented with type. The following table lists the possible numbers, and the comments on the various unit layout files (in /user/Mukki/mapunits/arc/*/texts.szs/layout.txt) are also included due to them helping understand what each number means. Also note that objects in some categories cannot use some numbers, and that objects in the treasure and gate categories cannot specify a type.

Group	Content	layout.txt comment	Notes	Category availability
				"Main"	"Decorative"	Dead end
0	Enemy Group A	Teki A		Yes	No	Yes
1	Enemy Group B	Teki B		Yes	No	Yes
2	Treasure	Item	Not used by any object in the canon game. In a cave unit, it marks the location of objects defined in CapInfo.	No	No	Yes
3	Unknown[unsure]		There is no object or cave unit that uses this number.	No	No	No
4	Hole/Geyser	FixObj	Objects can't use this number. In a cave unit, it marks a viable location for the next hole/geyser in a room, if dead ends are not present in the sublevel.	No	No	No
5	Seams		Commonly used for hazards such as fire geysers, electrical wires and gas pipes. These spots are located in the seams between two connecting cave units.	Yes	No	Yes
6	Plant	Plant	Commonly used by decorative plants.	Yes	Yes	Yes
7	Leader spawn	Start	Objects can't use this number. In a cave unit, it marks a possible player starting spot in the sublevel. The Y coordinate is ignored; it snaps to the ground.	No	No	No
8	Enemy Group C	Teki F	Commonly used for boss locations, or the location of tower Gatling Groinks/buried Armored Cannon Beetle Larvae. Most rooms do not have coordinates for this.	Yes	No	Yes

Example

	{f002} 4 5 	# 敵最大数

(...)

# TekiInfo
{
	2 	# num
	$Tadpole 23 	# weight
	0 	# type
	Sokkuri_bane 9 	# weight
	1 	# type
}

Assuming there's enough space in the sublevel, this would make the game spawn 2 Wogpoles, that only pop up from the sky when you get close. Then, it spawns 3 randomly picked enemies, with each enemy having a 3/12 chance of being a Wogpole (like the aforementioned ones, these spawn from the sky), and a 9/12 chance of being a Skitter Leaf that is carrying a Coiled Launcher. Any Wogpole in this sublevel will spawn in the set of coordinates that belong to group 0, whereas any Skitter Leaf will spawn on the coordinates of group 1.

ItemInfo

The next block is titled ItemInfo. It controls how treasures spawn. Treasures inside enemies aren't included here, but are instead defined in TekiInfo or CapInfo's objects.

The first number in the block is the total of entries. It is titled num. Each entry consists of one line. This line contains the internal name of the treasure, in all lowercase, and then after a space, the amount to spawn. This amount uses the same scheme as the TekiInfo block, except when deciding the random spawn distribution, the limit is decided by {f003} instead. If you try to spawn something here that is not a treasure, the game will crash.

Example

	{f003} 4 4

(...)

# ItemInfo
{
	3
	key 10
	gold_medal 12
	saru_head 04
}

The game will spawn one The Key and one Lustrous Element, the next two treasures (because {f003} is set to 4), will have a 2/6 chance of being a Lustrous Element, and a 4/6 chance of being a Colossal Fossil.

GateInfo

GateInfo controls what gates will appear. Each individual gate on a sublevel is randomly colored. The game will spawn the number of gates defined in {f004}, but will stop spawning them if there isn't enough room.

The first number in the block is the total of entries. It is titled num.

1. Each entry consists of two lines.
2. The first line is the gate's HP. It is titled with life. This line starts with any word (although the word gate is what's used in the vanilla game), and after a space, the amount of hit points it has, with decimal places (e.g. 1000.000000).
3. The second line is the spawn distribution weight. Only the last digit of this number is used.^[unsure] If the number is 0, this type of gate will not spawn at all, of course.

Example

	{f004} 4 2

(...)

# GateInfo
{
	2
	gate 4000.000000
	1
	gate 2500.000000
	1
}

This will spawn two different types of gates of random colours in random locations. The total number of gates appearing in the level is dependent on the value set in {f004}, which in this case is 2 so only two gates will spawn.

CapInfo

CapInfo determines what objects to spawn in dead ends. It works similarly to the TekiInfo block, though with some differences.

The first number in the block is the total number of entries. It is titled num. Each entry consists of three lines:

1. The first line is presumably, the type of dead end this spawn applies to. It always has the value 0, and is typically commented with the word "captype".
2. The second line is the amount, and works just like the TekiInfo block, except there's no special parsing if "type" is 6. This line is typically commented with the word "weight".
3. The third line is the "type", and it can either be 0 or 1. 0 allows up to two enemies to spawn per dead end, while type 1 allows only 1 enemy per dead end. This line is typically commented with the word "type".

Other than that, note the following:

• While in the TekiInfo block the locations of objects spawned is determined by the "type", that is not the case here. These objects always spawn in dead ends.
• Objects spawned with this block do not count for any limit (e.g. {f002}).
• Treasures can also be specified in this block.

Example

# CapInfo
{
	2
	0
	$2Egg 10
	1
	0
	WhitePom 10
	1
}

This will spawn an egg that will fall down when a Pikmin gets close, and an Ivory Candypop Bud, both in random dead-ends.