<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:27:41 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-11449] Repeaters update very differently</title>
                <link>https://bugs.mojang.com/browse/MC-11449</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;There is a problem when a timer is run and repeaters are placed in different directions and chunks, but to the same wire.&lt;/p&gt;

&lt;p&gt;Video: &lt;a href=&quot;http://www.youtube.com/watch?v=Xyo76ty0Fpk&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.youtube.com/watch?v=Xyo76ty0Fpk&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="25589">MC-11449</key>
            <summary>Repeaters update very differently</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>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="vilsol">Viljams Volosovskis</reporter>
                        <labels>
                            <label>redstone</label>
                            <label>repeaters</label>
                            <label>updates</label>
                    </labels>
                <created>Sat, 9 Mar 2013 23:10:23 +0100</created>
                <updated>Sun, 4 Feb 2018 17:20:49 +0100</updated>
                            <resolved>Sat, 29 Oct 2016 19:24:30 +0200</resolved>
                                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w05b</version>
                    <version>Minecraft 1.8</version>
                    <version>Minecraft 1.8.1-pre3</version>
                    <version>Minecraft 1.8.3</version>
                    <version>Minecraft 1.8.8</version>
                    <version>Minecraft 15w49b</version>
                                    <fixVersion>Minecraft 16w43a</fixVersion>
                                                        <votes>7</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="432877" author="nik115" created="Sun, 4 Feb 2018 17:20:49 +0100"  >&lt;p&gt;Apologies, I can&apos;t keep up the good work of bug reports, I forgot my Jira&lt;br/&gt;
account and want to unsubscribe from updates. Thanks.&lt;/p&gt;

&lt;p&gt;On Sun, Dec 6, 2015 at 12:01 PM, &lt;span class=&quot;error&quot;&gt;&amp;#91;Mod&amp;#93;&lt;/span&gt; Kumasasa (JIRA) &amp;lt;bugs@mojang.com&amp;gt;&lt;br/&gt;
wrote:&lt;/p&gt;

&lt;p&gt;&amp;gt; &lt;span class=&quot;error&quot;&gt;&amp;#91;Mod&amp;#93;&lt;/span&gt; Kumasasa&lt;br/&gt;
&amp;gt; &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa&lt;/a&gt;&amp;gt; &lt;b&gt;resolved&lt;/b&gt;&lt;br/&gt;
&amp;gt; an issue as &lt;b&gt;Awaiting Response&lt;/b&gt;&lt;br/&gt;
&amp;gt;&lt;br/&gt;
&amp;gt; Is this still an issue in the current Minecraft Snapshot &lt;b&gt;15w49b&lt;/b&gt; or&lt;br/&gt;
&amp;gt; later? If so, please update the affected versions in order to best aid&lt;br/&gt;
&amp;gt; Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;br/&gt;
&amp;gt; Minecraft &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC&lt;/a&gt;&amp;gt; / &lt;span class=&quot;error&quot;&gt;&amp;#91;image: Bug&amp;#93;&lt;/span&gt;&lt;br/&gt;
&amp;gt; &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-11449&lt;/a&gt;&amp;gt; &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449&quot; title=&quot;Repeaters update very differently&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11449&quot;&gt;&lt;del&gt;MC-11449&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
&amp;gt; &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-11449&lt;/a&gt;&amp;gt; Repeaters update very&lt;br/&gt;
&amp;gt; differently &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-11449&lt;/a&gt;&amp;gt; Change By: &lt;span class=&quot;error&quot;&gt;&amp;#91;Mod&amp;#93;&lt;/span&gt;&lt;br/&gt;
&amp;gt; Kumasasa &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa&lt;/a&gt;&amp;gt; Resolution:&lt;br/&gt;
&amp;gt; Awaiting Response Status: Reopened Resolved &lt;span class=&quot;error&quot;&gt;&amp;#91;image: Add Comment&amp;#93;&lt;/span&gt;&lt;br/&gt;
&amp;gt; &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449#add-comment&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-11449#add-comment&lt;/a&gt;&amp;gt; Add Comment&lt;br/&gt;
&amp;gt; &amp;lt;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-11449#add-comment&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-11449#add-comment&lt;/a&gt;&amp;gt;   This message was&lt;br/&gt;
&amp;gt; sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) &lt;span class=&quot;error&quot;&gt;&amp;#91;image: Atlassian logo&amp;#93;&lt;/span&gt;&lt;br/&gt;
&amp;gt;&lt;/p&gt;</comment>
                            <comment id="338994" author="the.modificator" created="Sat, 29 Oct 2016 18:41:09 +0200"  >&lt;p&gt;No. Tested the build of the YouTube video linked in the description with 16w43a.&lt;/p&gt;

&lt;p&gt;When loading a save file, an already running clock still had that problem.&lt;br/&gt;
When resetting the clock however, I was not able to reproduce the problem anymore.&lt;/p&gt;</comment>
                            <comment id="336357" author="miwob" created="Fri, 21 Oct 2016 20:35:10 +0200"  >&lt;p&gt;Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?&lt;/p&gt;</comment>
                            <comment id="270994" author="kuubaku" created="Mon, 7 Dec 2015 20:33:54 +0100"  >&lt;p&gt;Reporter&apos;s device (see vid in description) easily reproduced on latest snapshot (15w49b). &lt;/p&gt;</comment>
                            <comment id="270793" author="kumasasa" created="Sun, 6 Dec 2015 20:01:22 +0100"  >&lt;p&gt;Is this still an issue in the current Minecraft Snapshot &lt;b&gt;15w49b&lt;/b&gt; or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="223033" author="_death_star_" created="Thu, 26 Mar 2015 14:37:49 +0100"  >&lt;p&gt;Still present in 1.8.3&lt;/p&gt;</comment>
                            <comment id="205363" author="galaxy_2alex" created="Sat, 25 Oct 2014 15:32:30 +0200"  >&lt;p&gt;Reopened, thanks&lt;/p&gt;</comment>
                            <comment id="205357" author="the.modificator" created="Sat, 25 Oct 2014 15:25:54 +0200"  >&lt;p&gt;Yep, it is. Also, it might be related to &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11193&quot; title=&quot;The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11193&quot;&gt;MC-11193&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="168682" author="arokh" created="Fri, 27 Jun 2014 17:35:42 +0200"  >&lt;p&gt;On second thought, is this really a bug?&lt;/p&gt;

&lt;p&gt;Since the delays are not in alignment, it sounds more like an aliasing effect, which is also an issue in the real world.&lt;br/&gt;
I guess the repeaters which are supposedly &quot;out of sync&quot;, are just doing their sampling (checking their input) at different points of time, resulting in a different output sequence.&lt;br/&gt;
Changing that behavior to something else would probably lead to a lot of other issues and is probably hard to code in a satisfying way.&lt;/p&gt;</comment>
                            <comment id="138285" author="arokh" created="Thu, 6 Feb 2014 00:56:30 +0100"  >&lt;p&gt;It is still happening:&lt;br/&gt;
&lt;a href=&quot;http://youtu.be/jgwoGZUOEFY&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/jgwoGZUOEFY&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Issues start at around 1:40&lt;/p&gt;</comment>
                            <comment id="138258" author="kuubaku" created="Wed, 5 Feb 2014 22:02:43 +0100"  >&lt;p&gt;No progress made here since back then, I guess.&lt;/p&gt;</comment>
                            <comment id="64372" author="kuubaku" created="Tue, 30 Apr 2013 10:57:17 +0200"  >&lt;p&gt;@fibonatic&lt;br/&gt;
Glad you confirmed this. It also highly depends on how the signal is transported off the clock and - at higher delays - on how the payload (if any) is connected to a repeater.&lt;/p&gt;</comment>
                            <comment id="64355" author="fibonatic" created="Tue, 30 Apr 2013 03:53:42 +0200"  >&lt;p&gt;The first 3 repeaters in your video seem to follow the same cycle, however to moment of placing might have given the offset of the phase.&lt;br/&gt;
However I do have a &lt;a href=&quot;http://www.youtube.com/watch?v=PA1Is2Z6_UA&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;video&lt;/a&gt; in which the a similar phenomenon in demonstrated at the beginning: in certain positions 50% of the off-pulses get ignored.&lt;/p&gt;</comment>
                            <comment id="55734" author="nik115" created="Wed, 20 Mar 2013 05:06:31 +0100"  >&lt;p&gt;wowowowowowowowow awesome I love it&lt;/p&gt;</comment>
                            <comment id="55455" author="101m4n" created="Tue, 19 Mar 2013 15:42:13 +0100"  >&lt;p&gt;This seems to behave differently depending on position in world, perhaps related to the order of redstone updates in a wire? like &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11193&quot; title=&quot;The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11193&quot;&gt;MC-11193&lt;/a&gt;?&lt;br/&gt;
I really want both of these fixed &amp;gt;.&amp;lt;&lt;/p&gt;</comment>
                            <comment id="53327" author="kuubaku" created="Fri, 15 Mar 2013 00:40:42 +0100"  >&lt;p&gt;Came up with this clock oscilliscope setup while testing this report. Everything described below is valid as of 1.5.2pre. Fun facts:&lt;/p&gt;


&lt;p&gt;0) This seemingly orientation-independent device consists of a simple repeater clock and 8 oscilliscope lanes (3 test lanes and 1 for control purposes on each side).&lt;/p&gt;

&lt;p&gt;1) Each test lane in this device oscillates (almost) as expected when its respective controlling repeater (which are on gold blocks) has a delay that is lower than the clock has. &lt;/p&gt;

&lt;p&gt;2) When lane&apos;s controlling repeater has a delay greater than the clock has, it should oscillate only when one delay is divisible by another, otherwise the lane should become locked. However, this does not happen to 1st and 3rd test lanes (repeater-&amp;gt;block-&amp;gt;payload and repeater-&amp;gt;payload) when clock is set to 2 and repeaters are set to 3. Instead these lanes output a stable 3/5 signal. When toggled manually from 2 to 3, these repeaters are likely to lock their lanes. When toggled again to 4 in this locked state, they don&apos;t unlock the lane (like it happens on the reporter&apos;s video).&lt;/p&gt;

&lt;p&gt;3) When lane&apos;s controlling repeater is delayed as much as the clock is, 1st and/or 3rd test lanes may output a 3x/x pulse instead of expected x/x (for instance, 6/2 where 2/2 was expected). This depends largely on redstone wiring (e.g. which exact quartz block is used to support the wire which transports signal to the lanes). &lt;/p&gt;

&lt;p&gt;4) When all delays are set to 1, every lane (including control lane) outputs either 1/1 or 3/1 pulse. This also depends on wiring. Generally, if 2-clock pulse passing over some exact quartz block does generate 6/2 strobes on 1st and 3rd lanes, then 1-clock pulse passing over that block will give a 3/1 strobe on every lane. &lt;/p&gt;

&lt;p&gt;5) Set the clock delay to 1. If you swap your controlling repeaters for comparators, they will lock test lanes in low state. If instead you swap first receiving repeaters of each lane for comparators, you&apos;ll get to see that either all four lanes are down, or 1st and 3rd test lanes are locked up, or even all the test lanes are up. This, surprisingly, depends on timings: you have a chance to get each outcome out of these three after reconnecting the redstone through any quartz block you like in the exact wrong moment. &lt;/p&gt;

&lt;p&gt;6) I have built two similar devices: one 2 chunks east and one east-oriented a dozen chunks southeast. They had to be wired through some other quartz blocks to output the same doughnutlike patterns as this device does without comparators.&lt;/p&gt;</comment>
                            <comment id="51449" author="banana478" created="Sat, 9 Mar 2013 23:15:34 +0100"  >&lt;p&gt;Confirmed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="25303">MC-11193</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="23997">MC-10132</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="24897" name="2013-03-15_01.13.24.png" size="225276" author="kuubaku" created="Fri, 15 Mar 2013 00:40:42 +0100"/>
                            <attachment id="24898" name="2013-03-15_01.15.20.png" size="215415" author="kuubaku" created="Fri, 15 Mar 2013 00:40:42 +0100"/>
                            <attachment id="24899" name="2013-03-15_03.46.52.png" size="99297" author="kuubaku" created="Fri, 15 Mar 2013 00:47:52 +0100"/>
                            <attachment id="24971" name="2013-03-15_17.06.28.png" size="182787" author="kuubaku" created="Fri, 15 Mar 2013 14:44:26 +0100"/>
                            <attachment id="24972" name="2013-03-15_17.08.33.png" size="182429" author="kuubaku" created="Fri, 15 Mar 2013 14:44:26 +0100"/>
                            <attachment id="55637" name="2014-02-06_00.59.14.png" size="258599" author="kuubaku" created="Wed, 5 Feb 2014 22:02:43 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sun, 10 Mar 2013 01:31: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_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0dh1z:</customfieldvalue>

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