Observer doesn't detect Respawn Anchor charges
The observer block cannot detect that the observer block has either gained or lost a charge.
Steps to reproduce:
- Place a respawn anchor.
- Place an observer with the detector towards the respawn anchor.
- Place redstone behind the observer.
- Charge the respawn anchor once. Notice no redstone pulse is emitted.
Linked Issues
relates to7
MCPE-53919Observers don't detect changes to Note BlocksConfirmedMCPE-30544Observer doesn't detect curved rail changing directionConfirmedMCPE-41074Observer not detecting netherwart growingConfirmedMCPE-46345Observers do not detect an entity entering/exiting a bed ConfirmedMCPE-36783Observers don't detect Pumpkin or Melon stem changesFixedMCPE-40843Observers not detecting hopper status changeFixedMCPE-61978Observer doesn't detect several block state changesConfirmedAttachments1
Created Issue:
Observer doesn't detection Respawn Anchor charges
The observer block cannot detect that the observer block has either gained or lost a charge.
Steps to reproduce:
- Place a respawn anchor.
- Place an observer with the detector towards the respawn anchor.
- Place redstone behind the observer.
- Charge the respawn anchor once. Notice no redstone pulse is emitted.
Changed Summary:
Observer doesn't detectionRespawn Anchor charges
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
Added Labels: vanilla-parity
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
Added Linked Issues:
relates to
Added ADO: 357275
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Changed ADO: 357275 → 357275, 321644
Added Linked Issues:
duplicates
Added Affects Versions: 1.16.0.63 Beta
Added Linked Issues:
relates to
Added Affects Versions: 1.16.20.54 Beta
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
Added Linked Issues:
relates to
Removed Linked Issues:
relates to
duplicates
Added Affects Versions: 1.16.40 Hotfix 1.16.100.55 Beta
Added Affects Versions: 1.16.201 Hotfix
Added Affects Versions: 1.17.10 1.17.20.22 Beta
Added Affects Versions: 1.18.31
The bug
Observers do not activate when the following changes happen:
- A campfire becomes a signal fire (hay block placed below)
- Adding an eye of ender to a portal frame
- Powering a door/trapdoor that's already open
- Fire catching on another face of a block
- Vines spreading to another face of a block
- Fences/panes/walls/iron bars changing connections
- Stairs changing shape
- Grass becoming snowy
- Adding/removing a music disc from a jukebox
- Adding/removing a book from a lectern
- Leaves distance changing (log placed nearby)
- Locking a repeater
- Note block changing instrument (block below changed)
- Note block getting powered
- Tripwire changing shape/connections
- Snow layers generating from snowfall
Related issues
- Hoppers getting powered:
MCPE-40843 - Pumpkin/melon stems moving:
MCPE-36783 - Nether wart growing: MCPE-41074
- Note blocks changing note: MCPE-53919
- Entering a bed: MCPE-46345
- Rail changing direction: MCPE-30544
- Respawn anchor charged: MCPE-75742
- Target block getting hit: MCPE-84391
- Kelp age changing: MCPE-179683
- Various fixed issues:
MCPE-14710
This bug breaks automatic respawn anchor machines that automatically fill the respawn anchor when dying.
I had the same problem. Using pressure plates in the area that you spawn should work well enough until this bug is fixed.
Affects 1.16.20.54 Beta
Affects 1.16.40 Hotfix.
Affects 1.16.100.55 Beta.
Affects 1.16.100.56 Beta.
Affects 1.16.100
Affects 1.16.200.56 Beta
Still affects 1.16.200 Oficial
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please make sure the ticket description contains the following information:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still an issue
Happens in 1.17.11
Affects 1.18.31.
Still an issue in 1.19.