MCPE-171919/testforblock fails to detect bed block state "occupied_bit"
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
Created Issue:
Bed Block State "occupied_bit" isn't working as expected
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
Video Link: https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharing
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 11
- 1.20.0
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
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"(false) even when there isn't anyone laying in the bed.
Video Link: https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharing
Bed Block State "occupied_bit"isn't working as expected
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
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"(false) even when there isn't anyone laying in the bed.
Video Link: https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharing
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
Reproduce Steps:
- 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"(false) even when there isn't anyone laying in the bed.
Video Link: https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharing
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
Reproduce
Steps:
- 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"(false) even when there isn't anyone laying in the bed.
Video Link: https://drive.google.com/file/d/1GYiKPP8pOHOTBGotak-b9lDDbhHy0_BH/view?usp=sharingSo there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution. I hope this can get fixed soon.
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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. I can't stress enough as I've done tons of research for this problem and found absolutely no solution.I hope this can get fixed soon.So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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. 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
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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.19Summary:
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"(false) 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
Summary:
So there is a bug that I've been urging to get fixed that's required for a special project that I have been working on. It consists of the one of the bed block states, "occupied_bit" becoming inaccurate and not working as expected. Although I run the following command:
/testforblock 0 -60 0 bed [ "occupied_bit" : false ]
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"
(false)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.19Summary:
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
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
BedBlockState "occupied_bit"/testforblock fails to detect bed block state "occupied_bit"
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Also to mention one of the other Block states, "head_piece_bit" has the exact same issue. Exclusively after doing tons of research, all of the sources repeatedly claim that these block states are available to both Java & Bedrock, whilst Java I'd believe to have the only current functions of these commands. So would this reason still apply for that block state as well?
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
![[Mod] Umija5895M](../../../data/avatars/users/10122.svg){kind=small}
relates to
relates to
relates to
Changing resolution to duplicate of MCPE-171919 where I have confirmed the issue.
Testing for ["occupied_bit" : true] is never successful.
Testing for ["occupied_bit" : false] is always successful for the bed foot, and always fails for the head.
Having a villager or player sleeping in the bed makes not difference at all.
I believe "occupied_bit" does not work in block state commands for beds because beds have never had an occupied bit in Bedrock Edition. It's a Java Edition feature. I would resolve this report as a feature request except that the option actually exists in the command, and that makes it a bug.
It only works when you also specify the "head_piece_bit"=true/false". "direction" also doesn't work without it. Moreover, only when the bed is occupied by a player, it can be detected, it doesn't work with villagers.