MC-67930Doors Not Unpowered Using Commands With Replace
When powering doors by placing a Redstone Block/Torch/et cetera adjacent to them, the doors are not unpowered when the block is removed via commands using the replace function. They properly become unpowered when using the destroy function, however. This applies to all doors, trapdoors, and fence gates.
Steps To Reproduce:
1) Place any two doors.
2) Place one Redstone Block next to each door.
3) Remove one Redstone Block using /setblock ~ ~ ~ air 0 replace.
4) Remove the other using /setblock ~ ~ ~ air 0 destroy.
Step three will not unpower the door. Step four will. Other redstone devices work correctly- as far as I've tested- and unpower upon removal.
Created Issue:
Doors Not Unpowered Using Commands With Replace
When powering doors by placing a Redstone Block/Torch/et cetera adjacent to them, the doors are not unpowered when the block is removed via commands using the replace function. They properly become unpowered when using the destroy function, however. This applies to all doors and trapdoors.
Steps To Reproduce:
1) Place any two doors.
2) Place one Redstone Block next to each door.
3) Remove one Redstone Block using /setblock ~ ~ ~ air 0 replace.
4) Remove the other using /setblock ~ ~ ~ air 0 destroy.Step three will not unpower the door. Step four will. Other redstone devices work correctly- as far as I've tested- and unpower upon removal.
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)When powering doors by placing a Redstone Block/Torch/et cetera adjacent to them, the doors are not unpowered when the block is removed via commands using the replace function. They properly become unpowered when using the destroy function, however. This applies to all doors
andtrapdoors.Steps To Reproduce:
1) Place any two doors.
2) Place one Redstone Block next to each door.
3) Remove one Redstone Block using /setblock ~ ~ ~ air 0 replace.
4) Remove the other using /setblock ~ ~ ~ air 0 destroy.Step three will not unpower the door. Step four will. Other redstone devices work correctly- as far as I've tested- and unpower upon removal.
When powering doors by placing a Redstone Block/Torch/et cetera adjacent to them, the doors are not unpowered when the block is removed via commands using the replace function. They properly become unpowered when using the destroy function, however. This applies to all doors, trapdoors, and fence gates.
Steps To Reproduce:
1) Place any two doors.
2) Place one Redstone Block next to each door.
3) Remove one Redstone Block using /setblock ~ ~ ~ air 0 replace.
4) Remove the other using /setblock ~ ~ ~ air 0 destroy.Step three will not unpower the door. Step four will. Other redstone devices work correctly- as far as I've tested- and unpower upon removal.
Using setblock replace does not actually create a block update.
However, this also may be caused because of
MC-26739I'll have to test if this behaves differently from using /fill to replace a single block, in that case it might be a bug that needs fixing
So replace is supposed to do a block update?
I'm not sure, tbh. But /setblock and /fill should have the same behavior, so I'll compare them and then decide if this needs to be fixed.
As far as I can tell, the behavior is the same using /fill- which is the command I actually want to use it with- /setblock, and /clone. The issue is the replace does update redstone, like Redstone Lamps, Redstone Wire, et cetera, except doors. You can power doors using replace, but you cannot depower them. You can depower the other redstone related blocks.
The case for which I need it is opening and closing two adjacent sets of double doors. I planned on using /fill replace on the floor underneath to switch between Red Stained Hardened Clay and Redstone Blocks. The doors open when the floor is replaced with Redstone Blocks, but do not close when replaced with Red Stained Hardened Clay.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.