Minecraft:Dragon Egg: Difference between revisions
More actions
Sync: updated from Minecraft |
Sync: updated from Minecraft |
||
| (One intermediate revision by the same user not shown) | |||
| Line 33: | Line 33: | ||
=== Post-generation === | === Post-generation === | ||
{{IN|Java}}, a single dragon egg is generated | {{IN|Java}}, a single dragon egg is generated at (X=0, Z=0) when the first [[Minecraft:ender dragon]] is defeated. The Y-coordinate is determined by the <code>MOTION_BLOCKING</code> heightmap, which locates the highest block at (X=0, Z=0) with a collision box: | ||
* The dragon egg spawns directly on top of this block | |||
* If a block with collision is placed at the maximum build height (Y=255), the dragon egg fails to generate, as the target position (Y=256) exceeds the world height limit | |||
* Any non-motion-blocking block at that location (such as a button, torch, redstone wire, or air) is overwritten and replaced by the dragon egg | |||
{{IN|Bedrock}}, two dragon eggs generate on top of the exit portal; one generates when the first ender dragon is defeated, while the other generates when the second ender dragon is defeated.<ref name="TwoEggs" /> | |||
== Usage == | == Usage == | ||
| Line 123: | Line 129: | ||
|{{HistoryLine|||dev=12w30d|[[File:Dragon Egg JE1.png|32px]] The dragon egg uses its own model again when falling.}} | |{{HistoryLine|||dev=12w30d|[[File:Dragon Egg JE1.png|32px]] The dragon egg uses its own model again when falling.}} | ||
|{{HistoryLine||1.4.4|dev=1.4.3|[[File:Falling Dragon Egg JE4.png|32px]] The dragon egg uses cube model when falling.<ref>{{bug|MC-1688}}</ref> | |{{HistoryLine||1.4.4|dev=1.4.3|[[File:Falling Dragon Egg JE4.png|32px]] The dragon egg uses cube model when falling.<ref>{{bug|MC-1688}}</ref> | ||
|The dragon egg once again produces particles; however, it does not actually point to the location it teleports to as it did previously | |The dragon egg once again produces particles; however, it does not actually point to the location it teleports to as it did previously.<ref name="MC-2157">{{bug|MC-2157|resolution=Fixed}}</ref>}} | ||
|{{HistoryLine||1.4.6|[[File:Dragon Egg JE1.png|32px]] The dragon egg uses its own model when falling, once again.}} | |{{HistoryLine||1.4.6|[[File:Dragon Egg JE1.png|32px]] The dragon egg uses its own model when falling, once again.}} | ||
|{{HistoryLine||1.8|dev=14w07a|[[File:Dragon Egg JE2.png|32px]] The dragon egg is among the earliest of many blocks to be converted to custom block [[Minecraft:model]]s, deprecating hardcoded block rendering. The conversion, however, is flawed, as the third "tier" from the top is the same size as the second, resulting in an incorrectly shaped model as well as inconsistently sized pixels.<ref>{{bug|MC-120417}}</ref>}} | |{{HistoryLine||1.8|dev=14w07a|[[File:Dragon Egg JE2.png|32px]] The dragon egg is among the earliest of many blocks to be converted to custom block [[Minecraft:model]]s, deprecating hardcoded block rendering. The conversion, however, is flawed, as the third "tier" from the top is the same size as the second, resulting in an incorrectly shaped model as well as inconsistently sized pixels.<ref>{{bug|MC-120417}}</ref>}} | ||
| Line 133: | Line 139: | ||
|{{HistoryLine||1.21.2|dev=24w33a|[[File:Dragon Egg JE5.png|32px]] The broken model and UV mapping of the dragon egg have been fixed.<ref>{{bug|MC-120417|||Fixed}}</ref>}} | |{{HistoryLine||1.21.2|dev=24w33a|[[File:Dragon Egg JE5.png|32px]] The broken model and UV mapping of the dragon egg have been fixed.<ref>{{bug|MC-120417|||Fixed}}</ref>}} | ||
|{{HistoryLine||26.1|dev=snap11|Dragon eggs now check if there is a block beneath the teleport destination.<ref>{{bug|MC-231663|||Fixed}}</ref>}} | |{{HistoryLine||26.1|dev=snap11|Dragon eggs now check if there is a block beneath the teleport destination.<ref>{{bug|MC-231663|||Fixed}}</ref>}} | ||
|{{HistoryLine||26.3|dev=snap4|The dragon egg's particles now once again properly point to the location it teleports to.<ref name="MC-2157"/>}} | |||
}} | }} | ||
Latest revision as of 11:07, 15 October 2026
Template:Distinguish Template:Infobox block The dragon egg is a gravity-affected Minecraft:block that can be obtained only once per Minecraft:world (or twice Template:In<ref name=TwoEggs>Template:Bug</ref>) by defeating the Minecraft:ender dragon. It Minecraft:teleports to avoid being Template:Control, but drops as an Minecraft:item if it falls onto a non-full block such as a Minecraft:torch or is pushed by a Minecraft:piston.
Obtaining
The dragon egg is available in the Creative inventory. It can be obtained with Template:Control or the Template:Cmd command, or placed in the world with commands such as Template:Cmd and Template:Cmd.
Breaking
The dragon egg usually cannot be mined directly, as trying to do so causes it to teleport within a 31×15×31 volume centered on the egg, with locations toward the center more likely. If all air blocks in that area are filled so there is nowhere for the egg to teleport to, or if it fails to find an air block after 1,000 attempts at teleporting, it can be mined.
The dragon egg is a gravity-affected block, and drops as an item when pushed by a Minecraft:piston or when it falls onto a block less than a full block tall, such as a Minecraft:torch or a bottom Minecraft:slab.
When destroyed by an Minecraft:explosion, the block always drops as an item.
The dragon egg is not immune to destruction by the ender dragon, despite being produced by it.<ref name=":0">Template:Bug</ref> Template:Breaking row
Post-generation
Template:IN, a single dragon egg is generated at (X=0, Z=0) when the first Minecraft:ender dragon is defeated. The Y-coordinate is determined by the MOTION_BLOCKING heightmap, which locates the highest block at (X=0, Z=0) with a collision box:
- The dragon egg spawns directly on top of this block
- If a block with collision is placed at the maximum build height (Y=255), the dragon egg fails to generate, as the target position (Y=256) exceeds the world height limit
- Any non-motion-blocking block at that location (such as a button, torch, redstone wire, or air) is overwritten and replaced by the dragon egg
Template:IN, two dragon eggs generate on top of the exit portal; one generates when the first ender dragon is defeated, while the other generates when the second ender dragon is defeated.<ref name="TwoEggs" />
Usage
The dragon egg, if there is no block below it, falls until it lands on the next available block. When it is being affected by gravity and falling, it exhibits a smooth falling animation.
It does not Minecraft:suffocate mobs or players when it falls and covers them, nor does it squash mobs or players like Minecraft:anvils and Minecraft:stalactites do.
The dragon egg can be placed on a non-solid block without falling.
Like other falling blocks, when the dragon egg is floating, it has black particles falling from it.
Light source
The dragon egg emits a Minecraft:light level of 1.
Teleporting
To cause the egg to teleport, press Template:Control or Template:Control while in Minecraft:Survival or Minecraft:Adventure mode (or only Template:Control in Minecraft:Creative). It teleports to an air block nearby (up to seven blocks vertically and fifteen blocks horizontally), emitting portal particles, as endermen and nether portals. It may teleport into the air and subsequently fall to the ground since it forcefully obeys gravity. However, it always checks if there is ground beneath the teleport destination.
When the egg teleports, it creates a particle trail of particles from its old location to its new one.
If all available air blocks are filled, it is possible to break the block.
Dragon egg teleportation lacks teleportation sounds.<ref>Template:Bug</ref>
If egg teleportation finds an invalid location (such as below the world), it makes up to 999 additional attempts to find a valid location.
Sounds
Data values
ID
Template:Edition: Template:ID table
Template:Edition: Template:ID table
Falling block entity
Template:Infobox entity Template:Main {{#lst:Falling Block|entity data}}
Advancements
Videos
History
Development
Java Edition
Bedrock Edition
Legacy Console Edition
New Nintendo 3DS Edition
Data history
Issues
Trivia
- Developer Minecraft:Ulraf in a livestream expressed the idea of giving the dragon egg the use of modifying the Minecraft:world spawn, because there is only one dragon egg per world. He clarified that he experimented with this idea using Minecraft:commands, and that there weren't plans to add this function to vanilla.<ref> https://youtu.be/2cxUNoWNy50?t=11284</ref>
- The writer of the Minecraft comic WonderCraft, Samcube, was requested by Minecraft:Mojang Studios to create official Minecraft posters. In a part of these works, one can see an area with an ender dragon and a Minecraft:chicken on top of a Minecraft:huge mushroom. In the same scene, the dragon egg is visible near the chicken.
- Minecraft:Mojang Studios is aware that the dragon egg generates twice per world in Template:BE in an official video.<ref>https://youtu.be/xPOZqNjOMpA?t=43</ref>
Gallery
Screenshots
-
The teleporting distance of a dragon egg
-
An example of using a Minecraft:piston and a Minecraft:lever to obtain the dragon egg
-
A dragon egg on a Minecraft:snow layer
In other media
-
Samcube's Minecraft:Minecraft poster showing the dragon egg
-
The Model and Texture used in Minecraft: Story Mode
-
A developer concept for a remodeled dragon egg
-
Dragon egg in A Minecraft Movie McDonald's commercial
See also
References
External links
Template:Navbox blocks Template:Navbox entities Template:Navbox The End
Minecraft:de:Drachenei Minecraft:es:Huevo de dragón Minecraft:fr:Oeuf de dragon Minecraft:it:Uovo di drago Minecraft:ja:ドラゴンの卵 Minecraft:ko:드래곤 알 Minecraft:lzh:龍卵 Minecraft:nl:Drakenei Minecraft:pl:Smocze jajo Minecraft:pt:Ovo do Dragão Minecraft:ru:Яйцо дракона Minecraft:uk:Яйце дракона Minecraft:zh:龙蛋