mojira.dev
MCPE-176877

When the old world is not loaded into the area where the new world spawn point is located, the new world spawn point will be loaded after update, and the player can only spawn in this new spawn point

This tends to happen in seeds from New World spawn point far away from Old World spawn point.For example, 843417916 and so on.

The change of spawn location of also adds a lot of trouble.

Comments 5

Please give numbered steps to reproduce this issue.

Take the seed: 843417916 as an example,                

The coordinates of spawn point in the old world are: x=1864,z=4;
In the new world, the coordinates of spawn point are: x=-16,z=16.

It can be seen that the two spawn points are far apart.

To observe this problem, we should first create and enter an old world in version 1.17.x and before, then determine the location of the spawn point (by returning to Overworld from the End), and at the same time ensure that the area where the spawn point in the new world is located is not loaded, then update the world to version 1.18.x and later, and return to the spawn point again in the same way, and it will be transmitted to the spawn point in the new world.

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Does the issue still reproduce in latest version? Does this happen only on certain World?

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues) – 📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Does the issue still reproduce in latest version? Does this happen only on certain World?

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues) – 📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

YangYe

(Unassigned)

Unconfirmed

Android

Android10

1.20.41 Hotfix

Retrieved