MCPE-28749Redstone torch burnouts suddenly re-burnouts randomly
If you create what it is called a redstone torch burnout clock, it should burn out and turn both redstone dust and redstone torch off. However, somtimes the clock re-burnouts randomly, which basically means that once the clock is burn outed, it has a chance to re-burn out.
To recreate this, simply make a redstone torch burn-out clock. It will burn out once the circuit is complete. Then wait untill it re-burn outs.
Linked Issues
Attachments1
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Created Issue:
Redstone torch burnouts suddenly re-burnouts randomly
If you create what it is called a redstone torch burnout clock, it should burn out and turn both redstone dust and redstone torch off. However, somtimes the clock re-burnouts randomly, which basically means that once the clock is burn outed, it has a chance to re-burn out.
To recreate this, simply make a redstone torch burn-out clock. It will burn out once the circuit is complete. Then wait untill it re-burn outs.
relates to
Screenshot_2.png
![[Mod] bemoty](../../../data/avatars/users/50554.png){kind=small}
This is normal. Even in java.
The redstone torches are meant to reactivate after a random amount of time
I can not buy masks of strange things in the edition minecraft windows 10, when I click on get coins there is an error saying that it was not possible to connect to the store. How about checking your internet connection. And it is not only here that this happened, my friend also tested and could not buy, I can make any purchase in the Microsoft store, only in the minecraft store that I can not.
This issue with redstone torches was fixed in Java some time ago (reference) so it could well be a change that is deemed necessary in Bedrock also.
João Lucas Santos Santana - Please do not add unrelated comments and attachments to tickets. For help and support please contact Mojang Customer Support directly.
thank you
Reopened - this was fixed in the 1.2.10.1 BETA, but the fix wasn't included in 1.2.10.2.