<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:25:16 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-10708] Pistons don&apos;t respond to 0 redstone tick pulses at certain occasions</title>
                <link>https://bugs.mojang.com/browse/MC-10708</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;When a piston is powered with a 0 redstone tick pulse (or a half redstone tick pulse, meaning it&apos;s powered for only 1 game tick but not a full redstone tick), it only gives a pulse at some occasions, as it can be seen in the screenshots.&lt;/p&gt;

&lt;p&gt;To reproduce:&lt;br/&gt;
Make a monostable circuit (a sticky piston facing up with a block on top and a repeater pointing at the block), put a piston with a block on its head, next to the monostable circuit (as it can be seen in the screenshots), and power it.&lt;/p&gt;</description>
                <environment>Windows Vista, Windows 8</environment>
        <key id="24679">MC-10708</key>
            <summary>Pistons don&apos;t respond to 0 redstone tick pulses at certain occasions</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="6">Works As Intended</resolution>
                                        <assignee username="searge">[Mojang] Searge (Michael Stoyke)</assignee>
                                    <reporter username="siberianhat">Steve Bob</reporter>
                        <labels>
                            <label>piston</label>
                            <label>redstone</label>
                            <label>unreliable</label>
                    </labels>
                <created>Sat, 2 Mar 2013 01:53:17 +0100</created>
                <updated>Mon, 25 Jun 2018 04:02:36 +0200</updated>
                            <resolved>Tue, 14 Oct 2014 16:56:59 +0200</resolved>
                                    <version>Snapshot 13w09c</version>
                    <version>Snapshot 13w10a</version>
                    <version>Snapshot 13w10b</version>
                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Snapshot 13w18c</version>
                    <version>Snapshot 13w19a</version>
                    <version>Minecraft 1.7.10</version>
                    <version>Minecraft 14w30b</version>
                    <version>Minecraft 14w30c</version>
                    <version>Minecraft 14w31a</version>
                    <version>Minecraft 14w32a</version>
                    <version>Minecraft 14w32b</version>
                    <version>Minecraft 14w32c</version>
                    <version>Minecraft 14w32d</version>
                    <version>Minecraft 14w33c</version>
                    <version>Minecraft 14w34a</version>
                    <version>Minecraft 14w34b</version>
                    <version>Minecraft 14w34c</version>
                    <version>Minecraft 14w34d</version>
                    <version>Minecraft 1.8-pre1</version>
                    <version>Minecraft 1.8-pre2</version>
                    <version>Minecraft 1.8-pre3</version>
                    <version>Minecraft 1.8</version>
                                                                        <votes>15</votes>
                                    <watches>9</watches>
                                                                            <comments>
                            <comment id="463322" author="redcmd" created="Mon, 25 Jun 2018 04:00:59 +0200"  >&lt;p&gt;This bug is not due to pistons.&#160;&lt;/p&gt;

&lt;p&gt;Tho its hard to test without them&lt;br/&gt;
 Its due to block update order XYZ&lt;/p&gt;

&lt;p&gt;So the X-piston checks for power and fires&lt;br/&gt;
 Then the Y-piston checks for power and fires&#160; (which moves the block)&lt;/p&gt;

&lt;p&gt;Then Z-piston checks for power (sees no power due to the block being moved) and doesn&apos;t do anything&lt;/p&gt;

&lt;p&gt;If the block update order was changed from XYZ to XZY or YXZ there would be way less Directional stuff&lt;/p&gt;</comment>
                            <comment id="233826" author="kingsupernova" created="Fri, 10 Jul 2015 10:23:41 +0200"  >&lt;p&gt;Mojang seems to have decided that the purpose of pistons is to have as many inconsistent behaviors as possible. I don&apos;t think any piston-related reports are going to be fixed any time soon.&lt;/p&gt;</comment>
                            <comment id="233795" author="someone314" created="Thu, 9 Jul 2015 22:08:16 +0200"  >&lt;p&gt;please fix this. it breaks more redstone contraptions than it fixes&lt;/p&gt;</comment>
                            <comment id="203980" author="siberianhat" created="Fri, 17 Oct 2014 15:53:00 +0200"  >&lt;p&gt;Leaving the bug like that will also have something broken.&lt;/p&gt;</comment>
                            <comment id="203979" author="munkkiukko" created="Fri, 17 Oct 2014 15:47:59 +0200"  >&lt;p&gt;Maybe fixing that would break something&lt;/p&gt;</comment>
                            <comment id="203491" author="siberianhat" created="Wed, 15 Oct 2014 16:22:11 +0200"  >&lt;p&gt;I&apos;m sorry, but this bug being flagged as &quot;Works as intended&quot; will leave pistons buggy, as they&apos;ve always been. Sincerely, it feels like this bug wasn&apos;t even read by Mojang before being flagged by that.&lt;/p&gt;</comment>
                            <comment id="195687" author="dicotheredstoner" created="Sun, 31 Aug 2014 15:43:55 +0200"  >&lt;p&gt;An easy way to explain this is using &apos;microticks&apos;.&lt;br/&gt;
Each piston which retracts, causes a delay of 1 microtick, this is often seen as &apos;instant&apos;.&lt;br/&gt;
I believe a gametick goes on when all micro ticks have processed and when 0.05 seconds have passed. When you use this monostable, it depends on which piston is updated first.&lt;br/&gt;
When you add a microtick, by pushing a block forward that then lets redstone power through, powering the lower &apos;monostable&apos; piston which is moved above, it will be reliable. It just forces the correct order.&lt;/p&gt;</comment>
                            <comment id="194597" author="siberianhat" created="Wed, 27 Aug 2014 17:32:17 +0200"  >&lt;p&gt;Sand generators were already fixed.&lt;br/&gt;
This change was said to be made with the intention of pistons becoming more &quot;reliable&quot;, but it doesn&apos;t work reliably as you can see in the screenshots in which some pistons get powered and others not, even when getting the same pulse; as well as the title and the description say.&lt;/p&gt;</comment>
                            <comment id="180384" author="siberianhat" created="Sat, 26 Jul 2014 21:30:21 +0200"  >&lt;p&gt;Added more screenshots, updated the affected versions and changed the title as well as the description, explaining better what happens.&lt;/p&gt;</comment>
                            <comment id="180265" author="ezekielelin" created="Sat, 26 Jul 2014 20:52:00 +0200"  >&lt;p&gt;Is this still a concern in the latest Minecraft version &lt;b&gt;14w30c&lt;/b&gt;? 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="52150" author="kc_kennylau" created="Wed, 13 Mar 2013 00:54:00 +0100"  >&lt;p&gt;It seems that the pulse is actually 0.5 tick.&lt;/p&gt;</comment>
                            <comment id="49317" author="yut951121" created="Sun, 3 Mar 2013 12:28:37 +0100"  >&lt;p&gt;Seems like piston monostable circuit&apos;s output is shorter than 1 tick and pistons not responding it.&lt;/p&gt;</comment>
                            <comment id="49316" author="yut951121" created="Sun, 3 Mar 2013 12:27:53 +0100"  >&lt;p&gt;This is really weird because with some specific setup, pistons respond. See &lt;a href=&quot;http://youtu.be/J12aW0hmT98&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/J12aW0hmT98&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="48909" author="bljat" created="Sat, 2 Mar 2013 02:02:44 +0100"  >&lt;p&gt;Confirmed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="25762">MC-11602</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="23005" name="1.jpg" size="83019" author="siberianhat" created="Sat, 2 Mar 2013 01:53:17 +0100"/>
                            <attachment id="23006" name="2.jpg" size="81956" author="siberianhat" created="Sat, 2 Mar 2013 01:53:17 +0100"/>
                            <attachment id="74121" name="2014-07-26_16.15.33.png" size="82362" author="siberianhat" created="Sat, 26 Jul 2014 21:20:39 +0200"/>
                            <attachment id="74122" name="2014-07-26_16.15.36.png" size="90576" author="siberianhat" created="Sat, 26 Jul 2014 21:20:39 +0200"/>
                            <attachment id="74123" name="2014-07-26_16.15.54.png" size="82244" author="siberianhat" created="Sat, 26 Jul 2014 21:20:39 +0200"/>
                            <attachment id="74124" name="2014-07-26_16.15.56.png" size="85881" author="siberianhat" created="Sat, 26 Jul 2014 21:20:39 +0200"/>
                            <attachment id="74125" name="2014-07-26_16.19.59.png" size="100140" author="siberianhat" created="Sat, 26 Jul 2014 21:20:39 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 2 Mar 2013 02:02: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>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i07wtj:</customfieldvalue>

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