-
Bug
-
Resolution: Unresolved
-
None
-
1.18.32, 1.20.0
-
None
-
Confirmed
-
Windows
-
1057115
Summary:
Bed block state, "occupied_bit", failing to detect accurate block state for both true & false states.
Steps to Reproduce:
- Place a bed
- Command: /testforblock <x><y><z> bed [ "occupied_bit" : false ]
- View command feedback
Expected Results:
The bed has successfully been detected with that exact block state since there isn't a player or villager occupying it.
Observed Results:
The bed at that location doesn't match that specific block state "occupied_bit" even when there isn't anyone laying in the bed.
Screenshots/Videos:
https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharing
Notes:
It comes back that the block did not match it's appropriate state, I've also tried with setting the Boolean to true, and lying down and it still did not detect. This is a bug I've been wanting to be resolved and I can't continue my project if this bug isn't fixed immediately sooner or later. As I'm trying to implement a system that detects if certain beds are occupied at the same time. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. This bug has been occurring ever since I've tried testing for this specific block state, which was before 1.19
- is duplicated by
-
MCPE-155521 Block State "occupied_bit" is not working as expected
- Resolved
- relates to
-
MCPE-168391 Block state predicates in commands do not work properly (unprovided states require default value)
- Open