<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:07:29 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-15391] [Copy of MC-8328] Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &apos;algorithm&apos;)</title>
                <link>https://bugs.mojang.com/browse/MCPE-15391</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;Exactly the same as in Minecraft (&lt;a href=&quot;https://bugs.mojang.com/browse/MC-8328&quot; title=&quot;Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &amp;#39;algorithm&amp;#39;)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-8328&quot;&gt;MC-8328&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Please code a proper block update (order) algorithm!&lt;/p&gt;</description>
            <key id="143697">MCPE-15391</key>
            <summary>[Copy of MC-8328] Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &apos;algorithm&apos;)</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="7">Invalid</resolution>
                                            <reporter username="vin97">Vincent Wiltschek</reporter>
                        <labels>
                    </labels>
                <created>Tue, 14 Jun 2016 05:32:16 +0200</created>
                <updated>Mon, 21 Nov 2016 20:32:19 +0100</updated>
                            <resolved>Mon, 21 Nov 2016 20:32:19 +0100</resolved>
                                    <version>0.15.0</version>
                    <version>0.15.4</version>
                                                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="345332" author="zebulanstanphill@gmail.com" created="Mon, 21 Nov 2016 20:31:50 +0100"  >&lt;p&gt;Resolving as invalid, as I can find no evidence of 0-ticking being a thing in MCPE redstone. (See my previous comment on how the example cases were invalid as they were actually being caused by a separate bug, and by using modified versions of the test which weren&apos;t affected by that bug, the supposed 0-tick behavior did NOT occur, and therefore this was never a bug to begin with.&lt;/p&gt;</comment>
                            <comment id="344138" author="aman4700" created="Fri, 18 Nov 2016 05:34:20 +0100"  >&lt;p&gt;This is a bulk resolve of issues that haven&apos;t been updated to 0.16.0+ yet. Please comment below (To open the ticket) and update your affected versions. If you cannot reproduce the bug, please write in the comments so we can resolve it as &quot;Cannot Reproduce&quot;. Thank You!&lt;/p&gt;</comment>
                            <comment id="335421" author="zebulanstanphill@gmail.com" created="Sun, 16 Oct 2016 19:35:08 +0200"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=vin97&quot; class=&quot;user-hover&quot; rel=&quot;vin97&quot;&gt;vin97&lt;/a&gt; That test is impossible to perform, as MCPE pistons have different timings from Java edition pistons and therefore an instant NOT gate cannot be constructed. See &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;. I am currently investigating this issue, though. There IS definitely some odd timing stuff going on with MCPE redstone, though I&apos;m not sure 0-ticking is one of those things. Keep in mind that MCPE redstone is programmed VERY differently from the Java edition, and seemingly similar problems may be causes by very different things in each edition.&lt;/p&gt;</comment>
                            <comment id="335404" author="vin97" created="Sun, 16 Oct 2016 18:34:33 +0200"  >&lt;p&gt;Please test the bug with pistons as described in my initial report (&lt;a href=&quot;https://bugs.mojang.com/browse/MC-8328&quot; title=&quot;Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &amp;#39;algorithm&amp;#39;)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-8328&quot;&gt;MC-8328&lt;/a&gt;):&lt;br/&gt;
&quot;To replicate it, OR the input of an instant NOT gate (&lt;a href=&quot;http://youtu.be/vCsJWc7PcT0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/vCsJWc7PcT0&lt;/a&gt;) and it&apos;s output together and attach it to another piston. Toggle the input&quot;&lt;/p&gt;</comment>
                            <comment id="334025" author="zebulanstanphill@gmail.com" created="Sat, 8 Oct 2016 06:04:09 +0200"  >&lt;p&gt;&lt;b&gt;WAIT!! I WAS WRONG!&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/attachment/105392/2015-11-22_13.56.56.png&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/secure/attachment/105392/2015-11-22_13.56.56.png&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I built this in MCPE, but what I forgot was that this test would be affected by &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;. Because of this, the test was INVALID. By moving the dispenser one block to the right and by adding another redstone dust between the dispenser and the torch, I found that the dispenser would never fire. This means that MCPE does NOT have 0 ticks! I think this issue can be closed, unless someone can find a legitimate proof of the existence of micropulses in MCPE.&lt;/p&gt;</comment>
                            <comment id="334012" author="zebulanstanphill@gmail.com" created="Sat, 8 Oct 2016 04:12:52 +0200"  >&lt;p&gt;&lt;del&gt;Affects 0.15.10. (Tested on Windows 10.)&lt;/del&gt; See comment below.&lt;/p&gt;</comment>
                            <comment id="324190" author="vin97" created="Mon, 8 Aug 2016 05:45:52 +0200"  >&lt;p&gt;Still the same. Bug not solved.&lt;/p&gt;</comment>
                            <comment id="323685" author="aman4700" created="Mon, 8 Aug 2016 03:48:57 +0200"  >&lt;p&gt;Please respond and add the current version if you can reproduce this issue.&lt;/p&gt;</comment>
                            <comment id="314214" author="vin97" created="Thu, 16 Jun 2016 21:42:24 +0200"  >&lt;p&gt;I gave one way to replicate it in the description of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-8328&quot; title=&quot;Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &amp;#39;algorithm&amp;#39;)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-8328&quot;&gt;MC-8328&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="314204" author="myren" created="Thu, 16 Jun 2016 19:52:34 +0200"  >&lt;p&gt;Can you give an example of a 0 tick pulse monostable for MCPE? Or what exactly did you test in MCPE that made you conclude that there are 0 tick pulses? Because the update system is as far as I can tell very much different from the PC version and I didn&#180;t find any 0 tick technology that works in MCPE.&lt;br/&gt;
Edit: I found something that could be considered to be a 0 tick pulse. Ignore this.&lt;/p&gt;</comment>
                            <comment id="313457" author="vin97" created="Tue, 14 Jun 2016 05:55:58 +0200"  >&lt;p&gt;Yes, exactly.&lt;br/&gt;
Sorry for the duplicate but I could not select &quot;Minecraft Pocket Edition&quot; or &quot;Minecraft for Win10&quot; in the list of affected versions of the original issue.&lt;br/&gt;
If you could add it to the list for me, you could delete this duplicate issue right here.&lt;/p&gt;

&lt;p&gt;The bug has been discussed intensively in the comments section of the original issue (the conclusion is in the original report).&lt;/p&gt;</comment>
                            <comment id="313452" author="fuj1n" created="Tue, 14 Jun 2016 05:42:47 +0200"  >&lt;p&gt;So if I understand correctly, this is an exact same issue as &lt;a href=&quot;https://bugs.mojang.com/browse/MC-8328&quot; title=&quot;Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update &amp;#39;algorithm&amp;#39;)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-8328&quot;&gt;MC-8328&lt;/a&gt;, but applies to Minecraft: Pocket Edition?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="21246">MC-8328</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></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 Pro x86</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|i0kka7:</customfieldvalue>

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