<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:26:33 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-11107] Sticky Pistons will not drop blocks in some setups.</title>
                <link>https://bugs.mojang.com/browse/MC-11107</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;A sticky piston powered as in the picture below will create less than one tick pulses but the piston still holds on to the block. Powering the repeater to the left causes this. What I would expect to happen is the block to be left in the extended position as it does in nearly every other setup with 1 tick or shorter pulses.&lt;/p&gt;</description>
                <environment></environment>
        <key id="25207">MC-11107</key>
            <summary>Sticky Pistons will not drop blocks in some setups.</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="10001">Awaiting Response</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="amh11706">Andrew</reporter>
                        <labels>
                    </labels>
                <created>Wed, 6 Mar 2013 02:42:02 +0100</created>
                <updated>Sun, 9 Feb 2020 10:50:41 +0100</updated>
                            <resolved>Sun, 9 Feb 2020 10:50:40 +0100</resolved>
                                    <version>Minecraft 1.4.7</version>
                    <version>Snapshot 13w10a</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Snapshot 13w18c</version>
                    <version>Snapshot 13w19a</version>
                    <version>Minecraft 1.6.1</version>
                    <version>Minecraft 1.6.2</version>
                    <version>Minecraft 1.7.10</version>
                    <version>Minecraft 14w30b</version>
                    <version>Minecraft 14w30c</version>
                    <version>Minecraft 1.9</version>
                    <version>Minecraft 1.9.1 Pre-Release 3</version>
                    <version>Minecraft 1.10.2</version>
                    <version>Minecraft 16w44a</version>
                    <version>Minecraft 1.12 Pre-Release 6</version>
                    <version>Minecraft 1.13.2</version>
                    <version>Minecraft 18w47a</version>
                    <version>Minecraft 18w47b</version>
                                                                        <votes>3</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="631488" author="miwob" created="Sun, 9 Feb 2020 10:50:41 +0100"  >&lt;p&gt;Please check if that&apos;s still an issue for you in the latest 1.15.2 stable release or the latest 1.16 development snapshot.&lt;/p&gt;</comment>
                            <comment id="503807" author="dicotheredstoner" created="Thu, 29 Nov 2018 01:59:05 +0100"  >&lt;p&gt;@Connor Steppie&lt;/p&gt;

&lt;p&gt;I can reproduce this in 18w47b.&lt;/p&gt;</comment>
                            <comment id="503759" author="awesoman3000" created="Wed, 28 Nov 2018 23:53:56 +0100"  >&lt;p&gt;Cannot reproduce in 18w47b&lt;/p&gt;</comment>
                            <comment id="337709" author="miwob" created="Tue, 25 Oct 2016 18:16:18 +0200"  >&lt;p&gt;Is this still an issue in the most recent versions (currently that is &lt;b&gt;1.10.2&lt;/b&gt;, or &lt;b&gt;16w42a&lt;/b&gt;) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.&lt;/p&gt;</comment>
                            <comment id="295813" author="dicotheredstoner" created="Sun, 20 Mar 2016 16:37:53 +0100"  >&lt;p&gt;To quickly clarify why this bug occurs:&lt;br/&gt;
When the piston pushes the block, it does not update directly after. The first update comes from finishing the extension, after 1.5 ticks. Thus, the piston starts its retraction 1.5 ticks after extending, making it not leave the block behind, because for that it needs to extend for less than 1.5 ticks (most often referred to as receiving a 1-tick pulse).&lt;/p&gt;

&lt;p&gt;To confirm this, you can have a repeater coming from the redstone dust that powers the piston, which updates the piston (without powering it).&lt;/p&gt;

&lt;p&gt;This is not necessarily a bug, we might eventually see what Mojang thinks of it. If it were fixed, many buds would definitely break, such as the sticky piston with a slimeblock and a redstone block bud, or the one with glass and sand on top. Thus I would prefer to see this report&apos;s solution also become &apos;works as intended&apos;. Generally, redstone changes are bad, because they often break many contraptions that rely on current redstone mechanics. This one certainly would break quite a few if it were Fixed.&lt;/p&gt;</comment>
                            <comment id="295515" author="amh11706" created="Sat, 19 Mar 2016 01:47:00 +0100"  >&lt;p&gt;Yes, this still happens in 1.9.1-pre3. Now that the related piston report is &apos;works as intended&apos; I believe we can agree this is not intended behavior &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="295340" author="JIRAUSER71590" created="Fri, 18 Mar 2016 17:10:50 +0100"  >&lt;p&gt;Is this still an issue in 1.9 or 1.9.1-pre3?&lt;/p&gt;</comment>
                            <comment id="218787" author="kingsupernova" created="Thu, 12 Feb 2015 14:29:25 +0100"  >&lt;p&gt;Agreed. Which is why &lt;a href=&quot;https://bugs.mojang.com/browse/MC-5726&quot; title=&quot;Sticky pistons do not retract a block which they have pushed when given a short pulse&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-5726&quot;&gt;&lt;del&gt;MC-5726&lt;/del&gt;&lt;/a&gt; should be fixed. If it is fixed, this won&apos;t be an issue anymore. Until then, this still isn&apos;t a bug. This is what&apos;s supposed to happen, you&apos;re just used to the bug happening, so you see this as a bug itself.&lt;/p&gt;</comment>
                            <comment id="218786" author="amh11706" created="Thu, 12 Feb 2015 14:00:44 +0100"  >&lt;p&gt;Invalid? This bug is about more than leaving the block behind or not... The idea here is that in the majority of configurations the pistons will leave blocks behind with a short pulse but in this one it will not. An inconsistency is bad regardless of which outcome was intended.&lt;/p&gt;</comment>
                            <comment id="218749" author="kingsupernova" created="Thu, 12 Feb 2015 05:14:32 +0100"  >&lt;p&gt;Confirmed in 1.8.2-pre6, but see my previous comment as to why this is invalid.&lt;/p&gt;</comment>
                            <comment id="217882" author="kingsupernova" created="Mon, 2 Feb 2015 12:25:23 +0100"  >&lt;p&gt;This is not actually a bug, it&apos;s an exception to &lt;a href=&quot;https://bugs.mojang.com/browse/MC-5726&quot; title=&quot;Sticky pistons do not retract a block which they have pushed when given a short pulse&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-5726&quot;&gt;&lt;del&gt;MC-5726&lt;/del&gt;&lt;/a&gt;. If &lt;a href=&quot;https://bugs.mojang.com/browse/MC-5726&quot; title=&quot;Sticky pistons do not retract a block which they have pushed when given a short pulse&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-5726&quot;&gt;&lt;del&gt;MC-5726&lt;/del&gt;&lt;/a&gt; is resolved as WAI, then this will become a legitimate bug, but until then, this is intended behavior.&lt;/p&gt;</comment>
                            <comment id="205325" author="galaxy_2alex" created="Sat, 25 Oct 2014 14:40:14 +0200"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.8.1 Prerelease 3&lt;/b&gt; / Launcher version &lt;b&gt;1.5.3&lt;/b&gt; or later? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="182300" author="amh11706" created="Wed, 30 Jul 2014 18:09:12 +0200"  >&lt;p&gt;In earlier versions, the piston would leave the block behind. This was quite useful as a mono stable circuit that only fires once until it gets reset (pulling the block back in). I had a segmented farm setup that took advantage of this nicely. The piston removes its power source the instant it is powered, so it should create a &amp;lt;1 tick pulse and leave the block behind. &quot;Fixing&quot; it by adding another piston isn&apos;t very practical in survival and/or compact setups.&lt;/p&gt;</comment>
                            <comment id="182287" author="dicotheredstoner" created="Wed, 30 Jul 2014 17:38:53 +0200"  >&lt;p&gt;I just want to point out that this is not a bug to start with. It makes total sense.  (And it&apos;s useful.)&lt;br/&gt;
The easiest way to fix it is to attach another piston to the block which when pushed updates the sticky piston.&lt;/p&gt;</comment>
                            <comment id="180405" author="amh11706" created="Sat, 26 Jul 2014 23:18:18 +0200"  >&lt;p&gt;Still happens in 14w30c&lt;/p&gt;</comment>
                            <comment id="180273" author="ezekielelin" created="Sat, 26 Jul 2014 20:52:03 +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="50449" author="amh11706" created="Wed, 6 Mar 2013 20:24:11 +0100"  >&lt;p&gt;If this is the case, then why does stringing a line of repeaters after the block to the right show a series of 1 on 2 off pulses? Also, the dust is graphically flickering for less than one tick.&lt;/p&gt;</comment>
                            <comment id="50435" author="dicotheredstoner" created="Wed, 6 Mar 2013 19:26:12 +0100"  >&lt;p&gt;I can explain this.&lt;br/&gt;
in 1.4, a block pushed &lt;em&gt;out&lt;/em&gt; by a piston will actually stop being there after about 1.5 ticks.&lt;br/&gt;
within those 1.5 ticks, there wont be a single update the the dot of redstone behind the block, causing it to stay on for 1.5 ticks. Adding a repeater to the redstone (in 1.5 with another piece of redstone on the end and no block intersections) will cause it to turn off after 1 tick.&lt;br/&gt;
In both 1.5, and 1.4, there is another factor for this not being a 1 tick pulse.&lt;br/&gt;
if a piston gets unpowered for only 1 tick, it will not extend immediately when the power returns. its still retracting. This causes the block to stay for longer, which makes it a 1.5 tick pulse. &lt;/p&gt;</comment>
                            <comment id="50203" author="johnkcraft" created="Wed, 6 Mar 2013 03:54:54 +0100"  >&lt;p&gt;To whom and how do I ask?&lt;/p&gt;</comment>
                            <comment id="50201" author="bljat" created="Wed, 6 Mar 2013 03:48:28 +0100"  >&lt;p&gt;Only Mojang knows.&lt;/p&gt;</comment>
                            <comment id="50199" author="johnkcraft" created="Wed, 6 Mar 2013 03:41:57 +0100"  >&lt;p&gt;Tails, can you explain?&lt;/p&gt;</comment>
                            <comment id="50197" author="johnkcraft" created="Wed, 6 Mar 2013 03:19:10 +0100"  >&lt;p&gt;Also wanted to know why when you place a sticky piston, a boco in front and a torch on top of the block, the piston pushes and pulls back the block. This was to be a pulse of 1 tick.&lt;/p&gt;</comment>
                            <comment id="50195" author="bljat" created="Wed, 6 Mar 2013 02:57:49 +0100"  >&lt;p&gt;Confirmed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="18377">MC-5726</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="23566" name="Sticky Piston.png" size="179489" author="amh11706" created="Wed, 6 Mar 2013 02:54:13 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 6 Mar 2013 02:57:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11901" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Category</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11622"><![CDATA[(Unassigned)]]></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_10501" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Game Mode</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10305"><![CDATA[Creative]]></customfieldvalue>

                        </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|i0594v:</customfieldvalue>

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