<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:14:49 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-17274] Repeaters add random delay to pistons (but not to other components)</title>
                <link>https://bugs.mojang.com/browse/MCPE-17274</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;The double piston extenders below will work occasionally, even though there is not enough delay.&lt;br/&gt;
This seems entirely random.&lt;/p&gt;</description>
            <key id="150107">MCPE-17274</key>
            <summary>Repeaters add random delay to pistons (but not to other components)</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="ProNoob135">Tavish McEwen</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Sep 2016 16:30:48 +0200</created>
                <updated>Mon, 27 Mar 2017 21:35:35 +0200</updated>
                            <resolved>Mon, 23 Jan 2017 22:35:14 +0100</resolved>
                                    <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</version>
                    <version>1.0.2</version>
                                                                        <votes>4</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="355581" author="zebulanstanphill@gmail.com" created="Mon, 23 Jan 2017 22:35:14 +0100"  >&lt;p&gt;Resolving as duplicate of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15793&quot; title=&quot;Redstone components don&amp;#39;t apply the correct amount of delay when activated by world changes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15793&quot;&gt;MCPE-15793&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="335483" author="talaeus" created="Mon, 17 Oct 2016 08:37:34 +0200"  >&lt;p&gt;To explain what&apos;s going on:&lt;/p&gt;

&lt;p&gt;If you activate a repeater with an in-world change (pulling a lever, pushing a button, placing a redstone block, a piston pushed/pulls something which causes the redstone system to change) then the repeater will activate with 1 tick less delay than it should. A 1 tick delay repeater would activate immediately just as if it was redstone dust.&lt;/p&gt;</comment>
                            <comment id="335469" author="shukafu" created="Mon, 17 Oct 2016 01:01:43 +0200"  >&lt;p&gt;redstone dust has 1 tick delay. tested this side by side with a repeater and a comparator and they activate piston at the same time. tested it on 0.15.10&lt;/p&gt;</comment>
                            <comment id="333592" author="zebulanstanphill@gmail.com" created="Thu, 6 Oct 2016 17:50:15 +0200"  >&lt;p&gt;I think this may be related to, or even the same bug as, &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-17208&quot; title=&quot;Repeaters set to 1-redstone-tick &amp;amp; comparators have no delay compared to redstone dust&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-17208&quot;&gt;&lt;del&gt;MCPE-17208&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="332030" author="pronoob135" created="Thu, 29 Sep 2016 15:31:27 +0200"  >&lt;p&gt;May be the fact that pistons unpowering other pistons is not instant in PE, maybe this was improved/worsened in 0.15.9&lt;/p&gt;</comment>
                            <comment id="331922" author="depressed-pho" created="Thu, 29 Sep 2016 06:27:58 +0200"  >&lt;p&gt;The screenshot shown below is a circuit to move an extended piston back and forth. It was perfectly working until I updated the game to 0.15.9. Its expected behavior when you turn the lever off is as follows:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;At t=0, you turn the lever off. Ideally the piston A should start retracting but in reality nothing happens due to &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15607&quot; title=&quot;Pistons take 3 redstone ticks to extend and 1 tick to retract, which should both take only 1 rs tick&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15607&quot;&gt;&lt;del&gt;MCPE-15607&lt;/del&gt;&lt;/a&gt;.&lt;/li&gt;
	&lt;li&gt;At t=1, piston A starts retracting.&lt;/li&gt;
	&lt;li&gt;At t=2, piston A finishes retracting. At the same time piston B starts retracting because the redstone block is no longer adjacent to it.&lt;/li&gt;
	&lt;li&gt;At t=3, piston B finishes retracting.&lt;/li&gt;
	&lt;li&gt;At t=4, the repeater deactivates. Ideally the piston C should start retracting but it doesn&apos;t for the same reason as t=0.&lt;/li&gt;
	&lt;li&gt;At t=5, piston C starts retracting with pulling piston B because B has already been retracted at t=3.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;125212_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/125212/125212_repeater-piston-randomness.png&quot; title=&quot;repeater-piston-randomness.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;125212&quot; file-preview-title=&quot;repeater-piston-randomness.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/125212/_thumb_125212.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;However in 0.15.9, there is a small chance that the piston C leaves B behind, which is completely unexplainable. It is as if the repeater were only making 3 ticks delay even though it is set to 4 ticks. Adding one more repeater to piston C works around the problem but it shouldn&apos;t be needed at all.&lt;/p&gt;</comment>
                            <comment id="331867" author="pronoob135" created="Thu, 29 Sep 2016 02:23:26 +0200"  >&lt;p&gt;I meant that this dpe should never work&lt;/p&gt;</comment>
                            <comment id="331859" author="depressed-pho" created="Thu, 29 Sep 2016 02:02:33 +0200"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=ProNoob135&quot; class=&quot;user-hover&quot; rel=&quot;ProNoob135&quot;&gt;ProNoob135&lt;/a&gt;: Are you saying that DPE should work as long as there are 2 ticks and 0 ticks delays respectively but currently doesn&apos;t? If so that&apos;s &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15607&quot; title=&quot;Pistons take 3 redstone ticks to extend and 1 tick to retract, which should both take only 1 rs tick&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15607&quot;&gt;&lt;del&gt;MCPE-15607&lt;/del&gt;&lt;/a&gt;, not this one.&lt;br/&gt;
This very bug has been introduced very recently to 0.15.9 and 0.15.90.7. Contraptions that were working flawlessly in 0.15.8 now occasionally malfunction.&lt;/p&gt;</comment>
                            <comment id="331854" author="depressed-pho" created="Thu, 29 Sep 2016 01:57:00 +0200"  >&lt;p&gt;@tomas: Yeah I knew that ticking order was intentionally randomized. What I found was, however, inserting repeaters to create a delay &lt;b&gt;sometimes&lt;/b&gt; didn&apos;t do the trick. Even a repeater set to 4 ticks had a random chance to add no delay to pistons as you said. Repeaters behave completely normally to any other mechanical components.&lt;/p&gt;

&lt;p&gt;And in some cases repeaters can add too long delay to pistons, e.g. a repeater set to 2 ticks &lt;b&gt;sometimes&lt;/b&gt; add 3 or 4 ticks to pistons.&lt;/p&gt;</comment>
                            <comment id="331831" author="pronoob135" created="Thu, 29 Sep 2016 00:55:56 +0200"  >&lt;p&gt;This bug has been in the game since pistons were added, probably sooner. Yes the randomness is not a bug, but the fact that the dpe in images 3-4 work at all is. &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="331449" author="talaeus" created="Wed, 28 Sep 2016 16:50:02 +0200"  >&lt;p&gt;The randomness isn&apos;t a bug in itself. If two pistons are activated during the same tick, then it is completely random which one will actually be activated first. You need to make sure one of them are activated a whole tick before the others for it to be non-random.&lt;/p&gt;

&lt;p&gt;On the other hand, the repeaters seem to be buggy.&lt;/p&gt;</comment>
                            <comment id="331379" author="depressed-pho" created="Wed, 28 Sep 2016 11:27:32 +0200"  >&lt;p&gt;I&apos;ve seen similar issues in 0.15.9. Pistons and repeaters now interact very weirdly with regard to the ticking order, I mean, pistons that are supposed to be ticked have a chance of being skipped &lt;b&gt;or&lt;/b&gt; prematurely extended/retracted when they are powered by a repeater. I guess they changed the ticking system to fix &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15607&quot; title=&quot;Pistons take 3 redstone ticks to extend and 1 tick to retract, which should both take only 1 rs tick&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15607&quot;&gt;&lt;del&gt;MCPE-15607&lt;/del&gt;&lt;/a&gt; but the result is unfortunately even more buggy than before... ;(&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="124764" name="Screenshot_2016-09-26-07-23-15.png" size="936169" author="ProNoob135" created="Mon, 26 Sep 2016 16:30:48 +0200"/>
                            <attachment id="124763" name="Screenshot_2016-09-26-07-23-32.png" size="935874" author="ProNoob135" created="Mon, 26 Sep 2016 16:30:48 +0200"/>
                            <attachment id="124762" name="Screenshot_2016-09-26-07-24-00.png" size="863559" author="ProNoob135" created="Mon, 26 Sep 2016 16:30:48 +0200"/>
                            <attachment id="124761" name="Screenshot_2016-09-26-07-24-10.png" size="876822" author="ProNoob135" created="Mon, 26 Sep 2016 16:30:48 +0200"/>
                            <attachment id="125212" name="repeater-piston-randomness.png" size="933133" author="depressed-pho" created="Thu, 29 Sep 2016 06:27:58 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>32788</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 21 Jan 2017 02:03: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>Android 5.1</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10718"><![CDATA[Phone - Android - LG Other (Specify in description)]]></customfieldvalue>

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

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