Observer doesn't detect curved rail changing direction
Bug description
Observers cannot detect a corner rail switching its direction. This is because the rail state change does not cause a block update, which is required for observers in Bedrock to activate. I think rail-switching should cause block updates.
Steps to reproduce
- Build a rail intersection, with a corner rail placed on top of an observer whose output is facing downward into redstone wire directly below the observer.
- Power the corner rail using redstone. Notice that the observer doesn't activate.
- Unresolved
Zeb- 74
- 13
- Confirmed
- 135700
- Multiple
- block-update observer rail redstone
1.17.11 Hotfix - 1.21.51 Hotfix
1.17.11 Hotfix 1.17.20.23 Beta 1.17.20.22 Beta 1.17.10 1.16.210.60 Beta 1.16.100.58 Beta 1.16.100.57 Beta 1.16.100.56 Beta 1.16.100.55 Beta 1.16.20.54 Beta 1.16.20.53 Beta 1.16.0.67 Beta 1.16.0.63 Beta 1.16.0.55 Beta 1.16.0.53 Beta 1.16.0.51 Beta 1.15.0.56 Beta 1.15.0.55 Beta 1.15.0.54 Beta 1.15.0.51 Beta 1.14.30.51 Beta 1.14.2.51 Beta 1.14.2.50 Beta 1.14.0.51 Beta 1.13.3 1.14.0.4 Beta 1.13.1 1.14.1 Hotfix 1.14.0.3 Beta 1.14.0.2 Beta 1.14.0.1 Beta 1.13.0.18 Beta 1.2.9.1 1.2.10.1 1.5.3 1.6.0.30 Beta 1.7.0.9 Beta 1.12.1 1.13.0 1.14.1.2 Beta 1.14.30 Hotfix 1.16.1 1.16.40 Hotfix 1.16.201 Hotfix 1.17.30 1.18.2 Hotfix 1.19.31 Hotfix 1.20.51 Hotfix 1.21.44 Hotfix 1.21.51 Hotfix
Created Issue:
Observer doesn't detect rail-switching
Bug description
Observers cannot detect a corner rail switching its direction. This is presumably because the above state change does not cause a block update, which is required for observers in Bedrock to activate.
Steps to reproduce
- Build a rail intersection, with a corner rail placed on top of an observer whose output is facing downward into redstone wire directly below the observer.
- Power the corner rail using redstone. Notice that the observer doesn't activate.
1.14.0.1 also
1.14.0.2 also
1.14.0.3 also
1.14.0.4 also
1.14.0.51 and 1.13.3 also
Observer doesn't detect rail-switchingRail-switching doesn't cause block updates
Bug description
Observers cannot detect a corner rail switching its direction. This is
presumablybecause theabovestate change does not cause a block update, which is required for observers in Bedrock to activate.Steps to reproduce
- Build a rail intersection, with a corner rail placed on top of an observer whose output is facing downward into redstone wire directly below the observer.
- Power the corner rail using redstone. Notice that the observer doesn't activate.
Bug description
Observers cannot detect a corner rail switching its direction. This is because the rail state change does not cause a block update, which is required for observers in Bedrock to activate. I think rail-switching should cause block updates.
Steps to reproduce
- Build a rail intersection, with a corner rail placed on top of an observer whose output is facing downward into redstone wire directly below the observer.
- Power the corner rail using redstone. Notice that the observer doesn't activate.
1.14.1.2 also
1.14.2.50 and 1.14.1 hotfix also
Rail-switching doesn't cause block updatesObserver doesn't detect curved rail changing direction
relates to
1.14.2.51 also.
1.14.30.51 also
(Tested before reported - from 'Technical Bugs List' https://docs.google.com/document/d/1nziKYzCr4pBdCRj2gIMlfr9MVdWHd6HyafdiBHx9F0c/edit)
This issue happens in 1.14.30 hotfix and 1.15.0.51 also.
1.15.0.54 also
1.16.0.53 also
1.15.0.55 also
is duplicated by
Affects 1.16.0.67
1.16.0.55 also
1.16.0.63 also
Affects 1.16.1
Affects 1.16.20.53
relates to
is duplicated by
is duplicated by
Happens in 1.17.11.
I attechaed a new video and a picture.
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
Thank you for your report!
We're tracking this issue in MCPE-30544, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Upvoted. Can confirm, though I do not think that the bedrock edition is that much updated as the Java edition. I don't think they added that feature yet. Also I attached a clip of it.
Euan Jed Tabamo, I didn't see any attached clip (maybe your upload failed), so I made my own demonstration video and uploaded it.
Also, it should be noted that the basic behavior of observers in Java Edition and Bedrock is currently fundamentally different in the 2 codebases. In Java Edition, observers detect block state and ID changes, regardless of whether or not they cause a block update. In Bedrock, observers detect block updates, which are not caused by all state/ID changes in Bedrock currently, and block state changes are not the only thing that can cause block updates. (Actually, Bedrock technically doesn't have modern block states yet... just numeric metadata values, so I guess the proper term for Bedrock is "metadata/ID changes".) Coincidentally, the things that activate an observer in one codebase are almost the same in both codebases, but there are a few cases where the difference in functionality causes a difference in observable behavior.
In this case, the rail changes its metadata value, which I think SHOULD cause a block update, but currently does not in Bedrock, hence this bug report.
Affects 1.13 on windows 10 and xbox one
According to the Minecraft Wiki, observers detect block state changes on Java and block updates on Bedrock. This bug exists because rails do not create block updates when they re-orient.
This is actually intended, like Blobs said, observers in bedrock detect block updates, not state changes.
I guess the actual issue is that rail-switching doesn't cause block updates in the first place. (Though whether or not it should may be debatable.) I have updated the issue title and description to reflect this.
items are not generated in the chests of villages or other buildings and there is a bugs that when you take a lot of things from the creative they stay stuck and do not move from place until you leave the game that happens in version 1.16.0.63 help me please fix it
items are not generated in the chests of villages or other buildings and there is a bugs that when you take a lot of things from the creative they stay stuck and do not move from place until you leave the game that happens in version 1.16.0.63 help me please fix it
Affects 1.16.20.54 Beta
So, the problem is that it's not a block update, it's not the observers fault?
Affects 1.16.40 Hotfix.
Affects 1.16.100.55 Beta.
Affects 1.161.00.56 Beta.
Affects 1.16.100.57 Beta
Affects 1.16.100.58 Beta.
I think the developers should fix this with the Observer Block frankly :/
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
affects 1.17.20.23
Affects 1.17.30
Affects 1.18.2
Affects 1.19.20
Affects 1.19.31
Confirmed in 1.21.44