I was unable to find a recent bug report for this issue, so I hope I'm not creating clutter.
I am creating a map in the Nether to test out and build with all of the new features. Before 20w17a, I was able to set my spawn in the Nether using /spawnpoint command (with nothing dictating the Nether, to be clear) but now when I die I get taken back to the world spawn. I have also tried to use /spawnpoint in the End, and that too did not work. I figure it may have something to do with a fix to an exploit with the bed in the Nether allowing infinite respawns, though I am not too sure.
Thank you for your time, hopefully this gets fixed soon!
Attachments
Comments 3
Yeah, but with commands it shouldn't need those things. Setting your spawn in the Overworld with /spawnpoint doesn't require a bed.
I am unable to reproduce, the command works as expected in 20w22a in the Nether. Make sure the coordinates you give the command are valid and empty - if they are not, the game will tell you after dying.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
I'm not certain if this is intended but it could be due to the new spawn point object in the Nether and the End which is Weeping Obsidian (which needs charges to work).