[MC-1257] Spawnpoint not set when used with /spawnpoint; bed-not-found error used. Created: 30/Oct/12  Updated: 20/Apr/20  Resolved: 09/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: Math Maniac Assignee: Unassigned
Resolution: Works As Intended Votes: 0
Labels: command_block, spawn
Environment:

Executable-Run Client on a Windows 7 version 6.1 PC.


Attachments: PNG File bug.png    
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

I used a command block to set all spawn points in 1-second intervals. When I died using /kill, I spawn on the world spawn and a message comes, saying "Your bed was missing or obstructed". I tried to reproduce this bug, but it doesn't give the same results.



 Comments   
Comment by Alexander Spielvogel [ 09/Nov/12 ]

just had the same issue without bed-not-found, the spawnpoint did not work and I was somewhere in the woods. Thanks for the hint Raphael, it was not working because a sign was in the spawnpoint.

Comment by Raphael [ 30/Oct/12 ]

More info would be nice. You said, youre using a commandblock which sets your spawnpoint every second? That way your spawnpoint is constantly moving around, unless youre not moving. That way as soon as it hits a block which isnt air it becomes invalid, but valid again if you move away from whatever block you were standing in. This would also explain why your results are different.

Comment by Math Maniac [ 30/Oct/12 ]

Yes; I made sure of that. However, it is below a fence and above a pinewood plank, if this also means anything.

Comment by Raphael [ 30/Oct/12 ]

If at any point the spawnpoint isn't air (that means grass, buttons, pressure plates, water etc.), Minecraft counts it as obstructed and resets it to the default one. Works as intended.
You always need to stand in two completly empty blocks.

Generated at Sun Jan 12 11:53:50 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.