<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:09:03 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-15793] Redstone components don&apos;t apply the correct amount of delay when activated by world changes</title>
                <link>https://bugs.mojang.com/browse/MCPE-15793</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;h3&gt;&lt;a name=&quot;WhatIexpectedtohappenwas...&quot;&gt;&lt;/a&gt;What I expected to happen was...&lt;/h3&gt;

&lt;p&gt;On flicking the power switch in each example, the blue example shown would fire like the red example shown (end repeater lights up).&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Whatactuallyhappenedwas...&quot;&gt;&lt;/a&gt;What actually happened was...&lt;/h3&gt;

&lt;p&gt;In the blue example, the output repeater doesn&apos;t fire. If you rapidly flick the switch back and forth, the blue repeater fires intermittently.&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Stepstoreproduce%3A&quot;&gt;&lt;/a&gt;Steps to reproduce:&lt;/h3&gt;

&lt;ol&gt;
	&lt;li&gt;Drive redstone current into a block on top of a piston to generate a 1-tick pulse (red example). Position a repeater to pick up the current from the piston block, but the redstone should flow directly from power source to the block.&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;Turn on the power source; the piston will fire and the output repeater will light up for its pulse duration.&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;Insert a repeater anywhere along the input line and toggle the power source. the output repeater will not fire.&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;Rapidly toggle the power source (switch works best). The repeater will occasionally fire.&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;replacing the relay with redstone torch inverters shows the same issue (the mechanism will fire when the torch is placed, but not when the mechanism is toggled).&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;Using an observer block as the power source showed the same issue.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Minecraft pocket edition 0.15.0 (iOS - replicated on iPhone 6 and iPad air 2)&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update by &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=nighter&quot; class=&quot;user-hover&quot; rel=&quot;nighter&quot;&gt;nighter&lt;/a&gt;&lt;/b&gt;&lt;br/&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;br/&gt;
Please avoid duplicate comments. Post only NEW information regarding this bug.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update by &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=talaeus&quot; class=&quot;user-hover&quot; rel=&quot;talaeus&quot;&gt;talaeus&lt;/a&gt;, explaining the cause of the bug&lt;/b&gt;&lt;br/&gt;
Repeaters don&apos;t apply the delay properly in all cases. If the repeater was activated by another pure redstone component being &lt;em&gt;ticked&lt;/em&gt;, then the delay will be correct. However, if it was activated by a world change (lever, piston modifying a circuit, pressure plates, buttons, etc) then the repeater will output a signal 1 tick too fast. A 1-delay repeater will act as a 0-delay repeater (that is, completely ignored). A 3-delay repeater will act as a 2-delay repeater.&lt;/p&gt;</description>
            <key id="144472">MCPE-15793</key>
            <summary>Redstone components don&apos;t apply the correct amount of delay when activated by world changes</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="4" iconUrl="https://bugs.mojang.com/images/icons/statuses/reopened.png" description="This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.">Reopened</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                            <reporter username="Siphio">Siphio</reporter>
                        <labels>
                            <label>piston</label>
                            <label>redstone</label>
                            <label>redstone-pulse</label>
                            <label>redstone_comparator</label>
                            <label>redstone_repeater</label>
                            <label>redstone_torch</label>
                    </labels>
                <created>Tue, 21 Jun 2016 22:13:23 +0200</created>
                <updated>Fri, 26 Jul 2024 21:38:28 +0200</updated>
                                            <version>1.20.20.23 Preview</version>
                    <version>1.20.20.22 Preview</version>
                    <version>1.17.10</version>
                    <version>1.16.200.57 Beta</version>
                    <version>1.16.100.58 Beta</version>
                    <version>1.16.100.56 Beta</version>
                    <version>1.16.100.55 Beta</version>
                    <version>1.15.0.8 RTX Beta</version>
                    <version>1.16.0.63 Beta</version>
                    <version>1.16.0.61 Beta</version>
                    <version>1.15.0.53 Beta</version>
                    <version>1.15.0.51 Beta</version>
                    <version>1.14.30.51 Beta</version>
                    <version>1.14.2.51 Beta</version>
                    <version>1.14.2.50 Beta</version>
                    <version>1.14.0.51 Beta</version>
                    <version>1.13.3</version>
                    <version>1.14.0.4 Beta</version>
                    <version>1.13.1</version>
                    <version>1.14.1 Hotfix</version>
                    <version>1.14.0.3 Beta</version>
                    <version>1.14.0.2 Beta</version>
                    <version>1.14.0.1 Beta</version>
                    <version>1.13.0.18 Beta</version>
                    <version>1.13.0.17 Beta</version>
                    <version>1.13.0.16 Beta</version>
                    <version>1.13.0.15 Beta</version>
                    <version>1.13.0.9 Beta</version>
                    <version>1.13.0.6 Beta</version>
                    <version>1.12.0.2 Beta</version>
                    <version>0.15.0</version>
                    <version>0.15.2</version>
                    <version>0.15.4</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.7</version>
                    <version>1.0.0</version>
                    <version>1.0.2</version>
                    <version>1.0.3</version>
                    <version>1.0.4.0</version>
                    <version>1.0.4.1</version>
                    <version>1.0.4.11</version>
                    <version>1.0.5.13</version>
                    <version>1.0.6.0</version>
                    <version>1.0.5.54</version>
                    <version>1.1.0.0</version>
                    <version>1.0.6.52</version>
                    <version>1.1.0.4</version>
                    <version>1.1.0.5</version>
                    <version>1.0.7.0</version>
                    <version>1.1.0.9</version>
                    <version>1.1.0.55</version>
                    <version>1.1.1.0</version>
                    <version>1.1.1.51</version>
                    <version>1.1.2.50</version>
                    <version>1.1.3.1</version>
                    <version>1.1.5.0</version>
                    <version>1.2.0.25</version>
                    <version>1.2.0.31</version>
                    <version>1.2.3.6</version>
                    <version>1.2.5.12</version>
                    <version>1.2.6.2</version>
                    <version>1.2.5.52</version>
                    <version>1.2.6.60</version>
                    <version>1.2.9.1</version>
                    <version>1.2.10.1</version>
                    <version>1.2.10.2</version>
                    <version>1.2.15.01</version>
                    <version>1.2.16.3</version>
                    <version>1.5.0.0</version>
                    <version>1.4.0.5</version>
                    <version>1.5.0.7</version>
                    <version>1.4.2.0</version>
                    <version>1.5.0.14</version>
                    <version>1.6.0.6</version>
                    <version>1.7.0.9 Beta</version>
                    <version>1.9.0</version>
                    <version>1.10.0.4 Beta</version>
                    <version>1.11.0.1 Beta</version>
                    <version>1.11.0.3 Beta</version>
                    <version>1.11.4</version>
                    <version>1.12.1</version>
                    <version>1.12.0</version>
                    <version>1.13.0</version>
                    <version>1.14.1.2 Beta</version>
                    <version>1.14.0</version>
                    <version>1.14.30 Hotfix</version>
                    <version>1.14.60 Hotfix</version>
                    <version>1.16.0</version>
                    <version>1.16.20</version>
                    <version>1.16.50 Hotfix (iOS)</version>
                    <version>1.16.40 Hotfix</version>
                    <version>1.16.100</version>
                    <version>1.16.210</version>
                    <version>1.16.221 Hotfix</version>
                    <version>1.18.2 Hotfix</version>
                    <version>1.19.2 Hotfix</version>
                    <version>1.19.20</version>
                    <version>1.19.21 Hotfix</version>
                    <version>1.19.62</version>
                    <version>1.20.12 Hotfix</version>
                    <version>1.20.81 Hotfix</version>
                                                                        <votes>203</votes>
                                    <watches>90</watches>
                                                                            <comments>
                            <comment id="1340576" author="yri066.ru" created="Mon, 22 Jul 2024 10:19:26 +0200"  >&lt;p&gt;This problem often affects mechanisms designed for tick, because of it I face the fact that the mechanisms do not work correctly and constantly break, which makes their use in the game impossible&lt;/p&gt;

&lt;p&gt;In the video, the mechanism should go down 1 block, but because of the different delay of the signal given by the observer, it often works incorrectly or breaks &lt;a href=&quot;https://youtu.be/fOfB7Tgd_gA&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://youtu.be/fOfB7Tgd_gA &lt;/a&gt;Unlike Java, in Bedrock the mechanism works differently every time you run it and it&apos;s quite annoying&lt;/p&gt;</comment>
                            <comment id="1286219" author="chixvv" created="Fri, 20 Oct 2023 08:20:41 +0200"  >&lt;p&gt;&lt;a href=&quot;https://minecraft.wiki/w/User:Chixvv/About_redstone_timings_in_Bedrock_Edition&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;About redstone timings in Bedrock Edition&lt;/a&gt;&lt;br/&gt;
Here&apos;s an article about techically comprehensive explanation of redstone in Bedrock Edition, which may be helpful to understand why these issues happen.&lt;br/&gt;
In Bedrock Edition, redstone circuits rely on the circuit system to work, rather than block updates. The fundamental reason for these issues is that &lt;b&gt;there is something wrong with the original design of the circuit system&lt;/b&gt;. To fix the bug, many disruptive changes must be made, and perhaps even needs rewrite the whole circuit system. That&apos;s why this frustrating bug can&apos;t be fixed for a long time.&lt;/p&gt;</comment>
                            <comment id="1275645" author="brykkan" created="Sat, 19 Aug 2023 21:25:25 +0200"  >&lt;p&gt;Given that this is still an issue years later, I would really appreciate some official commentary/explanation of the underlying issue.&lt;/p&gt;

&lt;p&gt;On the surface, this seems incredibly straightforward to fix without major changes to tick processing order. That is, simply have components remember their previous power state, and always queue an update to invert them during the next tick if they received any update that &lt;b&gt;would have&lt;/b&gt; changed their state during the previous tick. I.e. This should just require adding a flag(s) to tile entities and an additional step to the block update logic). Maybe I&apos;m wrong, and this would break other things, or harm performance more significantly than I think. And of course, I can think of other (potentially noncompatible) ways to address it.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;In either case, a specific, techically comprehensive, &lt;b&gt;explanation&lt;/b&gt; of this &lt;b&gt;years-old&lt;/b&gt; and wildly frustrating bug would help set expectations for how this will be managed in the future, and what impact it will have on our clumsy workaround designs when it is eventually fixed.&lt;/p&gt;</comment>
                            <comment id="1240328" author="JIRAUSER727829" created="Sat, 25 Feb 2023 01:09:57 +0100"  >&lt;p&gt;Still affects 1.19.63&#160;&lt;/p&gt;</comment>
                            <comment id="1191124" author="talmelamed" created="Wed, 10 Aug 2022 09:26:39 +0200"  >&lt;p&gt;1.19.20 too&lt;/p&gt;</comment>
                            <comment id="1180517" author="JIRAUSER681109" created="Thu, 7 Jul 2022 15:24:55 +0200"  >&lt;p&gt;Still in 1.19.2and 1.19.20.20&lt;/p&gt;</comment>
                            <comment id="831037" author="goldenhelmet" created="Wed, 28 Oct 2020 01:52:02 +0100"  >&lt;p&gt;From &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-103999&quot; title=&quot;Redstone components do not react based on the game tick power is provided&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-103999&quot;&gt;&lt;del&gt;MCPE-103999&lt;/del&gt;&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;In the first video, the piston should extend/be powered like the repeater and redstone dust, but doesn&apos;t because it is processed in a different tick (&quot;consumer&quot; tick)&lt;br/&gt;
&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/344070/344070_C-tick+powering.mp4&quot; title=&quot;C-tick powering.mp4 attached to MCPE-15793&quot;&gt;C-tick powering.mp4&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;&lt;br/&gt;
In the second video, the piston is powered, but the repeater is not, and the dust is VISUALLY not powered, because they are processed in a different tick (&quot;producer&quot; tick)&lt;br/&gt;
 &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/344071/344071_P-tick+powering.mp4&quot; title=&quot;P-tick powering.mp4 attached to MCPE-15793&quot;&gt;P-tick powering.mp4&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;  &lt;br/&gt;
In both situations, the wire, repeater and piston should, logically, all be powered.&lt;br/&gt;
This behavior is not only inconsistent with java, it is also very unintuitive. It makes no sense to behave this way.&lt;/p&gt;&lt;/blockquote&gt;</comment>
                            <comment id="819691" author="ginepik" created="Thu, 1 Oct 2020 13:36:10 +0200"  >&lt;p&gt;Affects 1.16.100&lt;/p&gt;

&lt;p&gt;Affects 1.16.200.56 Beta&lt;/p&gt;</comment>
                            <comment id="807677" author="ginepik" created="Thu, 17 Sep 2020 18:52:43 +0200"  >&lt;p&gt;Affects 1.16.100.56 Beta.&lt;/p&gt;</comment>
                            <comment id="807080" author="ginepik" created="Wed, 16 Sep 2020 09:55:45 +0200"  >&lt;p&gt;Affects 1.16.40 Hotfix.&lt;/p&gt;

&lt;p&gt;Affects 1.16.100.55 Beta.&lt;/p&gt;</comment>
                            <comment id="795960" author="77tigers" created="Wed, 26 Aug 2020 01:01:58 +0200"  >&lt;p&gt;(note: different types of components are powered in alternating gameticks, it may be useful to know to understand why it happens)&lt;/p&gt;

&lt;p&gt;This seems hard to fix without major changes to redstone.&lt;/p&gt;

&lt;p&gt;The issue isn&apos;t with the repeater. The issue is that when a world change happens, the components activated in that tick (often called consumers) aren&apos;t instantly powered/depowered.&lt;/p&gt;

&lt;p&gt;You can either:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;remove the delay and make chains of pistons instantly power/depower each other&lt;/li&gt;
	&lt;li&gt;add extra delay to repeaters from world changes (and other components known as producers)&lt;/li&gt;
	&lt;li&gt;fix it only for player interactions&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The first two would break most redstone builds. The third wouldn&apos;t, but doesn&apos;t really fix the bug fully.&lt;/p&gt;

&lt;p&gt;May I suggest that this is marked as &quot;Won&apos;t fix&quot;?&lt;/p&gt;</comment>
                            <comment id="706206" author="natthan" created="Sun, 24 May 2020 19:21:11 +0200"  >&lt;p&gt;Affects 1.16.0.63&lt;/p&gt;</comment>
                            <comment id="688601" author="JIRAUSER479063" created="Mon, 4 May 2020 17:41:42 +0200"  >&lt;p&gt;Observers showing up to a 3 tick (often randomized) delay on 1.14.60.&lt;/p&gt;</comment>
                            <comment id="667794" author="blobs2" created="Fri, 17 Apr 2020 06:49:14 +0200"  >&lt;p&gt;Affects version 1.14.60.&lt;/p&gt;</comment>
                            <comment id="607441" author="blobs2" created="Sun, 24 Nov 2019 00:43:14 +0100"  >&lt;p&gt;My concern is that if I create redstone contraptions now, and design them to work in spite of this bug, they may break when this bug is fixed. Please fix this ASAP so players can make contraptions that will continue to work in the future.&lt;/p&gt;</comment>
                            <comment id="603127" author="bastireds" created="Sat, 16 Nov 2019 13:06:00 +0100"  >&lt;p&gt;I think this is related but with observers this time.&lt;/p&gt;

&lt;p&gt;I built a flying machine only with sticky pistons and it should work (or at least, I think so). Just look in the attached files to see what happens.&lt;/p&gt;

&lt;p&gt;Sorry if this is not related.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="587394" author="koppergames" created="Sun, 29 Sep 2019 22:04:27 +0200"  >&lt;p&gt;Affects 1.12.1&lt;/p&gt;</comment>
                            <comment id="563351" author="silentwisperer" created="Fri, 5 Jul 2019 06:59:06 +0200"  >&lt;p&gt;Affects 1.11.4&lt;/p&gt;</comment>
                            <comment id="542841" author="handlbar.rick@comcast.net" created="Sat, 4 May 2019 16:26:26 +0200"  >&lt;p&gt;Please remember that the bug tracker is for reporting bugs &lt;b&gt;only&lt;/b&gt;. It is not a discussion forum or a feedback site. &lt;/p&gt;</comment>
                            <comment id="522836" author="junior5a" created="Fri, 1 Mar 2019 00:44:35 +0100"  >&lt;p&gt;&lt;b&gt;Affects&#160;1.11.0.3 beta version&lt;/b&gt;&lt;/p&gt;</comment>
                            <comment id="520892" author="junior5a" created="Thu, 21 Feb 2019 22:24:07 +0100"  >&lt;p&gt;&lt;b&gt;Affects&#160;1.11.0.1&#160;beta version&lt;/b&gt;&lt;/p&gt;</comment>
                            <comment id="515521" author="zohan" created="Tue, 29 Jan 2019 14:49:55 +0100"  >&lt;p&gt;There is still a problem with the monostable circuits&lt;/p&gt;</comment>
                            <comment id="489713" author="mistahtokyo" created="Wed, 19 Sep 2018 01:17:02 +0200"  >&lt;p&gt;Source? ^&lt;/p&gt;</comment>
                            <comment id="489652" author="handlbar.rick@comcast.net" created="Tue, 18 Sep 2018 20:02:18 +0200"  >&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;Redacted: May have been inside information that Mojang does not want shared at this time.&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;For the present, the workaround of inserting a dummy repeater on input signal lines pulsed by world events is often enough to ensure the behavior of the circuit is at least predictable.&lt;/p&gt;</comment>
                            <comment id="489636" author="awkwrdtree3" created="Tue, 18 Sep 2018 18:23:46 +0200"  >&lt;p&gt;This is also affecting the Xbox one Bedrock version as of the Sept. 17 of 2018 in the most recent update. Please fix this or tell us if this is an intentional thing.&#160;&lt;/p&gt;</comment>
                            <comment id="473579" author="pc_screen" created="Thu, 19 Jul 2018 17:41:39 +0200"  >&lt;p&gt;Still affects 1.6.0.6&lt;/p&gt;</comment>
                            <comment id="457436" author="pc_screen" created="Fri, 1 Jun 2018 22:14:46 +0200"  >&lt;p&gt;I did some testing on this using the same design in 9 separate locations to make sure there wasn&apos;t any other factor in play. I put a lime concrete block on the ones that were following the intended behavior and red on the others over 2 consecutive runs: &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;169116_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/169116/169116_Screenshot+%2827%29.png&quot; title=&quot;Screenshot (27).png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;169116&quot; file-preview-title=&quot;Screenshot (27).png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/169116/_thumb_169116.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</comment>
                            <comment id="455793" author="mindblown" created="Sat, 26 May 2018 10:08:51 +0200"  >&lt;p&gt;Okay, sorry about that then&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="455789" author="drawesome4333" created="Sat, 26 May 2018 09:39:17 +0200"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=MindBlown&quot; class=&quot;user-hover&quot; rel=&quot;MindBlown&quot;&gt;MindBlown&lt;/a&gt;, Please do not make comments like that, they are not helpful in getting the issue resolved any faster. Thanks.&lt;/p&gt;</comment>
                            <comment id="455435" author="mindblown" created="Fri, 25 May 2018 04:53:37 +0200"  >&lt;p&gt;This has been around since repeaters were added and that was in 0.14.0.  We are now in 1.4.2 and approaching 1.5&lt;/p&gt;</comment>
                            <comment id="454464" author="mrjam003" created="Mon, 21 May 2018 22:23:53 +0200"  >&lt;p&gt;Affects 1.4.0.5&lt;/p&gt;</comment>
                            <comment id="440312" author="bastireds" created="Fri, 9 Mar 2018 10:50:56 +0100"  >&lt;p&gt;I built a monostable circuit and placed a repeater in front of it. It should have given me a short impulse but it didn&apos;t give me anything at all.&lt;br/&gt;
 &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/160172/160172_Monostable+circuit+bogu%C3%A9.mp4&quot; title=&quot;Monostable circuit bogu&#233;.mp4 attached to MCPE-15793&quot;&gt;Monostable circuit bogu&#233;.mp4&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; &lt;br/&gt;
Steps :&lt;br/&gt;
1. Place a block and a redstone dust on it.&lt;br/&gt;
2. Place a sticky piston vertically and a block on it.&lt;br/&gt;
3. Place a block and a repeater on it.&lt;br/&gt;
4. Place a block and a repeater on it before the redstone dust already placed.&lt;br/&gt;
5. Active with a lever or a button, it won&apos;t work as expected.&lt;/p&gt;

&lt;p&gt;Watch the video included if you don&apos;t understand.&lt;/p&gt;</comment>
                            <comment id="433726" author="hytsnbr" created="Thu, 8 Feb 2018 07:10:02 +0100"  >&lt;p&gt;Still affects in 1.2.10.2.&lt;/p&gt;</comment>
                            <comment id="428475" author="husky2490" created="Fri, 12 Jan 2018 09:07:25 +0100"  >&lt;p&gt;&lt;del&gt;Can anyone prove if this happens to moving observer blocks?&lt;/del&gt;&lt;/p&gt;

&lt;p&gt;Edit: &lt;del&gt;I&apos;m going to try my hand at it&lt;/del&gt; Sorry, what I&apos;m thinking of is probably a different issue&lt;/p&gt;</comment>
                            <comment id="428474" author="husky2490" created="Fri, 12 Jan 2018 09:05:11 +0100"  >&lt;p&gt;I originally posted this to &lt;span class=&quot;error&quot;&gt;&amp;#91;MCPE-25360&amp;#93;&lt;/span&gt; but I think it belongs here more&lt;/p&gt;

&lt;p&gt;I captured this behavior today in slow-mo with the help of a &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/155159/155159_One-tick+debug.ahk&quot; title=&quot;One-tick debug.ahk attached to MCPE-15793&quot;&gt;macro script&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;  (Uses AutoHotkey v1.1; run then press ALT+k to activate). The &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/155160/155160_Pistons%2C+repeaters%2C+and_or+redstone+update+bug%28s%29.gif&quot; title=&quot;Pistons, repeaters, and_or redstone update bug(s).gif attached to MCPE-15793&quot;&gt;GIF with a very long name&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; contains 10 images, 5 covering the rising edge and 5 covering the falling edge, representing 0.005 second intervals beginning with 0.005 seconds after clicking the lever. Due to issues with Windows not saving screenshots, images were captured individually on sequential runs.&lt;/p&gt;

&lt;p&gt; &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/attachment/155160/155160_Pistons%2C+repeaters%2C+and_or+redstone+update+bug%28s%29.gif&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt; &lt;/p&gt;</comment>
                            <comment id="418686" author="hytsnbr" created="Sun, 19 Nov 2017 11:19:06 +0100"  >&lt;p&gt;Still affects in 1.2.6.2.&lt;/p&gt;</comment>
                            <comment id="414300" author="zebulanstanphill@gmail.com" created="Tue, 24 Oct 2017 20:12:57 +0200"  >&lt;p&gt;I can confirm this is still happening as of 1.2.5 build 2 on Windows 10. Pistons appear to be slightly faster than before, but that didn&apos;t fix this bug (though it may make working around the bug in contraptions a little easier).&lt;/p&gt;</comment>
                            <comment id="414236" author="pneuma" created="Tue, 24 Oct 2017 10:03:20 +0200"  >&lt;p&gt;Still affects in 1.2.5.13&lt;/p&gt;</comment>
                            <comment id="410935" author="handlbar.rick@comcast.net" created="Thu, 5 Oct 2017 16:06:51 +0200"  >&lt;p&gt;@r.takahashi Although the pistons are clearly getting pulsed at the same time, if you look closely you can see that the redstone dust next to the repeater is being activated 1 tick after the piston.&lt;/p&gt;</comment>
                            <comment id="410902" author="pneuma" created="Thu, 5 Oct 2017 10:32:25 +0200"  >&lt;p&gt;MaladjustedPlatypus  &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/attachment/148330/148330_pe_redstone.gif&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt; I tested this way.&lt;br/&gt;
But, Re-affected on 1.2.2.&lt;/p&gt;</comment>
                            <comment id="410188" author="mistahtokyo" created="Sun, 1 Oct 2017 09:53:43 +0200"  >&lt;p&gt;^ Still occurring in 1.2.1.1. How did you test this?&lt;/p&gt;</comment>
                            <comment id="409683" author="pneuma" created="Fri, 29 Sep 2017 00:49:01 +0200"  >&lt;p&gt;I can&apos;t confirmed on 1.2.1.1.&lt;br/&gt;
Probably fixed.&lt;/p&gt;</comment>
                            <comment id="378875" author="zebulanstanphill@gmail.com" created="Thu, 20 Apr 2017 06:28:39 +0200"  >&lt;p&gt;In 1.1.0.5, the behavior has reverted to what is was like pre-1.1.0.0... still broken, but less broken. &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/tongue.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="378225" author="zebulanstanphill@gmail.com" created="Sat, 15 Apr 2017 22:14:21 +0200"  >&lt;p&gt;Revised title yet again to be even more descriptive of the issue.&lt;/p&gt;</comment>
                            <comment id="375469" author="zebulanstanphill@gmail.com" created="Sun, 2 Apr 2017 01:59:15 +0200"  >&lt;p&gt;Now even worse in 1.1.0.0... previously, repeaters set to 1 rs tick delay seemed to have no delay compared to just redstone dust. Now, a repeater set to a 2 rs tick (4 game tick) delay also seems to have no delay compared to redstone dust. This breaks almost everything that relies on redstone timing. (And most contraptions were already having to use extra delay to ensure things were activated in the right order... now they need even more.)&lt;/p&gt;</comment>
                            <comment id="374293" author="zebulanstanphill@gmail.com" created="Mon, 27 Mar 2017 21:39:38 +0200"  >&lt;p&gt;Revised title again, since this is not a bug exclusive to delays from repeaters, but delays from comparators, redstone torches, and other redstone delayers.&lt;/p&gt;</comment>
                            <comment id="355579" author="zebulanstanphill@gmail.com" created="Mon, 23 Jan 2017 22:27:58 +0100"  >&lt;p&gt;Re-opening, as this was incorrectly closed as a dupe of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13983&quot; title=&quot;Delay of repeaters can be ignored in some cases&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13983&quot;&gt;&lt;del&gt;MCPE-13983&lt;/del&gt;&lt;/a&gt;, which was a separate bug which has now been fixed. I have copied over the information provided by &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=talaeus&quot; class=&quot;user-hover&quot; rel=&quot;talaeus&quot;&gt;talaeus&lt;/a&gt; relating to this bug and added it to the description. Also revised the report title and attached the relevant screenshots from &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; &amp;amp; &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-17274&quot; title=&quot;Repeaters add random delay to pistons (but not to other components)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-17274&quot;&gt;&lt;del&gt;MCPE-17274&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="334299" author="zebulanstanphill@gmail.com" created="Mon, 10 Oct 2016 04:09:00 +0200"  >&lt;p&gt;Affects 0.15.10 &amp;amp; 0.15.90.8 (0.16.0 beta build 5).&lt;/p&gt;</comment>
                            <comment id="322511" author="siphio" created="Fri, 29 Jul 2016 09:06:38 +0200"  >&lt;p&gt;Still broken in 15.4. &lt;/p&gt;</comment>
                            <comment id="320043" author="siphio" created="Fri, 8 Jul 2016 14:32:31 +0200"  >&lt;p&gt;Still a problem in 0.15.2&lt;/p&gt;</comment>
                            <comment id="319879" author="siphio" created="Thu, 7 Jul 2016 14:42:16 +0200"  >&lt;p&gt;I can confirm that driving the last stage of your input chain with a redstone block on a piston &lt;b&gt;does&lt;/b&gt; work as a fix (with as many relays running into the redstone block piston as you need). This leads me to believe it&apos;s a problem with the way piston timing and redstone timings interact. &lt;/p&gt;</comment>
                            <comment id="318436" author="lloydaz" created="Thu, 30 Jun 2016 05:49:26 +0200"  >&lt;p&gt;I had something similar.  I was working on an automated melon farm using the observer block.  I had the farm working correctly last night, and when I looked at it today, two of the repeaters in the circuit would not activate.  I removed the repeaters and put down two new ones and the circuit began to work again.&lt;/p&gt;

&lt;p&gt;I was testing this on a Windows 10 Edition.  I can attach a download of the world if you need it.&lt;/p&gt;</comment>
                            <comment id="315702" author="depressed-pho" created="Wed, 22 Jun 2016 09:34:25 +0200"  >&lt;p&gt;Interesting. It is possible that this one and &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; stem from the same root cause.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="149814">MCPE-17208</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="150107">MCPE-17274</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="166727">MCPE-20762</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="166917">MCPE-20859</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="167026">MCPE-20904</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="167641">MCPE-21087</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="168388">MCPE-21281</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="177538">MCPE-24278</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="180327">MCPE-25859</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="182891">MCPE-27516</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="184587">MCPE-28387</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="185241">MCPE-28623</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="185350">MCPE-28657</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="185513">MCPE-28690</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="187083">MCPE-29171</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="191591">MCPE-30678</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="192159">MCPE-30888</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="195055">MCPE-31399</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="195502">MCPE-31470</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="196647">MCPE-31790</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="199578">MCPE-33011</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="201963">MCPE-33825</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="207364">MCPE-35543</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="211996">MCPE-36786</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="214181">MCPE-37625</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="225212">MCPE-41017</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="230346">MCPE-42968</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="281094">MCPE-60278</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="317576">MCPE-75293</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="340571">MCPE-84280</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="369325">MCPE-98587</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="380246">MCPE-103691</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="380935">MCPE-103999</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="457579">MCPE-136762</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="494920">MCPE-152120</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="515187">MCPE-161802</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="527718">MCPE-167483</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="540155">MCPE-173858</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="559646">MCPE-182268</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="213795">MCPE-37479</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="132752">MCPE-12848</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="144071">MCPE-15607</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="147119">MCPE-16371</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="203304">MCPE-34207</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="505074">MCPE-156762</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="351622">MCPE-89921</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="173727">MCPE-22741</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="177538">MCPE-24278</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="185296">MCPE-28647</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="409712">MCPE-116576</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="344070" name="C-tick powering.mp4" size="837324" author="GoldenHelmet" created="Wed, 28 Oct 2020 01:51:32 +0100"/>
                            <attachment id="120422" name="IMG_1634.PNG" size="1632352" author="Siphio" created="Tue, 21 Jun 2016 22:13:24 +0200"/>
                            <attachment id="136032" name="MCPE-15793 Direct VS Delayed Power Examples.png" size="3425359" author="SuperGeniusZeb" created="Fri, 31 Mar 2017 07:14:15 +0200"/>
                            <attachment id="132672" name="MCPE-15793 Piston Example A.png" size="402278" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:42:16 +0100"/>
                            <attachment id="132673" name="MCPE-15793 Piston Example B.png" size="407717" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:42:16 +0100"/>
                            <attachment id="160172" name="Monostable circuit bogu&#233;.mp4" size="5169666" author="BastiReds" created="Fri, 9 Mar 2018 10:46:07 +0100"/>
                            <attachment id="155159" name="One-tick debug.ahk" size="881" author="husky2490" created="Fri, 12 Jan 2018 09:04:02 +0100"/>
                            <attachment id="344071" name="P-tick powering.mp4" size="368398" author="GoldenHelmet" created="Wed, 28 Oct 2020 01:51:37 +0100"/>
                            <attachment id="155160" name="Pistons, repeaters, and_or redstone update bug(s).gif" size="4759085" author="husky2490" created="Fri, 12 Jan 2018 09:04:10 +0100"/>
                            <attachment id="169116" name="Screenshot (27).png" size="1297052" author="PC_Screen" created="Fri, 1 Jun 2018 22:13:13 +0200"/>
                            <attachment id="132674" name="Screenshot_2016-09-26-07-23-15.png" size="936169" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:48:23 +0100"/>
                            <attachment id="132675" name="Screenshot_2016-09-26-07-23-32.png" size="935874" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:48:23 +0100"/>
                            <attachment id="132676" name="Screenshot_2016-09-26-07-24-00.png" size="863559" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:48:23 +0100"/>
                            <attachment id="132677" name="Screenshot_2016-09-26-07-24-10.png" size="876822" author="SuperGeniusZeb" created="Mon, 23 Jan 2017 22:48:23 +0100"/>
                            <attachment id="148330" name="pe_redstone.gif" size="623412" author="pneuma" created="Thu, 5 Oct 2017 10:30:09 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>32788, 36225, 176093</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 13 Feb 2019 14:24: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_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>42.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>iOS 9.3.2</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11503"><![CDATA[Multiple]]></customfieldvalue>

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

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