MCPE-181058When attempting to respawn, it shows a loading icon and never actually respawns you.
When some strange condition is met, trying to respawn after dying results in an endless loading screen icon. Stuck there forever while the world goes on. When it bugged for me, I had a raid going on and there was beacons and a naturally spawned warden from a shrieker.
Linked Issues
Attachments1
Created Issue:
When attempting to respawn, it shows a loading icon and never actually respawns you.
When some strange condition is met, trying to respawn after dying results in an endless loading screen icon. Stuck there forever while the world goes on. When it bugged for me, I had a raid going on and there was beacons and a naturally spawned warden from a shrieker.
Attachments1
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is cloned by
We've run into the same issue as MCPE-181058, but we have found a reliable way to reproduce this:
- Make a new singleplayer world in 1.21.22 (or use attached).
- Join the world with a second player for easier killing, but it also works in singleplayer using /kill.
- place a bed at x = 112 and one at x = 111.
- let the second player stand at the same x pos as the bed (see the attached picture)
- make them click the bed, destroy the bed, then kill them.
- observe that if the player & bed were at 111, they will respawn at world spawn.
- observe that if the player & bed were at 112, they will get stuck on the respawn screen.
From our further testing here are some more observations:
- if either X or Z coordinate is at or above 112 it will trigger the issue
- it's not a problem anymore if the other coordinate is -97 or below (-96 is still a problem)
- it doesn't seem to be very consistent, as in it doesn't seem to span a huge rectangle of chunks - but at least it seems to be chunk based.
- bed position doesn't matter, death position doesn't matter, only the position of the player when clicking the bed
- it happens on singleplayer worlds as well as singleplayer worlds that has friends join in them
- it does NOT happen in worlds that were created on dedicated servers while on said server
- it however does happen in worlds that were created in singleplayer and then copied to dedicated servers
- This seems to be an issue if the world spawn is at 0 0 (default), -1 0, 0 -1; but not at 1 0 or 0 1. (y always -60 in my test case) At least not in the areas previously identified.
I hope some of these infos help figure out where the issue is coming from, as it's currently a massive issue with a map we're making.
Here is a testrun, with one test per chunk. green chunks mean respawn worked, red chunks mean the player got stuck on the respawn screen. up is +x, right is +y, the gold block is 0 0, the raw gold blocks are the blocks on -1.
I've attached the same tests with different world spawn locations, they are labeled x_z by the respective spawnpoint.
I am unable to reproduce the issue. Could you please attach a video demonstrating it?
I don't know how to do that and I honestly don't really know how to replicate it either but it happened so...
Resolving as Cannot Reproduce based on previous comment.
If you are able to reproduce this in the future, feel free to create a new bug report and be sure to include steps in the Description,