hmuller
- Cpt_Obvious
- cpt_obvious
- Europe/Stockholm
- Yes
- No
The search terms used prior to bug creation:
project = MC AND (summary ~ "end" OR summary ~ "bed") AND (status = Open OR resolution not in (Duplicate, Invalid, Incomplete)) ORDER BY created DESC, affectedVersion
Issue:
While in a hardcore survival world in I observed item frames (and their contents), an armor stand, and nearby villagers go missing (or become invisible) upon reentry to a nearby bed spawn when coming from the End.
This does not seem to happen during normal bed sleeping, or when the bed spawn is very far from the item frames, armor stand, and villagers.
I have not tested for this bug in previous snapshots or in version 1.13.2 or lower.
To duplicate:
- Create a new world, survival mode with cheats, any seed
- Create a simple box structure
- Within and along one of the interior walls, place item frames with objects, an armor stand with armor, and villagers
- place a plain white bed 4 blocks away from that wall and parallel to it
- /locate the Stronghold
- find the End Portal and activate it
- enter the End
- approach the End Dragon and allow it to kill you, OR kill the End Dragon and return from the End Exit Portal
Upon your return to the Overworld bed spawn, you will observe that the item frames with objects, armor stand with armor, and villagers are missing. Although you may hear villagers.
This is temporary, to correct the problem save and exit the game, then restart the game. The objects and villagers will be present and visible as expected.
hmuller I'm not so sure that this bug - 'obsidian platform coordinates entered as default in dragonkill-generated + on outer islands naturally existing end gateways' - and 'outer islands around the ~1k mark aren't generating anymore' are linked (unless both are intentional, as speculated below), however I am fairly certain that MC-141823 and outer islands around the 1k mark not generating anymore are related.
But you raise a very good argument here - Shouldn't "outer islands around 1k mark aren't generating anymore" get an own bugpost? (Question to the moderators here.)
(As soon as that would be fixed, MC-141823 should be automatically fixed, too, potentially.)
This is only extreme speculation, but maybe they are changing up the end cities/outer islands as for their optics and/or content, and thus have intentionally entered the obsidian spawn platform as teleport destination for the time being while they are still not finished with re-coding those end cities/outer islands. Wishful thinking though, likely ![]()
Let's just wait and see, if this is still not fixed in the first 1.14 prerelease, we'll somehow make sure that we know that the Devs have at least taken notice of this ![]()







Same issue with seed: -1504342332604097644
Stronghold End Portal is at: (-1433, 30, 680)
The issue occurs in Snapshot 18w43c and thereafter, it is not present in Snapshot 18w43b and older (and not in 1.13.2).
As Brad Corbin commented, the issue still occurs in 19w02a, has been broken since 18w43c. It is commonly believed that this bug is a side effect of End Cities not generating.
Confirmed Pierrot's comment. I normally play at a view/render distance of 10 chunks. After setting it to 12 chunks, the Ender Dragon spawns as expected, and it is therefore no longer necessary to go to 0 ~ 0 (or near) to cause it to spawn.
In response to Meri (thank you for your investigation!), the help that your describe in your comments would seem to be only applicable to cases where End Cities have generated. In my case the /locate command produces coordinates, but when /tp to the same coordinates there is nothing there but Void and death =).
As Doctor5555 and NeunEinser have indicated, /setblock is a fair workaround to get the End Gateway to do something other that put you back at the End spawn platform. But that still does not help if the End Cities have not generated.
I only add that information to highlight that it would appear that this bug and End Cities not generating are linked.
Thank you Oval. I search first before I create a bug, because there is no point in duplicating work:
summary ~ "end gateway*" OR description ~ "end gateway*" ORDER BY created DESC, lastViewed ASC
That search did not find that bug. Please do not assume the reporter did not search.
my bad, I didn't scroll far enough down.
my bad, I didn't scroll far enough down.
Just a data point on the End City generation distance. As of 19w05a, seed -1504342332604097644 has two known End Cities generated at the coordinates:
(48, ~, -1200)
(736, ~, -1232)
This is closer in than the previous snapshots (which put the End Cities beyond the 15K mark for this seed), but still apparently too far out for the current End Gateway code to reach.
Bartosz, Yes - Adding to Meri's, thanks for that communication, it eliminates the need to comment.
Attachments 2019-02-09_13.04.44.png and 2019-02-09_13.12.36.png show the state of the objects and villagers prior to entry to the End.
Attachment 2019-02-09_13.04.27.png shows the state of the objects and villagers after reentry to the bed spawn from the End.
Attachment 2019-02-09_13.42.08.png added for F3 data if required.
Bob, when playing at a render distance of 10, I had plenty of mobs. The only mob that was not spawning was the ender dragon, unless I travelled near 0 ~ 0 in the End. Setting render distance to 12 eliminated that necessity.
I am running Debian Bullseye (testing). To identify the pango libraries in use I ran the following:
The above shows that the launcher depends on the following individual pango libraries:
I modified the control file of the current Minecraft launcher (2.1.13829) debian package file (Minecraft.deb) accordingly and it runs without problems.
The contol file I used is attached. The minimum version number I used for the three libraries is the current version used for Debian Jessie (1.36.8-3)
control