MCPE-40467Player spawns at wrong position when reloading "Old"-type world
When loading an "Old"-type (limited) world, the player sometimes respawns a short distance away from where they were when they saved the world. When it happens, either their X or Z coordinate, whichever is closest to a chunk boundary, is changed to put them in a block next to that boundary on its eastern or southern side. Fractional position is significant in calculating which chunk boundary is closest.
The bug may not always be triggered, but is triggered pretty consistently in the attached test world. It has not been reported in "Infinite" or "Flat"-type worlds, but that possibility cannot be eliminated.
Steps to reproduce:
Import the sample world TestworldRespawn.mcworld and load it.
Expected results:
The player spawns at X=60.3372, Y=94.62, Z=60.6899 (the coordinates recorded as the player position in the saved world files).
Observed results:
The player spawns at X=60, Y=94, Z=63.
Special notes
- This issue was originally reported by Karla Maenlest in comments to
MCPE-38374. After a while, the mods concluded that it only occurred in old-type worlds and was therefore a separate issue, leading us to create this report to track it. - Karl created the test world and made a substantial and careful effort to explore the details of the bug (many thanks, Karl!). His comments, starting here, might well contain additional important information. In particular, the image he included in this comment helps clarify how the player spawn point gets moved.
- The test world was created with Experimental Gameplay enabled. It is unknown whether this has any effect, but it should be considered as a possible trigger for the bug.
Linked Issues
Attachments1
![[MCPE Mod] Auldrick](../../../data/avatars/users/10122.svg){kind=small}
Created Issue:
Player spawns at wrong position when reloading "Old"-type world
When loading an "Old"-type (limited) world, the player sometimes respawns a short distance away from where they were when they saved the world. When it happens, either their X or Z coordinate, whichever is closest to a chunk boundary, is changed to put them in a block next to that boundary on its eastern or southern side. Fractional position is significant in calculating which chunk boundary is closest.
The bug may not always be triggered, but is triggered pretty consistently in the attached test world. It has not been reported in "Infinite" or "Flat"-type worlds, but that possibility cannot be eliminated.
Steps to reproduce:
Import the sample world TestworldRespawn.mcworld and load it.Expected results:
The player spawns at X=60.3372, Y=94.62, Z=60.6899 (the coordinates recorded as the player position in the saved world files).Observed results:
The player spawns at X=60, Y=94, Z=63.Special notes
- This issue was originally reported by Karla Maenlest in comments to
MCPE-38374. After a while, the mods concluded that it only occurred in old-type worlds and was therefore a separate issue, leading us to create this report to track it.- Karl created the test world and made a substantial and careful effort to explore the details of the bug (many thanks, Karl!). His comments, starting here, might well contain additional important information. In particular, the image he included in this comment helps clarify how the player spawn point gets moved.
- The test world was created with Experimental Gameplay enabled. It is unknown whether this has any effect, but it should be considered as a possible trigger for the bug.
Attachments1
When loading an "Old"-type (limited) world, the player sometimes respawns a short distance away from where they were when they saved the world. When it happens, either their X or Z coordinate, whichever is closest to a chunk boundary, is changed to put them in a block next to that boundary on its eastern or southern side. Fractional position is significant in calculating which chunk boundary is closest.
The bug may not always be triggered, but is triggered pretty consistently in the attached test world. It has not been reported in "Infinite" or "Flat"-type worlds, but that possibility cannot be eliminated.
Steps to reproduce:
Import the sample world TestworldRespawn.mcworld and load it.Expected results:
The player spawns at X=60.3372, Y=94.62, Z=60.6899 (the coordinates recorded as the player position in the saved world files).Observed results:
The player spawns at X=60, Y=94, Z=63.Special notes
- This issue was originally reported by Karla Maenlest in comments to
MCPE-38374. After a while, the mods concluded that it only occurred in old-type worlds and was therefore a separate issue, leading us to create this report to track it.- Karl created the test world and made a substantial and careful effort to explore the details of the bug (many thanks, Karl!). His comments, starting here, might well contain additional important information. In particular, the image he included in this comment helps clarify how the player spawn point gets moved.
- The test world was created with Experimental Gameplay enabled. It is unknown whether this has any effect, but it should be considered as a possible trigger for the bug.
When loading an "Old"-type (limited) world, the player sometimes respawns a short distance away from where they were when they saved the world. When it happens, either their X or Z coordinate, whichever is closest to a chunk boundary, is changed to put them in a block next to that boundary on its eastern or southern side. Fractional position is significant in calculating which chunk boundary is closest.
The bug may not always be triggered, but is triggered pretty consistently in the attached test world. It has not been reported in "Infinite" or "Flat"-type worlds, but that possibility cannot be eliminated.
Steps to reproduce:
Import the sample world TestworldRespawn.mcworld and load it.Expected results:
The player spawns at X=60.3372, Y=94.62, Z=60.6899 (the coordinates recorded as the player position in the saved world files).Observed results:
The player spawns at X=60, Y=94, Z=63.Special notes
- This issue was originally reported by Karla Maenlest in comments to
MCPE-38374. After a while, the mods concluded that it only occurred in old-type worlds and was therefore a separate issue, leading us to create this report to track it.- Karl created the test world and made a substantial and careful effort to explore the details of the bug (many thanks, Karl!). His comments, starting here, might well contain additional important information. In particular, the image he included in this comment helps clarify how the player spawn point gets moved.
- The test world was created with Experimental Gameplay enabled. It is unknown whether this has any effect, but it should be considered as a possible trigger for the bug.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
Karla Maenlest: We have decided to track the behavior you reported in Old-type worlds as a separate issue, MCPE-40467. If you were watching this report, you might wish to watch that one instead or in addition. Again, thank you for your extensive and careful experimentation!
This problem no longer occurs in the sample world when imported into 1.11.0.5 Beta.
This problem no longer occurs in the 1.10.0.1 release.