Pikmin Technical Knowledge Base - User contributions [en]

Enemy Parameters

2026-05-08T00:35:44Z

Atyfaz: /* Individual Drop Chances vs Cumulative Chances */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====dropOption====

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, Mitites, and Honeywisp, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. This behavior occurs when dropOption is set to 1. To change that behavior to what most enemies use by default, change dropOption to 6.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|-
| Glow Pellet Pile || -4985278700699515859
|-
| Unknown found in GHageDamagumo.json || -6636693793515779733
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-05-07T23:55:45Z

Atyfaz: /* Individual Drop Chances vs Cumulative Chances */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Titan Blowhog || Verified by atyfaz
|-
| Blizzarding Blowhog || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|-
| Glow Pellet Pile || -4985278700699515859
|-
| Unknown found in GHageDamagumo.json || -6636693793515779733
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-05-06T01:24:35Z

Atyfaz: /* UnknownImport Table */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|-
| Glow Pellet Pile || -4985278700699515859
|-
| Unknown found in GHageDamagumo.json || -6636693793515779733
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-05-05T23:07:59Z

Atyfaz: /* UnknownImport Table */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|-
| Unknown found in GDodoro.json || -4985278700699515859
|-
| Unknown found in GDodoro.json || -7078622273973628666
|-
| Unknown found in GHageDamagumo.json || -6636693793515779733
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-05-05T22:07:40Z

Atyfaz: /* UnknownImport Table */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|-
| Unknown found in GDodoro.json || -4985278700699515859
|-
| Unknown found in GDodoro.json || -7078622273973628666
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-05-01T20:34:07Z

Atyfaz: /* UnknownImport Table */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray || -4763302052886507494
|-
| either ice blast or bomb rock (soon to be tested) || -7152833028850840769
|-
| either ice blast or bomb rock (soon to be tested) || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|-
| Mitite || -4725210440768732887
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-04-26T03:29:43Z

Atyfaz: /* Changing Drops Manually */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. The Honeywisp, Iridescent Flint Beetle, Iridescent Glint Beetle, and Doodlebug ignore drops given to them in area spawns, and always use their default in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray|| -4763302052886507494
|-
| ??? Doodlebug drop || -7152833028850840769
|-
| ??? Doodlebug drop || -4725210440768732887
|-
| ??? Doodlebug drop || -5755297407425022786
|-
| 1 Pellet || -7913393397111906650
|-
| 5 Pellet || -9111098510939959663
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-04-26T02:22:28Z

Atyfaz: /* Changing Drops Manually */

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For various reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

=====UnknownImport Table=====

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! Item !! UnknownImport
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray|| -4763302052886507494
|-
| Ice Blast || TBD via Doodlebug
|-
| Bomb Rock || TBD via Doodlebug
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-04-26T02:19:28Z

Atyfaz:

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]].

While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ActorSerializeParameter and AI]].

The gen variables one is likely looking for are:

{| class="wikitable sortable"
! Gen var || Meaning
|-
| <code>AttackAffordance_GEN_VARIABLE</code> || Possibly the properties of if an entity believes it can attack
|-
| <code>{EntityName}AI_GEN_VARIABLE</code> || Configures this specific enemy's behaviour and values
|-
| <code>TekiAIParameter</code> || Universal parameters all enemies have in common, mostly including detection, search, and territory, flick parameters, and drop parameters
|-
| <code>CarrotMove_GEN_VARIABLE</code> || Speed values
|-
| <code>Life_GEN_VARIABLE</code> || Health, health bar and some damage properties
|-
| <code>PointerAssist_GEN_VARIABLE</code> || Cursor properties
|}

==TekiAIParameter==

These parameters are shared aspects all enemies have in common, including territory, detection and vision areas, how the enemy flicks off Pikmin, and what they drop by default when defeated.

===Search and Territory===

====Parameters====

These values determine how and what an enemy can see.

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>Radius</code> || The distance up to which the enemy can see or be aware of any captains or Pikmin.
|-
| <code>Angle</code> || The angle of its vision, essentially creating a vision cone. Determines line of sight. When set to 0, the enemy skips checking if its vision has targets in it.
|-
| <code>SphereRadius</code> || The size of the enemy. Used to determine if an enemy is currently in the search area.
|-
| <code>Center</code> || The center point of the enemy, used to determine where the vision cone and <code>SphereRadius</code> begin from.
|-
| <code>TerritoryNestRatio</code> || A value between 0 and 1 that determines how much of the territory is the creature's nest. This is used in conjunction with the boolean below to limit certain behaviours to only occur within the nest or to occur within the entire territory.
|-
| <code>bSearchOuterTerritory</code> || A boolean usually set to false by default. This allows the enemy to use its full territory zone within the search area instead of just its nest, allowing them to roam further from home, be more alert, and act more aggressively.
|}

====SearchArea Categories====

The different categories and circumstances in which the enemy will be looking for targets or not.

{| class="wikitable sortable"
! SearchArea Category || Meaning
|-
| <code>SearchAreaGoToHome</code> || The enemy will attempt to go home if it is outside of or cannot see its home nest or territory.
|-
| <code>SearchAreaRest</code> || Used when an enemy is not aware of the player yet. For sleeping bulborbs and the Man-At-Legs, this determines when they begin to wake up once a Pikmin or captain gets close enough.
|-
| <code>SearchAreaCaution</code> || Used when an enemy is already alerted to the presence of the player, usually giving increased awareness compared to <code>SearchAreaRest</code>.
|-
| <code>SearchAreaOtakaraCarry</code> || The enemy's awareness of objects being carried nearby. Usually the highest search area for enemies so they can interrupt carrying routes.
|-
| <code>EatArea</code> || The distance and line of sight from which the enemy will attack. Increases to these values can often result in bulborb family members attacking when there are no Pikmin, but it will make Wollyhops jump much farther and Swooping Snitchbugs swoop toward Pikmin from farther distances.
|-
| <code>Territory</code> || The enemies total territory and home, which it will try to return to. Has an inner nest zone and an outer territory zone determined by <code>TerritoryNestRatio</code>.
|}

===Flick Parameters===

{| class="wikitable sortable"
! Parameter || Meaning
|-
| <code>MaxFlickNum</code> || How many Pikmin the enemy will shake off. By default this value is 50 when not specified and needs to have a new line added to <code>FlickArg</code> to change. This default is easiest to see on the Empress Bulbax (<code>Queen</code>), Porquillion (<code>Hari</code>), and Waddlepus (<code>Awadako</code>) when charged.
|}

===Item Drop Parameters===

====Individual Drop Chances vs Cumulative Chances====

[[File:Droptable-example-arcticbeetle.png|thumb|alt=The Rock Onion is set to drop 100% of the time when the condition NoSalvageItem is met, meaning the Rock Onion hasn't been collected yet. One to three 1-Pellets will drop 100% of the time if the Rock Onion has been collected because it is set to SalvageItem.|The modified drops of an Arctic Cannon Beetle.]]

In Pikmin 4, there are two ways enemies and objects will drop loot. Most enemies roll the chances for their drops individually independent of other loot in their drop list. This means you can give them multiple drops with multiple percent chances, and they will roll individually for each item and possibly drop multiple things. Eggs, however, roll for one item and use their drops section as a cumulative table, meaning the percentages should add up to 100% and will only produce one result. Some enemies have this cumulative behavior instead and will never drop more than one item at a time, just like eggs. Below is a table of all the enemies that behave this way and therefor cannot drop more than one thing at a time.

{| class="wikitable sortable"
! Species || Notes
|-
| Arctic Cannon Beetle || Verified by atyfaz
|-
| Horned Cannon Beetle || Needs testing
|-
| Honeywisp || Vanilla behavior present in game
|-
| Egg || Vanilla behavior present in game
|}

By using drop conditions like NoSalvageItem and SalvageItem, multiple drops should be possible but never at the same time, as seen in the example to the right.

====Changing Drops Manually====

For some reasons, you may want to change the default drops in an enemy's JSON file. The main reason you may want to do this is that creatures and eggs spawned in via ActorSpawners can't have their drops set and will use the defaults in their JSON. If you go into enemy JSON files to edit drops manually, you will notice a section like this:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-6652779844111892794"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 2,
"DropRatio": 1.0,
"bRegistGenerator": false,
"DropConditions": []
}
],
...
</source>

<code>"UnknownImport"</code> correlates to specific items or objects being dropped. In this case, the number in this example will produce Raw Material. You can change how many of the item drop using <code>"MinNum"</code> and <code>"MaxNum"</code>, either dropping a random amount between the two numbers, or producing the exact amount if you set both to the same number. <code>"DropRatio"</code> is the percent chance to drop the item as a decimal with 1.0 equaling 100%. For dropping multiple items at once, you would use something like the following:

<source lang="JSON">
"DropParameter": {
"DropItemParameter": [
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4916160322636296702"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.8,
"bRegistGenerator": false,
"DropConditions": []
},
{
"SpawnMiniInfo": {
"DropActor": {
"UnknownImport": "-4763302052886507494"
},
...
},
"UniqueId": 18446744073709551615,
"MinNum": 1,
"MaxNum": 1,
"DropRatio": 0.2,
"bRegistGenerator": false,
"DropConditions": []
},
],
...
</source>

This is the Mitite's default drops, with 1 nectar at 80% and 1 Ultra-Spicy Spray at 20%.

Most importantly, here is a table with all the most useful drops:

{| class="wikitable sortable"
|-
! UnknownImport !! Item
|-
| Raw Material || -6652779844111892794
|-
| Nectar || -4916160322636296702
|-
| Ultra-Spicy Spray|| -4763302052886507494
|-
| Ice Blast || TBD via Doodlebug
|-
| Bomb Rock || TBD via Doodlebug
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Enemy Parameters

2026-04-25T22:15:00Z

Atyfaz: /* Enemy Drops */

Enemy Parameters

2026-04-25T22:12:45Z

Atyfaz:

File:Droptable-example-arcticbeetle.png

2026-04-25T22:12:31Z

Atyfaz: An example of how to use drop tables in Pikmin 4 modding tool Dandori Desktop+. It shows how an enemy that cannot drop more than one item at a time, such as the Arctic Cannon Beetle, can drop different items based on condition to somewhat work around this setback that most enemies do not have as they can drop more than one item at once.

== Summary ==
An example of how to use drop tables in Pikmin 4 modding tool Dandori Desktop+. It shows how an enemy that cannot drop more than one item at a time, such as the Arctic Cannon Beetle, can drop different items based on condition to somewhat work around this setback that most enemies do not have as they can drop more than one item at once.

Enemy Parameters

2025-10-05T23:07:29Z

Atyfaz: /* Flick Parameters */

Enemy Parameters

2025-10-04T23:26:05Z

Atyfaz: /* TekiAIParameter */

Enemy Parameters

2025-10-04T23:17:24Z

Atyfaz: /* Flick Parameters */

Enemy Parameters

2025-10-04T21:48:19Z

Atyfaz:

Enemy Parameters

2025-10-04T21:46:38Z

Atyfaz:

Data Table/Actor Parameters

2025-09-06T23:10:12Z

Atyfaz:

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Data table files exist in <code>Carrot4/Core/GActor</code> and declare some of the superclass and individual parameters for objects, such as treasure weights and values, pikmin speeds and some enemy values.

== DT_TekiParameter ==

This file declares variables for each enemy usually related to economy and interaction values with other objects

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal creature name.
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>CarryIncPikmins</code> || Number of Pikmin sprouts produced by the corpse.
|-
| <code>MaxLife</code> || The max health of the enemy.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|-
| <code>VsScore</code> || Value during dandori battles
|-
| <code>BombHit</code> || Makes bombs and boulders do damage equal to MaxLife divided by BombHit. Yes, this includes the boulders shot by Armored Cannon Larva.
|-
| <code>BombInsideHit</code> || Makes ingested bombs do damage equal to MaxLife divided by BombInsideHit. Often does more damage than BombHit.
|-
| <code>PoisonHit</code> || Makes White Pikmin's poison damage after being eaten equal to MaxLife divided by PoisonHit.
|-
| <code>PurpleDirectHit</code> || Makes Purple Pikmin's impact damage equal to MaxLife divided by PurpleDirectHit.
|-
| <code>PressHit</code> || Used for direct hits on enemies like Bulborbs and Sheargrubs. It deals damage equal to MaxLife divided by PressHit.
|-
| <code>IceBombHit</code> || How many Ice Blasts it takes to max out the freeze gauge. Typically defaults to 1.0.
|-
| <code>IceBombInsideHit</code> || How many ingested Ice Blasts it takes to max out the freeze gauge. Typically more effective than IceBombHit.
|-
| <code>FreezeHit</code> || How many hits from an Ice Pikmin is required to max out the freeze gauge.
|-
| <code>FreezeInsideHit</code> || How many Ice Pikmin being eaten it takes to max out the freeze gauge.
|-
| <code>FreezeDamageRatio</code> || Multiplier on damage that frozen enemies take, reducing damage.
|-
| <code>CrushHit</code> || Damage taken if crushed by another enemy such as a Wollyhop, equal to MaxLife divided by CrushHit.
|-
| <code>FrozenCrushDamageRate</code> || Multiplier on how much crush damage is taken while frozen.
|-
| <code>SnowBallDamage</code> || Damage taken if hit by a snowball, equal to MaxLife divided by SnowBallDamage.
|-
| <code>StoneDamage</code> || Makes the Pebble Pitcher deal damage equal to MaxLife divided by StoneDamage.
|-
| <code>ThunderStopTime</code> || How long an enemy will be paused when struck with a Lightning Strike. There is also a separate file for the Lightning Strike, found at Core > ItemFunction > DT_ItemFunctionParameter.json, that determines its default stop time both in the main game and in Dandori Battles, defaulting to 7.5 for the main game and 2.5 for Dandori Battles. It also has differing ranges from 1,000 in the main game and 1,000,000 in Dandori Battles, but currently DT_ItemFunctionParameter.json does not encode properly and cannot be modified.
|-
| <code>CrushStopTime</code> || Enemy pause time if CrushHit applies damage to it.
|-
| <code>CrushKnockBackSpeed</code> || Knockback speed an enemy will take if CrushHit applies damage to it.
|-
| <code>FlashbangRate</code> ||
|-
| <code>FreezeDropType</code> || Corresponds with values in DT_FreezeDropItem.json to determine how much nectar an enemy should drop. The categories are TekiS, TekiM, TekiL, Boss, BigBoss, and NoDrop.
|-
| <code>DropStationPieceNum</code> ||
|-
| <code>URODistanceThresholds</code> || Array of 3 floats
|-
| <code>PlayerDamage</code> || How much damage the captain and Oatchi will take from the enemy's attack. This does not include the damage from boulders and snowballs or other entities spawned by an enemy that have their own files.
|-
| <code>OtherDamage</code> || How much damage the enemy will deal to a Tricknoll or Lumiknoll.
|-
| <code>FlashBangTargetWeight</code> ||
|-
|}

== DT_MoveSpeedRate ==

This file declares the speed multiplier of surfaces in the game, like sticky floors and swimming

== DT_OrimaEquipParameter ==

This file declares the values for equipment pieces of the main character

== DT_OtakaraParameter ==

This file declares variables for treasures

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal treasure name
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Data Table/Actor Parameters

2025-09-06T21:56:16Z

Atyfaz:

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Data table files exist in <code>Carrot4/Core/GActor</code> and declare some of the superclass and individual parameters for objects, such as treasure weights and values, pikmin speeds and some enemy values.

== DT_TekiParameter ==

This file declares variables for each enemy usually related to economy and interaction values with other objects

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal creature name.
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>CarryIncPikmins</code> || Number of Pikmin sprouts produced by the corpse.
|-
| <code>MaxLife</code> || The max health of the enemy.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|-
| <code>VsScore</code> || Value during dandori battles
|-
| <code>BombHit</code> || Makes bombs do damage equal to MaxLife divided by BombHit.
|-
| <code>BombInsideHit</code> || Makes ingested bombs do damage equal to MaxLife divided by BombInsideHit. Often does more damage than BombHit.
|-
| <code>PoisonHit</code> || Makes White Pikmin's poison damage after being eaten equal to MaxLife divided by PoisonHit.
|-
| <code>PurpleDirectHit</code> || Makes Purple Pikmin's impact damage equal to MaxLife divided by PurpleDirectHit.
|-
| <code>PressHit</code> || Used for direct hits on enemies like Bulborbs and Sheargrubs. It deals damage equal to MaxLife divided by PressHit.
|-
| <code>IceBombHit</code> || How many Ice Blasts it takes to max out the freeze gauge. Typically defaults to 1.0.
|-
| <code>IceBombInsideHit</code> || How many ingested Ice Blasts it takes to max out the freeze gauge. Typically more effective than IceBombHit.
|-
| <code>FreezeHit</code> || How many hits from an Ice Pikmin is required to max out the freeze gauge.
|-
| <code>FreezeInsideHit</code> || How many Ice Pikmin being eaten it takes to max out the freeze gauge.
|-
| <code>FreezeDamageRatio</code> || Multiplier on damage that frozen enemies take, reducing damage.
|-
| <code>CrushHit</code> || Damage taken if crushed by a boulder or another enemy such as a Wollyhop, equal to MaxLife divided by CrushHit.
|-
| <code>FrozenCrushDamageRate</code> || Multiplier on how much crush damage is taken while frozen.
|-
| <code>SnowBallDamage</code> || Damage taken if hit by a snowball. Research if fixed damage or a division of MaxLife is needed.
|-
| <code>StoneDamage</code> || Research needed if this is for boulders or the Pebble Pitcher, and if it's fixed damage or a division of MaxLife.
|-
| <code>ThunderStopTime</code> || How long an enemy will be paused when struck with a Lightning Strike. There is also a separate file for the Lightning Strike, found at Core > ItemFunction > DT_ItemFunctionParameter.json, that determines its default stop time both in the main game and in Dandori Battles, defaulting to 7.5 for the main game and 2.5 for Dandori Battles. It also has differing ranges from 1,000 in the main game and 1,000,000 in Dandori Battles, but currently DT_ItemFunctionParameter.json does not encode properly and cannot be modified.
|-
| <code>CrushStopTime</code> || Enemy pause time if CrushHit applies damage to it.
|-
| <code>CrushKnockBackSpeed</code> || Knockback speed an enemy will take if CrushHit applies damage to it.
|-
| <code>FlashbangRate</code> ||
|-
| <code>FreezeDropType</code> || Corresponds with values in DT_FreezeDropItem.json to determine how much nectar an enemy should drop. The categories are TekiS, TekiM, TekiL, Boss, BigBoss, and NoDrop.
|-
| <code>DropStationPieceNum</code> ||
|-
| <code>URODistanceThresholds</code> || Array of 3 floats
|-
| <code>PlayerDamage</code> || How much damage the captain and Oatchi will take from the enemy's attack. This does not include the damage from boulders and snowballs or other entities spawned by an enemy that have their own files.
|-
| <code>OtherDamage</code> || How much damage the enemy will deal to a Tricknoll or Lumiknoll.
|-
| <code>FlashBangTargetWeight</code> ||
|-
|}

== DT_MoveSpeedRate ==

This file declares the speed multiplier of surfaces in the game, like sticky floors and swimming

== DT_OrimaEquipParameter ==

This file declares the values for equipment pieces of the main character

== DT_OtakaraParameter ==

This file declares variables for treasures

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal treasure name
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Data Table/Actor Parameters

2025-09-06T21:13:08Z

Atyfaz:

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Data table files exist in <code>Carrot4/Core/GActor</code> and declare some of the superclass and individual parameters for objects, such as treasure weights and values, pikmin speeds and some enemy values.

== DT_TekiParameter ==

This file declares variables for each enemy usually related to economy and interaction values with other objects

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal creature name.
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>CarryIncPikmins</code> || Number of Pikmin sprouts produced by the corpse.
|-
| <code>MaxLife</code> || The max health of the enemy.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|-
| <code>VsScore</code> || Value during dandori battles
|-
| <code>BombHit</code> || Makes bombs do damage equal to MaxLife divided by BombHit.
|-
| <code>BombInsideHit</code> || Makes ingested bombs do damage equal to MaxLife divided by BombInsideHit. Often does more damage than BombHit.
|-
| <code>PoisonHit</code> || Makes White Pikmin's poison damage after being eaten equal to MaxLife divided by PoisonHit.
|-
| <code>PurpleDirectHit</code> || Makes Purple Pikmin's impact damage equal to MaxLife divided by PurpleDirectHit.
|-
| <code>PressHit</code> || Used for direct hits on enemies like Bulborbs and Sheargrubs. It deals damage equal to MaxLife divided by PressHit.
|-
| <code>IceBombHit</code> || How many Ice Blasts it takes to max out the freeze gauge. Typically defaults to 1.0.
|-
| <code>IceBombInsideHit</code> || How many ingested Ice Blasts it takes to max out the freeze gauge. Typically more effective than IceBombHit.
|-
| <code>FreezeHit</code> || How many hits from an Ice Pikmin is required to max out the freeze gauge.
|-
| <code>FreezeInsideHit</code> || How many Ice Pikmin being eaten it takes to max out the freeze gauge.
|-
| <code>FreezeDamageRatio</code> || Multiplier on damage that frozen enemies take, reducing damage.
|-
| <code>CrushHit</code> || Damage taken if crushed by a boulder or another enemy such as a Wollyhop, equal to MaxLife divided by CrushHit.
|-
| <code>FrozenCrushDamageRate</code> || Multiplier on how much crush damage is taken while frozen.
|-
| <code>SnowBallDamage</code> || Damage taken if hit by a snowball. Research if fixed damage or a division of MaxLife is needed.
|-
| <code>StoneDamage</code> || Research needed if this is for boulders or the Pebble Pitcher, and if it's fixed damage or a division of MaxLife.
|-
| <code>ThunderStopTime</code> || How long an enemy will be paused when struck with a Lightning Strike. There is also a separate file for the Lightning Strike, found at Core > ItemFunction > DT_ItemFunctionParameter.json, that determines its default stop time both in the main game and in Dandori Battles, defaulting to 7.5 for the main game and 2.5 for Dandori Battles. It also has differing ranges from 1,000 in the main game and 1,000,000 in Dandori Battles, but currently DT_ItemFunctionParameter.json does not encode properly and cannot be modified.
|-
| <code>CrushStopTime</code> || Enemy pause time if CrushHit applies damage to it.
|-
| <code>CrushKnockBackSpeed</code> || Knockback speed an enemy will take if CrushHit applies damage to it.
|-
| <code>FlashbangRate</code> ||
|-
| <code>FreezeDropType</code> || Possibly whether an enemy will drop its normal drops if frozen or drop nectar instead. Confirmation needed.
|-
| <code>DropStationPieceNum</code> ||
|-
| <code>URODistanceThresholds</code> || Array of 3 floats
|-
| <code>PlayerDamage</code> || How much damage the captain and Oatchi will take from the enemy's attack. This does not include the damage from boulders and snowballs or other entities spawned by an enemy that have their own files.
|-
| <code>OtherDamage</code> || How much damage the enemy will deal to a Tricknoll or Lumiknoll.
|-
| <code>FlashBangTargetWeight</code> ||
|-
|}

== DT_MoveSpeedRate ==

This file declares the speed multiplier of surfaces in the game, like sticky floors and swimming

== DT_OrimaEquipParameter ==

This file declares the values for equipment pieces of the main character

== DT_OtakaraParameter ==

This file declares variables for treasures

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal treasure name
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|}

[[Category:Constants]]
[[Category:Pikmin 4]]

Data Table/Actor Parameters

2025-09-06T20:39:05Z

Atyfaz:

{{DISPLAYTITLE:Data Table/Actor Parameters}}

Data table files exist in <code>Carrot4/Core/GActor</code> and declare some of the superclass and individual parameters for objects, such as treasure weights and values, pikmin speeds and some enemy values.

== DT_TekiParameter ==

This file declares variables for each enemy usually related to economy and interaction values with other objects

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal creature name.
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>CarryIncPikmins</code> || Number of Pikmin sprouts produced by the corpse.
|-
| <code>MaxLife</code> || The max health of the enemy.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|-
| <code>VsScore</code> || Value during dandori battles
|-
| <code>BombHit</code> || Makes bombs do damage equal to MaxLife divided by BombHit.
|-
| <code>BombInsideHit</code> || Makes ingested bombs do damage equal to MaxLife divided by BombInsideHit. Often does more damage than BombHit.
|-
| <code>PoisonHit</code> || Makes White Pikmin's poison damage after being eaten equal to MaxLife divided by PoisonHit.
|-
| <code>PurpleDirectHit</code> || Makes Purple Pikmin's impact damage equal to MaxLife divided by PurpleDirectHit.
|-
| <code>PressHit</code> || Used for direct hits on enemies like Bulborbs and Sheargrubs. It deals damage equal to MaxLife divided by PressHit.
|-
| <code>IceBombHit</code> || How many Ice Blasts it takes to max out the freeze gauge. Typically defaults to 1.0.
|-
| <code>IceBombInsideHit</code> || How many ingested Ice Blasts it takes to max out the freeze gauge. Typically more effective than IceBombHit.
|-
| <code>FreezeHit</code> || How many hits from an Ice Pikmin is required to max out the freeze gauge.
|-
| <code>FreezeInsideHit</code> || How many Ice Pikmin being eaten it takes to max out the freeze gauge.
|-
| <code>FreezeDamageRatio</code> || Multiplier on damage that frozen enemies take, reducing damage.
|-
| <code>CrushHit</code> || Damage taken if crushed by a boulder or another enemy such as a Wollyhop, equal to MaxLife divided by CrushHit.
|-
| <code>FrozenCrushDamageRate</code> || Multiplier on how much crush damage is taken while frozen.
|-
| <code>SnowBallDamage</code> || Damage taken if hit by a snowball. Research if fixed damage or a division of MaxLife is needed.
|-
| <code>StoneDamage</code> || Research needed if this is for boulders or the Pebble Pitcher, and if it's fixed damage or a division of MaxLife.
|-
| <code>ThunderStopTime</code> || How long an enemy will be paused when struck with a Lightning Strike. There is also a separate file for the Lightning Strike that determines it's default stop time both in the main game and in Dandori Battles, defaulting to 7.5 for the main game and 2.5 for Dandori Battles. It also has differing ranges from 1000 in the main game and 10000 in Dandori Battles.
|-
| <code>CrushStopTime</code> || Enemy pause time if CrushHit applies damage to it.
|-
| <code>CrushKnockBackSpeed</code> || Knockback speed an enemy will take if CrushHit applies damage to it.
|-
| <code>FlashbangRate</code> ||
|-
| <code>FreezeDropType</code> || Possibly whether an enemy will drop its normal drops if frozen or drop nectar instead. Confirmation needed.
|-
| <code>DropStationPieceNum</code> ||
|-
| <code>URODistanceThresholds</code> || Array of 3 floats
|-
| <code>PlayerDamage</code> || How much damage the captain and Oatchi will take from the enemy's attack. This does not include the damage from boulders and snowballs or other entities spawned by an enemy that have their own files.
|-
| <code>OtherDamage</code> || How much damage the enemy will deal to a Tricknoll or Lumiknoll.
|-
| <code>FlashBangTargetWeight</code> ||
|-
|}

== DT_MoveSpeedRate ==

This file declares the speed multiplier of surfaces in the game, like sticky floors and swimming

== DT_OrimaEquipParameter ==

This file declares the values for equipment pieces of the main character

== DT_OtakaraParameter ==

This file declares variables for treasures

{| class="wikitable sortable"
! Internal Name || Meaning
|-
| <code>ActorName</code> || Internal treasure name
|-
| <code>CarryWeightMin</code> || The minimum carry strength of the combined carriers required to carry an object.
|-
| <code>CarryWeightMax</code> || The maximum number of individual carriers on an object, including captains, Oatchi, Moss, as well as the Breadbug and Giant Breadbug. Each entity only counts as 1 regardless of its carry strength.
|-
| <code>CarryWeightMinVs</code> || The minimum carry strength of the combined carriers required to carry an object while in a Dandori Battle.
|-
| <code>CarryWeightMaxVs</code> || The maximum number of individual carriers on an object during Dandori Battles. This is also used when a Breadbug or Giant Breadbug is carrying the object.
|-
| <code>Kira</code> || Sparklium
|-
| <code>Poko</code> || Dandori points?
|}

[[Category:Constants]]
[[Category:Pikmin 4]]