Talk:Ender Dragon/Archive 2

No AI tag?
So, will the /NoAI tag work on the Ender Dragon? Brickticks (talk) 18:06, 18 March 2015 (UTC)


 * Yes, it will work fine. The only issue with it is the ender dragon cannot be damaged directly when using NoAI. – KnightMiner  t/c 03:07, 27 March 2015 (UTC)

Targeting 0,0? Doesn't seem like it.
Looking at the class in 1.8, I don't see any evidence that the dragon actually targets 0,0 or specifically orbits 0,0. The "select new target" function will do one of two things:
 * If there are any non-spectator players in the End, regardless of distance, 50% chance of targeting one at random.
 * Otherwise choose random points in X=±60, Y=70–120, Z=±60 until it picks one that's at least 10 blocks away from the dragon's current position.

But when the dragon next updates, if the target is closer than 10 blocks or farther than 150 blocks then it'll choose a new target. So it might target a far-away player and then immediately retarget making it look like it ignores players over 150 blocks away, and the choosing of random target points within ±60 of 0,0 might seem like orbiting.

It also chooses a new target if the last movement attempt was adjusted because of colliding bounding boxes of some sort, but the "core" piece seems to have noclip set so that will never actually happen (but turning off noclip might have resulted in this because of this collision check). There's also a specific variable to force setting a new target, but I don't see it being set from anywhere.

And if it's damaged, it targets a point about 5 blocks behind it (±1 in X and Z from exactly 5 blocks behind) and slightly above (+1–4 in Y), which would cause the "turn and retarget when hit" behavior. Anomie x (talk) 01:20, 10 May 2015 (UTC)


 * Since the video was released almost a year ago, my memory on it was a bit fuzzy, and so the trivia piece sounded accurate. Watching it again states "a random location around 0,0, and further defines it to be a 120×50×120 box centered at 0,95,0, or like you said. Feel free to correct it. – KnightMiner  t/c 01:49, 10 May 2015 (UTC)

Dragon is male?
In dinnerbone's tweethe refers to the dragon as being male should this be edited ? 141.135.4.3 23:57, 19 May 2015 (UTC)

Too many pictures
I think that some of the pictures in the gallery are not needed, because there are older photos that already state the same things. Specially the giant sitting on the Ender Dragon. Do we really need that? Here is my suggested version of the gallery

&#60;&#60; SchobbishBot3000 &#62;&#62; (talk)

I think it might need to stay the same. I mean, it's a gallery. So it shouldn't matter about the "Not needed" pictures. -|Pika Party|- 98.216.47.99 00:30, 28 August 2015 (UTC)

Remove the Console Edition section?
The stuff in the Console Edition section is all in the 1.9 snapshots now, should the section be removed completely? RosalinaFan573 (talk) 04:19, 15 August 2015 (UTC)


 * Not until 1.9 is officially released, rather than just snapshots. At that point, the article will need substantial revision, but this section will probably still exist, as there are some differences between what's in the snapshots and Console Edition. -- Orthotopetalk 04:35, 15 August 2015 (UTC)


 * The console edition boss is different from the 1.9 one. It even says, for 1.9, "One step further." Fyreboy5 (talk) 13:20, 8 February 2016 (UTC)

Dynamic Hitboxes?
I think that the Ender Dragon has dynamic hitboxes, unlike all of the other entities. If you press F3+B, the hitbox of the dragon is very big, but when you shoot an arrow at the hitbox, but not the visible dragon, it doesn't damage the entity. However, of a pig, if you strike the hitbox, but not the visible pig, the entity gets damaged. Thereby, the ender dragon may have dynamic hitboxes. What I mean is a hitbox for each body part. Such as the hurtboxes for characters in Super Smash Bros. I just chose the word Dynamic to say the whole entity's hitbox isn't a complete rectangular prism. Fyreboy5 (talk) 13:32, 8 February 2016 (UTC)

Ender Dragon Strategies
Maybe there could be a page where we could list our strategies on how to defeat the ender dragon. Exactly how, and in which specific version. (Before 1.9? After 1.9? Console?) Maybe you could give your strategy a title.

Maybe you pillar up to the crystals just to take off the iron bars (1.9 & Console). Perhaps you use beds to explode the dragon when it gets near(Before 1.9). Possibly just shoot the dragon when it gets near you(Before 1.9).

This page, I think, would be a good idea. I will make it when I perform myself a strategy. Fyreboy5 (talk) 13:57, 8 February 2016 (UTC)


 * Tutorials/Ender dragon slaying. – LauraFi -  talk  14:56, 8 February 2016 (UTC)

Follow the rules. Rule #1 on Wiki talk pages. No tutorials on other pages beside Tutorials. This is your 1st warning or your going to be banned from the wiki for Spamming. miner 23:26, 9 February 2016 (UTC)Miner


 * What? – LauraFi -  talk  02:45, 10 February 2016 (UTC)

Summoning not working?
Whenever I summon an Ender Dragon, it spawns, but it just sits there in place, spamming it's flying animation. I've attempted this with both a custom name and without one. Here's the command I've been using: /summon EnderDragon –Preceding unsigned comment was added by 99.236.140.211 (talk) at 22:22, 17 March 2016 (UTC). Please sign your posts with


 * So I looked into it; when you use, an ender dragon's  tag has its default value of 10, which is the harmless hovering animation you see.  So, use , with   set to any value but 10, and you should get a working dragon, though still without the health bar, which I think is by design.  I've clarified it a little in the article. – Sealbudsman talk/contr 03:46, 18 March 2016 (UTC)

Detailed resummoning information
I'm new to editing here, but I've used the Wiki as reference for a long time. Unfortunately I've often found it to be an incomplete or inaccurate reference given actual research and testing within the game. So for my first edit I thought it would be extremely useful for folks to know that blocks around the obsidian pillars are destroyed when the dragon is respawned. In my game we had attempted to create stairs up to the tops of the obsidian towers made of obsidian so that they would last across respawns, and they were eliminated, it seemed no matter how far away we built them. So we tested it and determined exactly what blocks are removed during a respawn. This is the sort of useful technical information that the wiki often contains, like what blocks the dragon removes when she flies through them, or how she attacks, but that is occasionally absent, so I thought I would help out.

I find very disheartening that my first edit, which was thoroughly researched and verified, was summarily undone with only the comment 'tutorial'. But it does seem to explain why so often critical information seems to be missing from the Wiki. Could someone explain? What is this wiki if not an accurate reference for Minecraft?

For convenience, here is the block of text I added, I would be interested in knowing where this sort information would appropriately be posted: During the re-spawning process a solid cylinder of blocks is cleared from the bedrock exit portal to 32 blocks above it, even creatively added bedrock is eliminated. Then the end crystals, obsidian towers, bedrock end crystal pedestals, and iron bar cages (where appropriate) are regenerated from Y level 0 to the bedrock pedestal even if they have been completely removed. An area of 21x21x21 blocks centered on each newly generated end crystal is cleared of any existing blocks. Again, even creatively added bedrock is wiped out of this area. DarkJMKnight (talk) 12:23, 28 April 2016 (UTC)
 * I've found this wiki to be reasonably accurate, as long as you remember that the main articles generally describe what something is without giving strategies for using it. Perhaps less so for Console and PE. The reason of "tutorial" for your revert probably isn't quite accurate, but the information doesn't really belong in this article.
 * The information about the portal would probably be more appropriate at End portal, and the pillars at Obsidian pillar. Then you could link to that information briefly from here, e.g. " This also regenerates the exit portal and obsidian pillars. ". The "even creatively added bedrock" bit isn't necessary, just say all blocks are removed and leave it at that.
 * BTW, I note your pillar information isn't quite accurate: the bounding box around the pillar is cleared from Y=66 up to the top of the pillar + 10, while only the pillar itself is regenerated from Y=0 to Y=65. Also, the 21×21×21 area is cleared before the pillar is respawned: the code goes "clear 21×21×21 (which also wipes out the top of the pillar), make explosion, regenerate pillar (which includes the bars if appropriate and crystal)". Anomie x (talk) 13:35, 28 April 2016 (UTC)

Does the Dragon Destroy Structure Blocks?
I think someone should test this. If the answer is yes, it should be listed as a bug on the Bug Tracker. Structure blocks were added in 1.10. Fyreboy5 (talk) 22:41, 14 June 2016 (UTC)

Dynamic Hitboxes shown with F3+B
I have taken screenshots of the ender dragon's dynamic hitboxes in the 1.11 snapshot 16w39c. Should I post the images?

Dragon bleeds when death}}
When i defeated the ender dragon on Pocket Edition 1.0}}, She bleed showing red particles. She's not an redstone dragon, Isn't she? Have i should respected ACB's M? –Preceding unsigned comment was added by 173.215.216.190 (talk) at 18:25, 12 November 2016 (UTC). Please sign your posts with


 * 1. I have an iOS device not an android device so I can't use the development versions.
 * 2. There are so many grammar mistakes in that.
 * 3. What does ACB have to do with M or this post?
 * 4. I don't know what you are talking about.
 * 5. Please remember to sign your posts on talk pages with ~
 * Thank you. And please make an account. Boorider7 (talk) 18:28, 12 November 2016 (UTC)


 * 1. ACB is:
 * Australian goverment
 * Classification Board
 * Classification Board


 * 2. The bleeding dragon Is in 0.17.0 –Preceding unsigned comment was added by 64.237.226.18 (talk) at 17:03, 13 November 2016 (UTC). Please sign your posts with