<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 14:53:48 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MCPE-11869] Redstone Torches placed on Redstone blocks do not emit a one tick signal</title>
                <link>https://bugs.mojang.com/browse/MCPE-11869</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;I was attempting to make a 1- tick clock with torch repeaters, and attempted to start it off with a one tick pulse supplied by a redstone torch placed on top of a redstone block.&lt;/p&gt;

&lt;p&gt;What I expected: A one tick signal to run through the connected redstone wire, as in the Java version&lt;/p&gt;

&lt;p&gt;What happened: The torch flicked on for a very short amount of time and did not power the redstone wire at all.&lt;/p&gt;

&lt;p&gt;To replicate: place a redstone block level with the ground. Run a redstone line away from the redstone block, but not on top of the block. Place a torch on top of the redstone block.&lt;/p&gt;

&lt;p&gt;To any moderators: If there are any criteria I did not meet, please notify me in the comments/reply section&lt;/p&gt;

&lt;p&gt;NOTE: This does not occur in the PC release of the game&lt;/p&gt;</description>
            <key id="127810">MCPE-11869</key>
            <summary>Redstone Torches placed on Redstone blocks do not emit a one tick signal</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                            <reporter username="Mario22qwerty">Cameron Young</reporter>
                        <labels>
                            <label>redstone</label>
                    </labels>
                <created>Sat, 28 Nov 2015 02:28:51 +0100</created>
                <updated>Mon, 30 May 2016 08:53:36 +0200</updated>
                            <resolved>Mon, 30 May 2016 08:53:36 +0200</resolved>
                                    <version>0.13.0</version>
                                    <fixVersion>0.14.3</fixVersion>
                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="308467" author="depressed-pho" created="Mon, 30 May 2016 08:53:36 +0200"  >&lt;p&gt;Yes, it&apos;s now fixed. I don&apos;t know the exact version in which the bug got fixed though.&lt;/p&gt;</comment>
                            <comment id="308224" author="drawesome4333" created="Sun, 29 May 2016 07:24:37 +0200"  >&lt;p&gt;Fixed in 0.14.3 or below&lt;/p&gt;</comment>
                            <comment id="270207" author="depressed-pho" created="Fri, 4 Dec 2015 05:18:48 +0100"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-11953&quot; title=&quot;Redstone torch timings are off by half a tick&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-11953&quot;&gt;&lt;del&gt;MCPE-11953&lt;/del&gt;&lt;/a&gt; might explain why the NOT-AND-clock circuit in MCPE does not work in the Java version. Torches should not respond to pulses shorter than 1.5 ticks in the first place...&lt;/p&gt;</comment>
                            <comment id="269580" author="mario22qwerty" created="Wed, 2 Dec 2015 01:45:15 +0100"  >&lt;p&gt;I have a new development: The circuit that proves torches work as intended does not work in the Java (PC) version of the game. The components used are all currently implemented in the Pocket/Windows 10 edition of the game. The Java circuit is in both screenshots, on the left of SideBySide.png and the main feature of Javacircuit.png. The java circuit reacts differently than the windows 10 version, proving that torches do not line up with one tick.&lt;/p&gt;

&lt;p&gt;Edit: I have tested a one- tick PC redstone torch with an old style two-torch repeater. It seems that the NOT gate is reacting to the torch much like the redstone wire in Pocket Edition, in that the &quot;repeater&quot; does not respond to the visibly powered torch and connected wire&lt;/p&gt;

&lt;p&gt;Edit: Sadly, i cannot add a screenshot, as the moment of all three things happening at the same time is very small, and would require very precise timing to capture.&lt;/p&gt;</comment>
                            <comment id="269574" author="mario22qwerty" created="Wed, 2 Dec 2015 01:22:59 +0100"  >&lt;p&gt;I have replicated your circuit for torch taking one tick to turn off, but instead of a side- block torch, I substituted it for a top of block torch, and the results remained the same. I ran this in order to test whether or not the behavior of torches differed based upon their orientation, as with  &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-11855&quot; title=&quot;Redstone works funny &quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-11855&quot;&gt;&lt;del&gt;MCPE-11855&lt;/del&gt;&lt;/a&gt;&apos;s oddities. Screenshot: Replicatedcircuit.png  &lt;/p&gt;</comment>
                            <comment id="269573" author="mario22qwerty" created="Wed, 2 Dec 2015 01:07:05 +0100"  >&lt;p&gt;I can confirm that the door does make the opening sound, as well as the closing sound on WIndows 10 64 bit&lt;/p&gt;</comment>
                            <comment id="269572" author="mario22qwerty" created="Wed, 2 Dec 2015 01:03:01 +0100"  >&lt;p&gt;With your torch and-gate experiment, would the AND gate not add a delay to the circuit? I feel that if you added torches of any kind to the circuit, it should cause the pulse to be thrown out if too short, due to it not satisfying the delay. With your circuit as-is, the torches could be adding up to a one tick delay from the existing, incorrect delay that you proved exists, but is less than one tick in the Door test.&lt;/p&gt;</comment>
                            <comment id="269464" author="depressed-pho" created="Tue, 1 Dec 2015 17:50:08 +0100"  >&lt;p&gt;I investigated this further. First, I wanted to know if the torch put on the redstone block produces any pulse no matter how short it is, so I connected it to a door (shown in &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/105896/105896_pulse-detector-using-a-door.png&quot; title=&quot;pulse-detector-using-a-door.png attached to MCPE-11869&quot;&gt;pulse-detector-using-a-door.png&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://bugs.mojang.com/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;) to see if the door produces any sound when the torch is put. To my surprise, the door &lt;b&gt;did&lt;/b&gt; produce a sound while it did so without any visible changes. This means the torch emitted a pulse whose length is shorter than 1 tick, otherwise it would initiate the torch clock.&lt;/p&gt;

&lt;p&gt;Then I built a circuit shown in &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/105897/105897_torch-taking-1-tick-to-turn-off.png&quot; title=&quot;torch-taking-1-tick-to-turn-off.png attached to MCPE-11869&quot;&gt;torch-taking-1-tick-to-turn-off.png&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://bugs.mojang.com/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt; to see if torches take exactly 1 tick to turn off in the general case. It has an AND gate where one of its input is directly connected to a button and another is negated by a torch. When the button is pushed, there will be 1 tick of moment where both inputs being high &lt;b&gt;if and only if&lt;/b&gt; the torch takes 1 tick to turn off, producing a 1 tick pulse from the AND gate and thus initiates the clock connected to its output. The result was that the clock did get initiated so the turning-off delay was proven to be 1 tick, at least in this setup.&lt;/p&gt;</comment>
                            <comment id="269355" author="mario22qwerty" created="Mon, 30 Nov 2015 23:29:11 +0100"  >&lt;p&gt;The odd thing is, with the Burnout torch clock (which I will add once I figure a way to) the delay seems present, even to a point of too much of a delay, as the torches alternate so evenly that the top wire will stay continuously powered throughout the cycles. More torches added just continue their neighbor&apos;s activity&lt;/p&gt;


&lt;p&gt;Edit: I actually may make this a separate report after checking to see if it has been reported before or not.&lt;/p&gt;

&lt;p&gt;Edit: I have created a separate report for this issue labeled &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-11906&quot; title=&quot;Redstone Torches hold a steady signal instead of creating a burnout clock&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-11906&quot;&gt;&lt;del&gt;MCPE-11906&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="269353" author="depressed-pho" created="Mon, 30 Nov 2015 23:05:02 +0100"  >&lt;p&gt;Aha, I had forgotten that 1-tick delay. You are right Cameron, this is indeed a bug.&lt;/p&gt;</comment>
                            <comment id="269331" author="mario22qwerty" created="Mon, 30 Nov 2015 22:04:47 +0100"  >&lt;p&gt;(scorethrough)To respond to your comment PHO, if i&apos;m not mistaken, Redstone torches do introduce a delay of one tick to any circuit that they are added to, since they definitely aren&apos;t instantaneous (such as Redstone wire). I will soon put up a specific test/example(/scorethrough)&lt;br/&gt;
Edit:&lt;br/&gt;
A minor possible oversight: Since redstone torches add a delay of one tick to circuits, how would the clock circuit be a one-tick clock? with four torches, the delay would be 4 ticks. This would mean that the pulse of the redstone dust would have to overcome the threshold of four ticks in order to carry through the clocks. Either the system is Very broken, or I feel that we might have stumbled a bit with the one-tick notion (the latter being more likely)&lt;/p&gt;</comment>
                            <comment id="268830" author="depressed-pho" created="Sat, 28 Nov 2015 08:01:45 +0100"  >&lt;p&gt;Hmm... The moment when the torch on the redstone block tries to power the wire &lt;b&gt;and&lt;/b&gt; the torch gets activated (and thus turned off) by the redstone block are in exactly the same tick, right? If so, the circuit itself can be considered very unreliable. Even in the PC version the behavior can change between versions I assume...&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="132568">MCPE-12776</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="105726" name="AfterTorch.png" size="442607" author="Mario22qwerty" created="Sat, 28 Nov 2015 02:28:51 +0100"/>
                            <attachment id="105727" name="BeforeTorch.png" size="639264" author="Mario22qwerty" created="Sat, 28 Nov 2015 02:28:51 +0100"/>
                            <attachment id="105728" name="IsolatedBug.png" size="704013" author="Mario22qwerty" created="Sat, 28 Nov 2015 02:28:51 +0100"/>
                            <attachment id="105909" name="Javacircuit.png" size="1074930" author="Mario22qwerty" created="Wed, 2 Dec 2015 01:41:47 +0100"/>
                            <attachment id="105905" name="Replicatedcircuit.png" size="958564" author="Mario22qwerty" created="Wed, 2 Dec 2015 01:23:25 +0100"/>
                            <attachment id="105908" name="SideBySide.png" size="1319772" author="Mario22qwerty" created="Wed, 2 Dec 2015 01:41:47 +0100"/>
                            <attachment id="105896" name="pulse-detector-using-a-door.png" size="1513358" author="depressed-pho" created="Tue, 1 Dec 2015 17:50:08 +0100"/>
                            <attachment id="105897" name="torch-taking-1-tick-to-turn-off.png" size="1680512" author="depressed-pho" created="Tue, 1 Dec 2015 17:50:08 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Windows 10, 64 bit ( Bug also noticed on android Lenovo Tab S8 50f, same version)</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10901"><![CDATA[Windows]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0kjsv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>