MC-74211Door placed in spawn protection only half disappears
When a non-op user tries to place a door in the spawn protection, the door only half disappears. This is a client side only bug. The other users can't see the half door, only the player who originally placed it can.
Linked Issues
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
Created Issue:
Door placed in spawn protection only half disappears
When a non-op user tries to place a door in the spawn protection, the door only half disappears. This is a client side only bug. The other users can't see the half door, only the player who originally placed it can.
Environment
windows 8
windows 8
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
relates to
When a non-op user tries to place a door in the spawn protection, the door only half disappears. This is a client side only bug. The other users can't see the half door, only the player who originally placed it can.
When a non-op user tries to place a door in the spawn protection, the door only half disappears. This is a client side only bug. The other users can't see the half door, only the player who originally placed it can.
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
Sounds like a server plugin might be causing this issue, contact a server administrator or inform the plugin creator about the problem.
Its a vanilla server. There are no plugins.
is this still reproduceable?
Does this still happen in 1.8.8/15w31c? If so, please update the Affected Versions field.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.
Cannot reproduce in 20w51a.
I am still able to reproduce this issue in 21w14a. I've attached a screenshot.
Can confirm in 1.18.1.
Can confirm in 1.18.2.
This issue was present in 1.18.2, but no longer occurs in versions above or equal to 22w11a. With that being said, this issue has been fixed in 22w11a.