You cannot set lit state of redstone torches using setblock, debug stick and BlockStateTag, to be to opposite of the situation it would be in
Using the debug stick, or using setblock, fill, etc. you cannot create redstone torches that are unlit, only when the block the torch is on/attached to is powered, in which case, making it lit becomes impossible.
This is inconsistent with every other powerable block, which you can create and alter to be powered, without it getting "corrected".
In order to do this with setblock or fill, replace a block with the same ID, in order to create such a block, eg replace a redstone lamp with redstone_lamp[lit=true] to create a lit redstone lamp, without redstone power. This does not work for redstone torches, which will change their lit state depending on the attached block's incomming redstone power.
Linked Issues
is duplicated by6
relates to4
Created Issue:
You cannot create unlit redstone torches using setblock and debug stick, except when the torch would be unlit as usual
using the debug stick, or using setblock, fill, etc. you cannot create redstone torches that are lit=false, only when the block the torch is on/attached to is powered (in which case, making a lit=true becomes impossible).
This is inconsistent with every other powerable block, which you can create and alter to be powered, without it getting "corrected".
in order to do this with setblock or fill, replace a block with the same ID, in order to create such a block, eg replace a redstone lamp with redstone_lamp[lit=true] to create a lit redstone lamp, without redstone power. This does not work for redstone torches, which will change their lit state depending on the attached block's incomming redstone power.
You cannot create unlit redstone torches using setblockanddebug stick, except when the torch would be unlit as usualYou cannot create unlit redstone torches using setblock, debug stick and BlockStateTag, except when the torch would be unlit as usual
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
relates to
using the debug stick, or using setblock, fill, etc. you cannot create redstone torches that are lit=false, only when the block the torch is on/attached to is powered(in which case, makingalit=truebecomes impossible).This is inconsistent with every other powerable block, which you can create and alter to be powered, without it getting "corrected".
in order to do this with setblock or fill, replace a block with the same ID, in order to create such a block, eg replace a redstone lamp with redstone_lamp[lit=true] to create a lit redstone lamp, without redstone power. This does not work for redstone torches, which will change their lit state depending on the attached block's incomming redstone power.Using the debug stick, or using setblock, fill, etc. you cannot create redstone torches that are unlit, only when the block the torch is on/attached to is powered, in which case, making it lit becomes impossible.
This is inconsistent with every other powerable block, which you can create and alter to be powered, without it getting "corrected".
In order to do this with setblock or fill, replace a block with the same ID, in order to create such a block, eg replace a redstone lamp with redstone_lamp[lit=true] to create a lit redstone lamp, without redstone power. This does not work for redstone torches, which will change their lit state depending on the attached block's incomming redstone power.
You cannotcreate unlitredstone torches using setblock, debug stick and BlockStateTag,except when the torch would be unlit as usualYou cannot set lit state of redstone torches using setblock, debug stick and BlockStateTag, to be to opposite of the situation it would be in
relates to
is duplicated by
relates to
When using the Debug Stick to change the shape property of any rail type to one of the ascending_ values, the rail drops as item if there is no supporting block.
The Debug Stick is supposed to change block states without updating the block to allow placing invalid states, however here this is not possible. Therefore the general rules "block states created using Debug Stick not working as intended" does not apply here because the Debug Stick is not able to create the block state in the first place.
Steps to Reproduce:
- Place down any type of rail block on flat ground, without other blocks nearby
- Use the Debug Stick to change the shape property to any of the ascending_ values
Expected & Experienced Results:
→
The rail breaks, and drops as item.
→
The rail would be set properly to the state value you are changing, and not break.
Video(s):
Notes
Thank you for your report!
We're tracking this issue in MC-141297, 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-141297, 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-141297, 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
Can confirm in 1.17 Release Candidate 1. By the way, this also applies to redstone torches. Looks like that last remark is already reported as MC-141297. Sorry, it's really hard to find bugs on blockstates for some reason.
Duplicate of MC-141297, please use the search function in the future.
Thank you for your report!
We're tracking this issue in MC-141297, 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 (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
The Bug
MC-141297 was fixed for setblock and fill command, but it still impossible to change the lit state of redstone torches using a debug stick.
How to reproduce
- Place a redstone torch
- Get a debug stick and right-click on the redstone torch with the debug stick
->
The redstone torch is still lit
Debug sticks are not supported, and bugs involving them will be marked as Won't Fix/Invalid.
Um, perhaps read? This is not only with debug sticks, debug sticks are only 1 of the ways to try and make an unlit redstone torch, hence why I did mention them, but it's not the sole way of getting this issue.
Well? Is this not a duplicate of
MC-122323?Oh, and by the way, you yourself commented on the issue: "Debug stick bugs won’t get fixed, as it’s not supported."
1. That one is solely about debug sticks unable to make it, this covers more.
2. I’m aware debug sticks aren’t supported, but again, I just listed them as it’s an alternate way of trying to achieve it.
Affects 19w07a
Affects 20w21a, can I request ownership?
Can confirm in 21w03a.
Can confirm in 21w05b.
In 1.16.5 when using:
/setblock <x> <y> <z> minecraft:redstone_wall_torch[facing=south,lit=false]
It will place a turned off torch for like .1 second but then it will turn on again. So I can confirm the issue in this version as well.
Can confirm in 21w10a. Video attached.
Can confirm for 1.17 Release Candidate 1.
Can confirm in 1.17.1.
Why was this closed as Won't Fix? The submitter mentioned the debug stick in the title, but it says the bug can occur even without the debug stick.
This stills affects 1.18.1, and isn't just limited to the debug stick. The /setblock command with the lit property set to false results in a lit torch. Why is this marked as won't fix?
Because it requires changing the redstone torch behavior quite a bit, I presume, and they don't want to risk breaking creations. (I'm the original reporter)
@Dhrainos my guess is that this would erquire them to change how redstone updates propagate, as they currently behave a bit differently from regular block updates.
That doesn't explain why repeaters, wires, comparators, lamps, etc. can all get set to powered, without source, just fine. It's just torches and rails (different report).
Relates to
MC-193404.Relates to
MC-255254and can confirm in 1.19.2 and 1.19.3-rc3Not really related to that; the redstone torch does set the state, but immediately changes the state to what the game would normally have it in as if manually placed,rather than just refusing to set the state.
Can confirm in 23w04a
The fix in 25w02a only applies when using /setblock or /fill, and does not work with a debug stick.