<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:14:34 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-17208] Repeaters set to 1-redstone-tick &amp; comparators have no delay compared to redstone dust</title>
                <link>https://bugs.mojang.com/browse/MCPE-17208</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay. This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://youtu.be/z5BXgd2fbP8&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://youtu.be/z5BXgd2fbP8&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Note that at the time of recording, I thought the bug was with pistons, and didn&apos;t realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters/comparators, by redstone dust, or by just incorrect redstone timings in general. I&apos;ve also noticed that repeaters, comparators, redstone torches, and redstone dust are powered with the correct timing delay when repeaters are powering them, either directly or with redstone dust in-between, but the affected components listed below will still be powered as though there were no dust between them and the repeater (meaning that you can power a line with dust -&amp;gt; repeater -&amp;gt; 2nd dust -&amp;gt; redstone lamp, and the redstone lamp will come on at the same time as the 1st dust and repeater, and actually 1 redstone tick before the 2nd dust that&apos;s supposed to be powering it! This bug almost certainly has something to do with the way that redstone components are powered in MCPE ignoring certain factors (this bug is another example: &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-11871&quot; title=&quot;Redstone not powering horizontally adjacent blocks&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-11871&quot;&gt;&lt;del&gt;MCPE-11871&lt;/del&gt;&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;List of blocks this bug affects:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;pistons&lt;/li&gt;
	&lt;li&gt;sticky pistons&lt;/li&gt;
	&lt;li&gt;dispensers&lt;/li&gt;
	&lt;li&gt;droppers&lt;/li&gt;
	&lt;li&gt;redstone lamps&lt;/li&gt;
	&lt;li&gt;observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)&lt;/li&gt;
	&lt;li&gt;note blocks&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;List of blocks this bug doesn&apos;t seem to affect:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;repeaters (the proper delay will be applied to repeaters being powered by other repeaters or redstone dust coming from other repeaters)&lt;/li&gt;
	&lt;li&gt;comparators (same as with repeaters)&lt;/li&gt;
	&lt;li&gt;redstone torches (by sending the dust/repeaters into blocks to invert the torches)&lt;/li&gt;
	&lt;li&gt;redstone dust (but components hooked up like repeater -&amp;gt; dust -&amp;gt; piston will actually be powered 1 redstone tick before the dust and in the same tick as the repeater is powered)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they&apos;re hooked up to. I&apos;m not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-16371&quot; title=&quot;Multiple mechanism components are ticked in a random order when they are to be ticked in exactly the same rs tick&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-16371&quot;&gt;&lt;del&gt;MCPE-16371&lt;/del&gt;&lt;/a&gt;, since there&apos;s no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.&lt;/p&gt;</description>
            <key id="149814">MCPE-17208</key>
            <summary>Repeaters set to 1-redstone-tick &amp; comparators have no delay compared to redstone dust</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="3">Duplicate</resolution>
                                            <reporter username="SuperGeniusZeb">Zeb</reporter>
                        <labels>
                            <label>delay</label>
                            <label>piston</label>
                            <label>redstone</label>
                            <label>redstone-comparator</label>
                            <label>redstone-dust</label>
                            <label>redstone-lamp</label>
                            <label>redstone-piston</label>
                            <label>redstone-repeater</label>
                            <label>redstone-tick</label>
                            <label>redstone-timing</label>
                            <label>redstone-update</label>
                    </labels>
                <created>Tue, 20 Sep 2016 17:30:41 +0200</created>
                <updated>Sun, 19 Mar 2017 06:02:56 +0100</updated>
                            <resolved>Wed, 18 Jan 2017 13:00:40 +0100</resolved>
                                    <version>0.15.8</version>
                    <version>0.15.90.7</version>
                    <version>0.15.9</version>
                    <version>0.15.10</version>
                    <version>0.15.90.8</version>
                    <version>0.16.0</version>
                    <version>0.16.1</version>
                    <version>0.17.0.1</version>
                    <version>0.16.2</version>
                    <version>1.0.0.0</version>
                    <version>1.0.0.1</version>
                    <version>1.0.0.2</version>
                    <version>1.0.0.7</version>
                    <version>1.0.0</version>
                                                                        <votes>12</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="334822" author="nighter" created="Thu, 13 Oct 2016 12:05:48 +0200"  >&lt;p&gt;This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided). &lt;/p&gt;</comment>
                            <comment id="333095" author="zebulanstanphill@gmail.com" created="Mon, 3 Oct 2016 22:39:01 +0200"  >&lt;p&gt;Updated the title and description to reflect recent testing that shows that this bug also affects redstone lamps and other redstone components as well.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="144472">MCPE-15793</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="124515" name="Minecraft_ Windows 10 Edition Beta 9_20_2016 9_56_07 &#169;.png" size="407717" author="SuperGeniusZeb" created="Tue, 20 Sep 2016 17:30:41 +0200"/>
                            <attachment id="124516" name="Minecraft_ Windows 10 Edition Beta 9_20_2016 9_56_42 &#169;.png" size="402278" author="SuperGeniusZeb" created="Tue, 20 Sep 2016 17:30:41 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>36225</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 19 Dec 2016 17:43: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_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Windows 10 Version 1607</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|i00szr:</customfieldvalue>

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