<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:58:09 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>[MC-2523] Redstone loops get broken timings.</title>
                <link>https://bugs.mojang.com/browse/MC-2523</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=PmXkJIC0Agc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.youtube.com/watch?v=PmXkJIC0Agc&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A redstone loop, consisting of 3 repeaters and two torches, acting as a timing loop, will get locked into a stable state, or get an altered timing.&lt;/p&gt;

&lt;p&gt;First seen in 125 multiplayer (very common); never happened in 125 single player.&lt;/p&gt;

&lt;p&gt;Still happens &amp;#8211; much less frequently &amp;#8211; in 142.&lt;/p&gt;</description>
                <environment>Mac os 10.6 and 10.7. Java 6.</environment>
        <key id="14206">MC-2523</key>
            <summary>Redstone loops get broken timings.</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="4">Incomplete</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="keybounce">Keybounce</reporter>
                        <labels>
                    </labels>
                <created>Thu, 8 Nov 2012 18:08:18 +0100</created>
                <updated>Thu, 17 Mar 2016 16:17:56 +0100</updated>
                            <resolved>Thu, 17 Mar 2016 16:17:56 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                    <version>Snapshot 13w05b</version>
                    <version>Snapshot 13w10b</version>
                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Minecraft 1.6.4</version>
                    <version>Minecraft 1.7.9</version>
                                                                        <votes>6</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="295154" author="JIRAUSER71590" created="Thu, 17 Mar 2016 16:17:56 +0100"  >&lt;p&gt;No response for over a year.&lt;/p&gt;</comment>
                            <comment id="206562" author="galaxy_2alex" created="Thu, 30 Oct 2014 17:27:33 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt;? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; 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.&lt;/p&gt;

&lt;p&gt;Keep in mind that the &quot;Resolved&quot;-Status on this ticket just means &quot;Answered&quot;, 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 deliviered.&lt;/p&gt;</comment>
                            <comment id="184053" author="keybounce" created="Sun, 3 Aug 2014 02:04:20 +0200"  >&lt;p&gt;AAarrrggh.&lt;/p&gt;

&lt;p&gt;I cannot find that test world! I have checked every save I can find.&lt;/p&gt;</comment>
                            <comment id="168217" author="keybounce" created="Thu, 26 Jun 2014 16:20:53 +0200"  >&lt;p&gt;My computer is in the shop right now so I can&apos;t test. Should be back by monday.&lt;/p&gt;

&lt;p&gt;(Motherboard failure under warranty)&lt;/p&gt;</comment>
                            <comment id="168205" author="themoogle" created="Thu, 26 Jun 2014 15:22:43 +0200"  >&lt;p&gt;Is this still an issue in 14w26b? I&apos;ve recently committed a fix that removes random updates from redstone devices.&lt;/p&gt;</comment>
                            <comment id="162976" author="keybounce" created="Thu, 12 Jun 2014 19:47:54 +0200"  >&lt;p&gt;Actually, there is something else.&lt;/p&gt;

&lt;p&gt;If the issue was that a torch getting a random update would turn on and stay on, then I would probably be seeing a different failure pattern.&lt;/p&gt;

&lt;p&gt;The &quot;fail&quot; state is always the impossible state. The circuit should exist in either the &quot;off&quot; state, or the &quot;loop&quot; state &amp;#8211; the &quot;on, stable&quot; state should never happen.&lt;/p&gt;

&lt;p&gt;The &quot;fail&quot; state is always the &quot;on, stable&quot; state &amp;#8211; it never fails into the off state. If I&apos;m understanding what you said about the torches getting random updates and going bad, them 1 out of three failures should be into the off state.&lt;/p&gt;</comment>
                            <comment id="162972" author="keybounce" created="Thu, 12 Jun 2014 19:44:42 +0200"  >&lt;p&gt;Oh. My video in the original post showed my original circuit &amp;#8211; a little more complicated. Basically, an R/S Nor latch, with 3 repeaters at length 4 &amp;#8211; two on one side of the circuit, and one on the other side. A &quot;doorbell&quot; button that fed into the circuit, and noteblocks (plus a redstone torch) as outputs.&lt;/p&gt;

&lt;p&gt;Gave a nice, &quot;stable&quot; doorbell while playing single player. It actually worked properly in 125 single player. That was the last time that complicated redstone circuits worked without timing issues &amp;#8211; heck, instant wire worked across unloaded chunks.&lt;/p&gt;

&lt;p&gt;That it worked in 125 single player, and broke in 125 multiplayer, is why I suspect that random block updates is not the only issue, even if it fixed other issues. 125 single player would still have had random updates and scheduled updates.&lt;/p&gt;</comment>
                            <comment id="162878" author="antofthy" created="Thu, 12 Jun 2014 05:45:27 +0200"  >&lt;p&gt;The problem effects torches which are part of the loop!&lt;br/&gt;
Also the image is of loops only consisting of torches.&lt;/p&gt;

&lt;p&gt;Random update is for dealing with burned out torches, but the timing fault may result in torches remaining permanently on, which never gets fixed.&lt;/p&gt;</comment>
                            <comment id="162655" author="keybounce" created="Wed, 11 Jun 2014 07:10:25 +0200"  >&lt;p&gt;Ok, tested in 1.7.9.&lt;/p&gt;

&lt;p&gt;Actually rebuilt both circuits in a new world.&lt;/p&gt;

&lt;p&gt;The pure torch loop fails fairly quickly. The torch and repeater loop takes longer to fail, but still fails.&lt;/p&gt;</comment>
                            <comment id="162638" author="keybounce" created="Wed, 11 Jun 2014 02:08:18 +0200"  >&lt;p&gt;Hmm, need to retest in 1.7.10 ...&lt;/p&gt;</comment>
                            <comment id="162637" author="keybounce" created="Wed, 11 Jun 2014 02:07:35 +0200"  >&lt;p&gt;Unlikely to be the same, but might point to something similar.&lt;/p&gt;

&lt;p&gt;I looked, and their list of classes does not include the repeater. Maybe what is being seen has the same issue as that.&lt;/p&gt;

&lt;p&gt;To clarify: There is an attachment that shows a loop of just redstone torches; that is easy to show the timing error, and is almost certainly the issue that they found (that random block updates interfere with time sensitive scheduled updates &amp;#8211; I agree that the call for a scheduled update should not be the same as the call for a random update). But what I originally found this in, and showed in the video I linked, had repeaters and was not just going into timing error, but steady state &amp;#8211; including an &quot;impossible&quot; to get to but stable once obtained state.&lt;/p&gt;</comment>
                            <comment id="162632" author="antofthy" created="Wed, 11 Jun 2014 01:56:08 +0200"  >&lt;p&gt;It is probably the same as &lt;a href=&quot;https://bugs.mojang.com/browse/MC-56541&quot; title=&quot;Redstone torches (and other redstone components) have inconsistent timings&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-56541&quot;&gt;&lt;del&gt;MC-56541&lt;/del&gt;&lt;/a&gt; which ZipKrowd members Kabo and Panda have provided a fix for,&lt;/p&gt;</comment>
                            <comment id="133336" author="galaxy_2alex" created="Tue, 21 Jan 2014 22:05:20 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.7.4&lt;/b&gt; / Launcher version &lt;b&gt;1.3.8&lt;/b&gt; or later? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="126410" author="keybounce" created="Sun, 22 Dec 2013 21:00:22 +0100"  >&lt;p&gt;Whoops, yes. Still present in 164.&lt;br/&gt;
Will retest in 174 &quot;real soon now&quot; &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="106412" author="cubethethird" created="Thu, 26 Sep 2013 04:57:44 +0200"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.6.4&lt;/b&gt; / Launcher version &lt;b&gt;1.2.5&lt;/b&gt; ? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="90080" author="keybounce" created="Sat, 13 Jul 2013 00:48:05 +0200"  >&lt;p&gt;Still in 152.&lt;br/&gt;
I have not yet tested in 16x.&lt;/p&gt;</comment>
                            <comment id="50930" author="keybounce" created="Fri, 8 Mar 2013 04:16:30 +0100"  >&lt;p&gt;Still present in 1.5 pre-release.&lt;br/&gt;
&lt;a href=&quot;http://youtu.be/aR2Kz2N05SM&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/aR2Kz2N05SM&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="50593" author="keybounce" created="Thu, 7 Mar 2013 01:31:01 +0100"  >&lt;p&gt;Still present in 13w10b.&lt;/p&gt;</comment>
                            <comment id="49111" author="keybounce" created="Sat, 2 Mar 2013 17:49:47 +0100"  >&lt;p&gt;I haven&apos;t seen any mention of this in the release notes for the snapshots, and I do not have an easy way to test this right now. (BTW: I love that 5 torch dual-loop!). Is this still active, or has it been fixed yet?&lt;/p&gt;</comment>
                            <comment id="43674" author="keybounce" created="Tue, 5 Feb 2013 05:23:50 +0100"  >&lt;p&gt;Ahh &amp;#8211; someone else has tested this for me &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="43673" author="keybounce" created="Tue, 5 Feb 2013 05:09:28 +0100"  >&lt;p&gt;Sorry. Was in 145; will recheck 147, but not expecting any difference.&lt;/p&gt;</comment>
                            <comment id="43645" author="bljat" created="Tue, 5 Feb 2013 03:17:31 +0100"  >&lt;p&gt;Confirmed.&lt;/p&gt;</comment>
                            <comment id="43433" author="kimitsu" created="Mon, 4 Feb 2013 12:56:04 +0100"  >&lt;p&gt;Bug is still present in 13w05b&lt;br/&gt;
Looks like redstone torches still receive random block updates.&lt;br/&gt;
In multiplayer, though, the issue probably lies in block update limit which can get part of your redstone updates postponed to the nex tick.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="21013" name="2013-02-04_14.35.02.png" size="127496" author="kimitsu" created="Mon, 4 Feb 2013 12:59:11 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 5 Feb 2013 03:17:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></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_10501" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Game Mode</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10304"><![CDATA[Survival]]></customfieldvalue>

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

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