According to source code obtained by decompiling Minecraft with MCP, End portal blocks (ID 119) are meant to disappear if placed in the End before defeating the Ender Dragon, and presumably stay in the End if placed after the dragon has died. Instead, when placing 119 in the End, it despawns immediately regardless of whether the boss has been defeated.
Attachments
Comments 7
According to the code, End portals are supposed to disappear from the End or Nether before the Ender Dragon has been killed, and stay afterward. However, they always disappear. The dragon's death is supposed to set bossDefeated to true, but it apparently only does so while it generates the exit portal.
I don't see the point. All it does is make it impossible for players in Creative to build their own portals. After looking at the code, this does appear to work as intended, but it actually is a problem. What if, due to another bug, a dragon doesn't spawn in the End in SMP? Is everyone supposed to just commit suicide and respawn in the Overworld?
If, due to a bug, the Enderdragon doesn't spawn in The End, then they should work on fixing that bug, rather than making a workaround for it. If they wanted the player to be able to make their own portals in The End, they'd give them a way to do it that doesn't involve cheats such as the /give command.
I agree that it would be nice to be able to make your own portals out of The End once you've defeated the Enderdragon. In general, it would be neat if they did more with The End overall, rather than it just being kind of a joke about the kind of game Minecraft isn't. However, as this appears to be Working as Intended, you should make a suggestion on the forum or subreddit.
Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
Please review the guidelines before reporting issues.
Even after staring a while to that source code, I fail to see the bug, please explain.