Minecraft:Mob spawning - Revision history

SyncBot: Sync: updated from Minecraft

2026-09-21T11:12:59Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:12, 21 September 2026
Line 230:		Line 230:
	\|		\|
	\|-		\|-
	\| rowspan="4" \| {{EntityLink\|Llama}}		\| rowspan="5" \| {{EntityLink\|Llama}}
	\| rowspan="2" \| 4 \|\| rowspan="2" \| 8		\| rowspan="2" \| 4 \|\| rowspan="2" \| 8
	\| {{BiomeLink\|Savanna Plateau}}		\| {{BiomeLink\|Savanna Plateau}}
Line 253:		Line 253:
	\|		\|
	\|-		\|-
	\| {{BiomeLink\|Windswept Hills}}		\|{{BiomeLink\|Windswept Hills}}
	\|
	\|		\|
	\|		\|
Line 612:		Line 611:
	* {{EntityLink\|Strider}}		* {{EntityLink\|Strider}}
	* {{EntityLink\|Tadpole}}		* {{EntityLink\|Tadpole}}
	* {{EntityLink\|Trader Llama}}		* {{EntityLink\|Trader Llama}}<ref name=MC-272975>{{bug\|MC-272975\|\|Wandering traders and trader llamas count towards the passive mob cap}}</ref><ref group="note" name=MC-272975-note>Despite being included in the creature mob cap, wandering traders and their trader llamas can still spawn even if the cap is full.</ref>
	* {{EntityLink\|Turtle}}		* {{EntityLink\|Turtle}}
	* {{EntityLink\|Wandering Trader}}		* {{EntityLink\|Wandering Trader}}<ref name=MC-272975/><ref group="note" name=MC-272975-note/>
	* {{EntityLink\|Wolf}}		* {{EntityLink\|Wolf}}
	\|-		\|-

SyncBot: Sync: updated from Minecraft

2026-08-31T11:13:08Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 31 August 2026
Line 231:		Line 231:
	\|-		\|-
	\| rowspan="4" \| {{EntityLink\|Llama}}		\| rowspan="4" \| {{EntityLink\|Llama}}
	\| 4 \|\| 8 \|\| {{BiomeLink\|Windswept Savanna}}		\| rowspan="2" \| 4 \|\| rowspan="2" \| 8
			\| {{BiomeLink\|Savanna Plateau}}
			\|
			\|
			\|
			\|-
			\| {{BiomeLink\|Windswept Savanna}}
	\|		\|
	\|		\|

SyncBot: Sync: updated from Minecraft

2026-08-28T11:20:30Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:20, 28 August 2026
Line 512:		Line 512:
	* [[Minecraft:Village]] – Villages not only generate a number of [[Minecraft:villager]]s, but also typically come with one or more existing [[Minecraft:iron golem]]s and various animals, such as [[Minecraft:cow]]s, [[Minecraft:horse]]s, [[Minecraft:pig]]s, [[Minecraft:sheep]], and [[Minecraft:stray cat]]s. If the village is abandoned, the villagers instead generate as [[Minecraft:zombie villager]]s and iron golems will not generate at all.		* [[Minecraft:Village]] – Villages not only generate a number of [[Minecraft:villager]]s, but also typically come with one or more existing [[Minecraft:iron golem]]s and various animals, such as [[Minecraft:cow]]s, [[Minecraft:horse]]s, [[Minecraft:pig]]s, [[Minecraft:sheep]], and [[Minecraft:stray cat]]s. If the village is abandoned, the villagers instead generate as [[Minecraft:zombie villager]]s and iron golems will not generate at all.
	* [[Minecraft:Woodland Mansion]] – The various rooms can have one or more generated [[Minecraft:vindicator]]s and/or an [[Minecraft:evoker]] in them. [[Minecraft:Allay]]s also spawn in woodland mansions.		* [[Minecraft:Woodland Mansion]] – The various rooms can have one or more generated [[Minecraft:vindicator]]s and/or an [[Minecraft:evoker]] in them. [[Minecraft:Allay]]s also spawn in woodland mansions.
	* [[Minecraft:Nether Fortress\|Nether fortress]] - [[Minecraft:Blaze\|Blazes]] and [[Minecraft:Wither Skeleton\|wither skeletons]] can only spawn in nether fortresses.

	== Spawn cycle ==		== Spawn cycle ==

SyncBot: Sync: updated from Minecraft

2026-08-24T11:13:36Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 24 August 2026
Line 6:		Line 6:
	{{Exclusive\|Java\|section=1}}		{{Exclusive\|Java\|section=1}}

	As new [[Minecraft:chunk]]s are generated, they have a chance to generate an initial set of [[Minecraft:mob]]s from the "creature" category (i.e. ~~most~~ naturally-occurring land animals<ref group="A">Even though [[Minecraft:ocelot]]s are animals and count against the "creature" mob cap, their spawn in jungle biomes is configured as part of the "monster" category. ({{bug\|MC-1788}}) As a result they never spawn on chunk generation.</ref>) along with them, ignoring the [[#Java Edition mob cap\|mob cap]], any applicable [[#Spawn costs\|spawn costs]], and the setting of {{Cmd\|/gamerule spawn_mobs}}. Any randomness affecting this entire process is derived from the [[Minecraft:world seed]] and the position of the chunk that is being generated. Even though biome distribution within the chunk is already known at this point in the generation, the biome of the north west corner of the chunk at the maximum world height is used to make all decisions about this spawning process. As a result, biomes that generate only underground can never affect the initially spawned mobs. Similarly, although structures have been generated already, their potentially configured spawn overrides are ignored. The spawn conditions for most animals prevent them from spawning on "non-terrain blocks", so they won't end up generating on the roofs (or inside) of structures.		As new [[Minecraft:chunk]]s are generated, they have a chance to generate an initial set of [[Minecraft:mob]]s from the "creature" category (i.e. naturally-occurring land animals) along with them, ignoring the [[#Java Edition mob cap\|mob cap]], any applicable [[#Spawn costs\|spawn costs]], and the setting of {{Cmd\|/gamerule spawn_mobs}}. Any randomness affecting this entire process is derived from the [[Minecraft:world seed]] and the position of the chunk that is being generated. Even though biome distribution within the chunk is already known at this point in the generation, the biome of the north west corner of the chunk at the maximum world height is used to make all decisions about this spawning process. As a result, biomes that generate only underground can never affect the initially spawned mobs. Similarly, although structures have been generated already, their potentially configured spawn overrides are ignored. The spawn conditions for most animals prevent them from spawning on "non-terrain blocks", so they won't end up generating on the roofs (or inside) of structures.

	The selected biome supplies all relevant mob spawn settings for this process:		The selected biome supplies all relevant mob spawn settings for this process:
Line 498:		Line 498:

	<references group="A" />		<references group="A" />


	== Mob spawning on structure generation ==		== Mob spawning on structure generation ==
Line 733:		Line 732:
	Each individual spawn attempt succeeds only if ''all'' of the following conditions are met:		Each individual spawn attempt succeeds only if ''all'' of the following conditions are met:

	* There must be no players or the world spawn point within a 24 block radius (spherical) of the spawning block.		* There must be no players or the world spawn point{{needs testing\|Is this still relevant after the removal of the spawn chunks?}} within a 24 block radius (spherical) of the spawning block.
	* The number of loaded mobs of that type must be less than the mob cap for that type (I.e. the corresponding mob cap must not be full).		* The number of loaded mobs of that type must be less than the mob cap for that type (I.e. the corresponding mob cap must not be full).
	* The mob's collision box upon spawning must not collide with another collision box. A mob cannot spawn inside of anything that would collide with it upon spawning.		* The mob's collision box upon spawning must not collide with another collision box. A mob cannot spawn inside of anything that would collide with it upon spawning.
Line 999:		Line 998:
	The [[Minecraft:warped forest]] and [[Minecraft:soul sand valley]] biomes introduced a new mechanic to limit the amount of mobs that naturally spawn in them. The spawn cost (also called '''spawn potential''' or '''spawn density''') takes on a value for each block in the biome. Certain mobs increase that value by some number ("charge") divided by their distance to the block. If a new spawn attempt would bring the "potential" of the spawning block above a certain threshold, the spawn attempt is canceled. This results in mobs not spawning too close to one another in these biomes, and new spawns in the area are completely blocked long before the full mobcap of 70 hostile mobs is ever reached.		The [[Minecraft:warped forest]] and [[Minecraft:soul sand valley]] biomes introduced a new mechanic to limit the amount of mobs that naturally spawn in them. The spawn cost (also called '''spawn potential''' or '''spawn density''') takes on a value for each block in the biome. Certain mobs increase that value by some number ("charge") divided by their distance to the block. If a new spawn attempt would bring the "potential" of the spawning block above a certain threshold, the spawn attempt is canceled. This results in mobs not spawning too close to one another in these biomes, and new spawns in the area are completely blocked long before the full mobcap of 70 hostile mobs is ever reached.

	More specifically, a mob may be spawned at a location if <code>sum( existing mob's charge ÷ distance to mob ) × new mob's charge < new mob's maximum potential</code>.<!--See net.minecraft.world.level.PotentialCalculator--> While the code allows for different mobs to have different charges and maximum potential, all checked mobs have the same charge and maximum potential within both the ~~[[Minecraft:~~warped forest]] and the ~~[[Minecraft:~~soul sand valley]].		More specifically, a mob may be spawned at a location if <code>sum( existing mob's charge ÷ distance to mob ) × new mob's charge < new mob's maximum potential</code>.<!--See net.minecraft.world.level.PotentialCalculator--> While the code allows for different mobs to have different charges and maximum potential, all checked mobs have the same charge and maximum potential within both the warped forest and the soul sand valley.

	Which mobs contribute to the charge, how much they add, and what the maximum potential is are all biome-specific. Mobs carry charge according to their current biome, and affect spawning in an adjacent biome even if they would not contribute a charge if in that biome. For example, striders in a soul sand valley affect enderman spawns in an adjacent warped forest, even though striders in the warped forest itself do not.		Which mobs contribute to the charge, how much they add, and what the maximum potential is are all biome-specific. Mobs carry charge according to their current biome, and affect spawning in an adjacent biome even if they would not contribute a charge if in that biome. For example, striders in a soul sand valley affect enderman spawns in an adjacent warped forest, even though striders in the warped forest itself do not.

SyncBot: Sync: updated from Minecraft

2026-08-19T11:14:09Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 19 August 2026
Line 541:		Line 541:
	* {{EntityLink\|Drowned}}		* {{EntityLink\|Drowned}}
	* {{EntityLink\|Elder Guardian}}		* {{EntityLink\|Elder Guardian}}
	* {{EntityLink\|Ender Dragon}}		* {{EntityLink\|Ender Dragon}}<ref name=MC-272976>{{bug\|MC-272976\|\|Ender dragons and withers count towards the hostile mob cap}}</ref>
	* {{EntityLink\|Enderman}}		* {{EntityLink\|Enderman}}
	* {{EntityLink\|Endermite}}		* {{EntityLink\|Endermite}}
Line 569:		Line 569:
	* {{EntityLink\|Warden}}		* {{EntityLink\|Warden}}
	* {{EntityLink\|Witch}}		* {{EntityLink\|Witch}}
	* {{EntityLink\|Wither}}		* {{EntityLink\|Wither}}<ref name=MC-272976/>
	* {{EntityLink\|Wither Skeleton}}		* {{EntityLink\|Wither Skeleton}}
	* {{EntityLink\|Zoglin}}		* {{EntityLink\|Zoglin}}
Line 650:		Line 650:
	* {{EntityLink\|Snow Golem}}		* {{EntityLink\|Snow Golem}}
	* {{EntityLink\|Villager}}		* {{EntityLink\|Villager}}
	* All non-mob entity types (including {{EntityLink\|Player}} and {{EntityLink\|Mannequin}})~~{{More info\|Should ender dragons and withers also be listed here, or are they undefined internally?}}~~		* All non-mob entity types (including {{EntityLink\|Player}} and {{EntityLink\|Mannequin}})
	\|}		\|}

SyncBot: Sync: updated from Minecraft

2026-08-15T11:13:08Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-08-11T11:33:54Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:33, 11 August 2026
Line 739:		Line 739:
	[[File:Spawning_science.jpg\|thumb\|Example of a mob pack spawning. The mob spawning area is shaded blue. The yellow figures represent the actual positions that mobs could spawn in after checking the environment. Note that the mobs can spawn inside torch and ladder blocks. The red cube is the center of the pack.]]		[[File:Spawning_science.jpg\|thumb\|Example of a mob pack spawning. The mob spawning area is shaded blue. The yellow figures represent the actual positions that mobs could spawn in after checking the environment. Note that the mobs can spawn inside torch and ladder blocks. The red cube is the center of the pack.]]
	[[File:Spawning_requirements.png\|thumb\|Requirements for the spawning location of individual mobs. Top slabs, upside-down stairs{{Only\|Java}} etc. count as opaque block.]]		[[File:Spawning_requirements.png\|thumb\|Requirements for the spawning location of individual mobs. Top slabs, upside-down stairs{{Only\|Java}} etc. count as opaque block.]]
	For each spawning cycle, attempts are made to spawn ''packs'' of mobs per ''each'' eligible chunk. An eligible chunk is determined by the same check for which chunks are [[Minecraft:random tick]]ed. A random location in the chunk is chosen to be the center point of the pack. The X and Z coordinates are chosen completely at random, while the Y coordinate is a random coordinate between the block above the highest block in the column and ~~-64~~. This makes lower maximum elevations a strong way to increase spawn rates and is the reason why perimeters are so effective. If the block in which a pack spawn occurs is an opaque full cube, further pack spawn attempts are canceled. There are a maximum of 3 pack spawn attempts per mob category.		For each spawning cycle, attempts are made to spawn ''packs'' of mobs per ''each'' eligible chunk. An eligible chunk is determined by the same check for which chunks are [[Minecraft:random tick]]ed. A random location in the chunk is chosen to be the center point of the pack. The X and Z coordinates are chosen completely at random, while the Y coordinate is a random coordinate between the block above the highest block in the column and the minimum [[Minecraft:World boundary#Vertical limits\|vertical limit]]. This makes lower maximum elevations a strong way to increase spawn rates and is the reason why perimeters are so effective. If the block in which a pack spawn occurs is an opaque full cube, further pack spawn attempts are canceled. There are a maximum of 3 pack spawn attempts per mob category.

	Before the attempt to spawn each mob in the pack, the position is offset by ±5 (triangular distribution) on the X and Z axes. Thus, while the pack can be spread out up to 40 blocks from the initial position for a pack size of 4, it's much more likely they'll be closer to the center. Approximately 85% of spawns are within 5 blocks of the pack center, and 99% within 10 blocks of the center. Mobs spawn with the lowest part of their body ''inside'' this area.		Before the attempt to spawn each mob in the pack, the position is offset by ±5 (triangular distribution) on the X and Z axes. Thus, while the pack can be spread out up to 40 blocks from the initial position for a pack size of 4, it's much more likely they'll be closer to the center. Approximately 85% of spawns are within 5 blocks of the pack center, and 99% within 10 blocks of the center. Mobs spawn with the lowest part of their body ''inside'' this area.

SyncBot: Sync: updated from Minecraft

2026-08-01T11:09:39Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 1 August 2026
Line 1,511:		Line 1,511:
	** Is named with a [[Minecraft:name tag]].		** Is named with a [[Minecraft:name tag]].
	** Is tempted with [[Minecraft:food]].		** Is tempted with [[Minecraft:food]].
	** Is [[Minecraft:bred]], or born as a result of breeding ~~(except for turtles hatched from eggs before 1.17.10 <ref>{{bug\|MCPE-70664}}</ref>).~~		** Is [[Minecraft:bred]], or born as a result of breeding
	** Is tamed by the player.		** Is tamed by the player.
	** Is summoned using the {{cmd\|summon}} command or a spawn egg.		** Is summoned using the {{cmd\|summon}} command or a spawn egg.

SyncBot: Sync: updated from Minecraft

2026-07-09T11:10:43Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:10, 9 July 2026
Line 259:		Line 259:
	\| 1 \|\| {{BiomeLink\|Jungle}}		\| 1 \|\| {{BiomeLink\|Jungle}}
	\|		\|
	\|~~Normal Panda~~		\|brown panda
	\|		\|0.1%
	\|-		\|-
	\| 80 \|\| {{BiomeLink\|Bamboo Jungle}}		\| 80 \|\| {{BiomeLink\|Bamboo Jungle}}
	\|		\|
	\|Normal Panda		\|Normal Panda
	\|		\|72.23%
	\|-		\|-
	\| rowspan="2" \| {{EntityLink\|Parrot}} \|\| rowspan="2" \| 1–2 \|\| rowspan="2" \| 1		\| rowspan="2" \| {{EntityLink\|Parrot}} \|\| rowspan="2" \| 1–2 \|\| rowspan="2" \| 1

SyncBot: Sync: updated from Minecraft

2026-07-01T11:22:17Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:22, 1 July 2026
Line 1,494:		Line 1,494:
	* [[Minecraft:Zombie villager]]s: If they were converted from a [[Minecraft:villager]] that has been traded with. This still counts toward the hostile mob cap.<ref>{{bug\|MC-182304}}</ref>		* [[Minecraft:Zombie villager]]s: If they were converted from a [[Minecraft:villager]] that has been traded with. This still counts toward the hostile mob cap.<ref>{{bug\|MC-182304}}</ref>
	* [[Minecraft:Zombified piglin]]s and [[Minecraft:witch]]es: If they were converted from a [[Minecraft:pig]] or [[Minecraft:villager]] struck by lightning.		* [[Minecraft:Zombified piglin]]s and [[Minecraft:witch]]es: If they were converted from a [[Minecraft:pig]] or [[Minecraft:villager]] struck by lightning.
	* [[Minecraft:Hoglin]]s: If a [[Minecraft:crimson fungus]] is {{control\|used}} on them. [[Minecraft:Zoglin]]s as a result of hoglins have crimson fungus {{control\|used}} on them before they zombify also do not despawn.		* [[Minecraft:Hoglin]]s: If a [[Minecraft:crimson fungus]] is {{control\|used}} on them. [[Minecraft:Zoglin]]s as a result of hoglins that have crimson fungus {{control\|used}} on them before they zombify also do not despawn.

	=== ''Bedrock Edition'' ===		=== ''Bedrock Edition'' ===
Line 1,631:		Line 1,631:
	If you have any questions about this, please start a topic on the talk page and ping TigerZhang and Leo768.		If you have any questions about this, please start a topic on the talk page and ping TigerZhang and Leo768.
	-->		-->

	[[Minecraft:cs:Výskyt]]		[[Minecraft:cs:Výskyt]]
			[[Minecraft:de:Spawn]]
	[[Minecraft:es:Aparición]]		[[Minecraft:es:Aparición]]
	[[Minecraft:fr:Apparition]]		[[Minecraft:fr:Apparition]]

← Older revision		Revision as of 11:12, 21 September 2026
Line 230:		Line 230:
	\|		\|
	\|-		\|-
	\| rowspan="4" \| {{EntityLink\|Llama}}		\| rowspan="5" \| {{EntityLink\|Llama}}
	\| rowspan="2" \| 4 \|\| rowspan="2" \| 8		\| rowspan="2" \| 4 \|\| rowspan="2" \| 8
	\| {{BiomeLink\|Savanna Plateau}}		\| {{BiomeLink\|Savanna Plateau}}
Line 253:		Line 253:
	\|		\|
	\|-		\|-
	\| {{BiomeLink\|Windswept Hills}}		\|{{BiomeLink\|Windswept Hills}}
	\|
	\|		\|
	\|		\|
Line 612:		Line 611:
	* {{EntityLink\|Strider}}		* {{EntityLink\|Strider}}
	* {{EntityLink\|Tadpole}}		* {{EntityLink\|Tadpole}}
	* {{EntityLink\|Trader Llama}}		* {{EntityLink\|Trader Llama}}<ref name=MC-272975>{{bug\|MC-272975\|\|Wandering traders and trader llamas count towards the passive mob cap}}</ref><ref group="note" name=MC-272975-note>Despite being included in the creature mob cap, wandering traders and their trader llamas can still spawn even if the cap is full.</ref>
	* {{EntityLink\|Turtle}}		* {{EntityLink\|Turtle}}
	* {{EntityLink\|Wandering Trader}}		* {{EntityLink\|Wandering Trader}}<ref name=MC-272975/><ref group="note" name=MC-272975-note/>
	* {{EntityLink\|Wolf}}		* {{EntityLink\|Wolf}}
	\|-		\|-

← Older revision		Revision as of 11:14, 19 August 2026
Line 541:		Line 541:
	* {{EntityLink\|Drowned}}		* {{EntityLink\|Drowned}}
	* {{EntityLink\|Elder Guardian}}		* {{EntityLink\|Elder Guardian}}
	* {{EntityLink\|Ender Dragon}}		* {{EntityLink\|Ender Dragon}}<ref name=MC-272976>{{bug\|MC-272976\|\|Ender dragons and withers count towards the hostile mob cap}}</ref>
	* {{EntityLink\|Enderman}}		* {{EntityLink\|Enderman}}
	* {{EntityLink\|Endermite}}		* {{EntityLink\|Endermite}}
Line 569:		Line 569:
	* {{EntityLink\|Warden}}		* {{EntityLink\|Warden}}
	* {{EntityLink\|Witch}}		* {{EntityLink\|Witch}}
	* {{EntityLink\|Wither}}		* {{EntityLink\|Wither}}<ref name=MC-272976/>
	* {{EntityLink\|Wither Skeleton}}		* {{EntityLink\|Wither Skeleton}}
	* {{EntityLink\|Zoglin}}		* {{EntityLink\|Zoglin}}
Line 650:		Line 650:
	* {{EntityLink\|Snow Golem}}		* {{EntityLink\|Snow Golem}}
	* {{EntityLink\|Villager}}		* {{EntityLink\|Villager}}
	* All non-mob entity types (including {{EntityLink\|Player}} and {{EntityLink\|Mannequin}})~~{{More info\|Should ender dragons and withers also be listed here, or are they undefined internally?}}~~		* All non-mob entity types (including {{EntityLink\|Player}} and {{EntityLink\|Mannequin}})
	\|}		\|}