<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 14:54:08 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-11953] Redstone torch timings are off by half a tick</title>
                <link>https://bugs.mojang.com/browse/MCPE-11953</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;In PC, redstone torches change state when the block they are attached to has a change in signal longer than 1 tick (except for when that change in state is caused by the redstone torch itself, i.e. a short-circuit). In PE however, torches can change state when the block they&apos;re attached to has a signal change of 1 tick. The video demonstrates two examples of this in both PE (MCW10) and PC.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=8vNeAsOgeyk&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.youtube.com/watch?v=8vNeAsOgeyk&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;To fix:&lt;/b&gt; torches should &lt;em&gt;ignore&lt;/em&gt; any change in signal to their attachment block that is exactly 1 game tick or shorter (50ms or shorter), and only change state when the change in signal is longer than 1 tick. That way, a pulse that is 1.5 ticks or 2 ticks will affect a the torch, but a pulse that is exactly 1 tick or shorter won&apos;t, which is how redstone torches in the PC edition work.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Edit:&lt;/b&gt; updated info, since redstone torches in the PC edition ignore any pulse that is 1 game tick or shorter and respond to any pulse longer than 1 tick, not just 1.5 ticks.&lt;/p&gt;</description>
            <key id="128295">MCPE-11953</key>
            <summary>Redstone torch timings are off by half a tick</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="6">Works As Intended</resolution>
                                            <reporter username="jocopa3">Matt S</reporter>
                        <labels>
                    </labels>
                <created>Fri, 4 Dec 2015 01:13:29 +0100</created>
                <updated>Thu, 28 Apr 2016 19:33:25 +0200</updated>
                            <resolved>Wed, 9 Mar 2016 09:47:21 +0100</resolved>
                                    <version>0.13.0</version>
                                                                        <votes>2</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="294208" author="depressed-pho" created="Fri, 11 Mar 2016 04:38:26 +0100"  >&lt;p&gt;Well... okay then.  Thanks for your information.&lt;/p&gt;</comment>
                            <comment id="293638" author="missmarzenia" created="Wed, 9 Mar 2016 09:47:21 +0100"  >&lt;p&gt;This issue was marked by developers as &quot;As designed&quot; &lt;br/&gt;
Both teams (Stockholm and Redmond) are talking about this issue, so they are aware of the problem and they will try to fix it without breaking anything else. For now it is working as intended so it does not break other Redstone functions. &lt;/p&gt;</comment>
                            <comment id="280258" author="illidicia" created="Wed, 27 Jan 2016 02:44:43 +0100"  >&lt;p&gt;Reopened.&lt;/p&gt;</comment>
                            <comment id="280242" author="depressed-pho" created="Wed, 27 Jan 2016 01:01:08 +0100"  >&lt;p&gt;Attached an image &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/109178/109178_pulser-and-latch.jpg&quot; title=&quot;pulser-and-latch.jpg attached to MCPE-11953&quot;&gt;pulser-and-latch.jpg&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; showing a circuit to reproduce the issue without being affected by graphic update lag. The bottom half of it is an RS-NOR latch whose state can be toggled by button &quot;R&quot; and &quot;S&quot;. The upper half is a 1-tick pulse generator with button &quot;P&quot;.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Steps to reproduce:&lt;/b&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Press the button &quot;R&quot;.&lt;/li&gt;
	&lt;li&gt;Then press the button &quot;P&quot;.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;b&gt;What I expected:&lt;/b&gt;&lt;br/&gt;
The state of RS-NOR latch does not change after pressing the button &quot;P&quot;.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What actually happened:&lt;/b&gt;&lt;br/&gt;
The RS-NOR latch turned into a 1-tick clock, eternally changing its state.&lt;/p&gt;</comment>
                            <comment id="280176" author="jocopa3" created="Tue, 26 Jan 2016 23:16:11 +0100"  >&lt;p&gt;This bug still exists in 0.14.0, and it still does not work as intended.&lt;/p&gt;</comment>
                            <comment id="277666" author="jocopa3" created="Wed, 13 Jan 2016 18:53:39 +0100"  >&lt;p&gt;I agree with PHO. I clearly demonstrated in the YouTube video that there is a difference in how redstone torches work in PC and Pocket Edition, yet this issue is marked as &quot;Works As Intended.&quot; If the intention is to get redstone working the same in PE as it does in PC, then this is certainly not working as intended, and is still a bug.&lt;/p&gt;</comment>
                            <comment id="276525" author="depressed-pho" created="Wed, 6 Jan 2016 15:57:51 +0100"  >&lt;p&gt;Someone please reopen the issue, or tell us why it&apos;s an intended difference. I just can&apos;t stand getting it simply ignored and then permanently forgotten. &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-11279&quot; title=&quot;Activator Rail makes wool/cake sound when placing/breaking it&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-11279&quot;&gt;&lt;del&gt;MCPE-11279&lt;/del&gt;&lt;/a&gt; is another example which has been dismissed by &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=Janosik&quot; class=&quot;user-hover&quot; rel=&quot;Janosik&quot;&gt;Janosik&lt;/a&gt; for no apparent reason. There would be no point reporting bugs then.&lt;/p&gt;</comment>
                            <comment id="276501" author="depressed-pho" created="Wed, 6 Jan 2016 13:43:58 +0100"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=Janosik&quot; class=&quot;user-hover&quot; rel=&quot;Janosik&quot;&gt;Janosik&lt;/a&gt; closed this issue as &quot;Works As Intended&quot; with no explanation why it&apos;s intended. I strongly disagree with that because it&apos;s certainly behaving differently from the PC version, and since redstone mechanics is a really complicated system, having two different mechanics would not make things better.&lt;/p&gt;</comment>
                            <comment id="270212" author="jocopa3" created="Fri, 4 Dec 2015 05:46:05 +0100"  >&lt;p&gt;This is exactly what&apos;s going on. Those really compact and impossible clocks where two torches are on the same block only work because the 1-tick pulse created by one torch is short enough to change the state of the other torch.&lt;/p&gt;</comment>
                            <comment id="270210" author="depressed-pho" created="Fri, 4 Dec 2015 05:34:58 +0100"  >&lt;p&gt;Great. This may explain issues about weird behavior of torches, e.g. &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>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="139124">MCPE-14079</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="109178" name="pulser-and-latch.jpg" size="935136" author="depressed-pho" created="Wed, 27 Jan 2016 01:01: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</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|i0jun3:</customfieldvalue>

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