<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:21:20 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-9523] Powered pistons require block update to extend if ability to extend becomes available</title>
                <link>https://bugs.mojang.com/browse/MC-9523</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Pistons that are powered and cannot push forward (because of the amount of blocks in front of the piston or because another piston is pushing the opposite direction) do not extend when they gain the ability to push forward (when the number of blocks is less than the maximum allowed or the opposing piston attracts). These bugged pistons will then extend if any block update is made (placing/removing blocks, extension of an adjacent piston, etc.).&lt;/p&gt;

&lt;p&gt;See the attached world file. In the example, there are two sets of pistons: one with two pistons pushing against each other in opposite directions with 1 space between them, and one with 3 blocks between them. If you remove the power from the extended piston in the first set, the powered piston on the other side will extend (because the retraction of the first piston updates the second piston).&lt;br/&gt;
In the next example, where there are blocks between the two pistons, the first piston&apos;s retraction does not update the second piston and thus the second piston does not retract regardless of it being powered.&lt;/p&gt;</description>
                <environment>Windows 7 64 bit, java 6</environment>
        <key id="23145">MC-9523</key>
            <summary>Powered pistons require block update to extend if ability to extend becomes available</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="-1">Unassigned</assignee>
                                    <reporter username="ianbleaker">Ian</reporter>
                        <labels>
                            <label>block</label>
                            <label>piston</label>
                            <label>redstone</label>
                    </labels>
                <created>Sun, 10 Feb 2013 01:24:29 +0100</created>
                <updated>Fri, 18 Dec 2020 10:16:26 +0100</updated>
                            <resolved>Sun, 10 Feb 2013 01:48:02 +0100</resolved>
                                    <version>Snapshot 13w06a</version>
                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="53169" author="matt5327" created="Thu, 14 Mar 2013 19:54:47 +0100"  >&lt;p&gt;Quite. Not only that, but if checking for updates was really the problem, then it would have lagged back when it worked - which it has since the piston was introduced.&lt;/p&gt;</comment>
                            <comment id="53159" author="ianbleaker" created="Thu, 14 Mar 2013 19:35:11 +0100"  >&lt;p&gt;Agreed with Joris. I used to use that timer, and then had to modify it to make it work correctly (the old timer didn&apos;t make it lag any more than it does now, so I believe it is bug-related rather than technicality-related).&lt;/p&gt;</comment>
                            <comment id="53157" author="gamemaster676" created="Thu, 14 Mar 2013 19:31:00 +0100"  >&lt;p&gt;But that does not really make sense. In this (&lt;a href=&quot;http://youtu.be/bYwzd62cLSw&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/bYwzd62cLSw&lt;/a&gt;) video by Etho, he shows a hopper timer build in one of the first 1.5 Snapshots. If you build it now in the 1.5 Release, it doesn&apos;t work anymore because of this bug.&lt;/p&gt;</comment>
                            <comment id="44932" author="banana478" created="Sun, 10 Feb 2013 01:48:02 +0100"  >&lt;p&gt;This is for technical reasons. If pistons had to constantly check (when they had power) if they could extend, there would be an enormous amount of lag. This is the reason for the block update system. If a block&apos;s updates had were carried by adjacent blocks, every removal or placement of block would update the entire world, causing the same lag issues.&lt;/p&gt;</comment>
                            <comment id="44931" author="banana478" created="Sun, 10 Feb 2013 01:45:37 +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="26211">MC-11732</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="26569">MC-11856</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="97501">MC-69855</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="232391">MC-146523</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="265047">MC-163680</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="364366">MC-197920</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="21520" name="13w06aPistonBug.rar" size="57900" author="ianbleaker" created="Sun, 10 Feb 2013 01:24:29 +0100"/>
                            <attachment id="21521" name="2013-02-09_19.23.25.png" size="138801" author="ianbleaker" created="Sun, 10 Feb 2013 01:24:29 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 2 May 2015 03:37:00 +0200</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>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0jr7r:</customfieldvalue>

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