Java Edition:Occupied Bed

Beds are supposed to only be occupied when a player or a villager is sleeping on them. There have been several bugs that allow for permanently retaining the occupied:true block state when no entity is using the bed. Trying to sleep in a bed that is occupied will print the message "This bed is occupied". Looking at the bed with the F3 debug screen enabled will show the occupied block state.

Obtaining

Sleep Limbo Abuse

This section is a work in progress. 

Please help in the creation of this article by expanding or improving it.

With a sufficiently high ping, you can confuse the game into a state where the client thinks player is awake, while the server thinks player is sleeping.

If you then unload the chunk with the bed (by walking far enough away, for example), the game will wake you up (as you don't have a bed anymore), but, because the bed is unloaded, it remains occupied.

^[test] starting and ending ranges, and if this (at least at this point) is a bukkit only bug.

Zombie Waking Up Villager

From 19w11a to 19w14b (1.14 snapshots), a bed will stay occupied if a villager sleeping in it is woken up by a zombie.^[1]

Sleeping Villager

From 19w11a (a 1.14 snapshot) to 24w35a (a 1.21.2 snapshot), when lightning strikes near a sleeping villager, the villager will be converted into a witch and the bed will remain occupied.^[2]

Portals

From 21w17a (a 1.17 snapshot) to 1.19.3, entering a bed whilst riding an entity inside a portal would create a permanently occupied bed.^[3] This is due to an accidental change making the player sleep at the location of the vehicle in 21w17a instead of at the bed.

This works with all rideable entities and with both End and Nether portals, but will only work in the Overworld, as trying to sleep in either the Nether or the End will cause the bed to explode.

• 

  Simple setup to create permanently occupied beds.

See also

• Open Barrel

References