-
Bug
-
Resolution: Duplicate
-
None
-
1.20.0
-
None
-
Unconfirmed
-
Windows
Summary:
Bell block state, "toggled_bit", failing to detect accurate block state for both true & false states.
Steps to Reproduce:
- Place a bell
- Command: /testforblock <x><y><z> bell [ "toggled_bit" : true ]
- View command feedback
Expected Results:
The bell has successfully been detected with that exact block state since it has been toggled by a player in-game.
Observed Results:
The bell at that location doesn't match that specific block state "toggled_bit" even when it is rung by a player
Screenshots/Videos:
_https://drive.google.com/file/d/1Wx1uBv_sqy0XMD_QNvn_mbeNTkTY_KhT/view?usp=sharing_
Note:
This absence of a feature worked before the 1.20 update where simple block states were determined by numbers. However, this new update had broken yet another feature I had in plan for my game and it is not pleasant. All of the bedrock block states are leaving but staying for Java? I want this to restored to how it used to be if the block states that are listed on the bedrock website. It was the testing for the bed's "occupied_bit" state and now the bell states simply don't even work anymore. It already broke a feature from one of my games and I don't like how it's affecting it. Is minecraft Bedrock just going down to trash while Java is being upgraded?
- duplicates
-
MCPE-168391 Block state predicates in commands do not work properly (unprovided states require default value)
- Open