<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:10:22 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-6184] Piston-pushed block behavior altered</title>
                <link>https://bugs.mojang.com/browse/MC-6184</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;In 1.4.6 and before, when the block a pressure plate rested on was pushed by a piston, it would remain in place if ta valid block remained underneath it. First two images show this behavior in 1.4.6. In snapshot 13w01b, any block movement under a pressure plate will cause it to pop off and become an item, even if the block that is moved underneath the pressure plate would be a valid block to place one on. Next two images show this behavior. &lt;/p&gt;

&lt;p&gt;My testing shows this change also affects vines, ladders, snow, levers, and all types of rails, buttons, torches in addition to pressure plates. There may be other blocks I&apos;m missing. The behavior of paintings and item frames seems unaffected by this change though.&lt;/p&gt;

&lt;p&gt;Unsure if this is the new intended behavior of these blocks or is a side effect of the changes to pistons etc. The old behavior would definitely have some nice applications now with the weighted pressure plates and hoppers though (swapping fences for solid blocks and vice versa). Really, if the old behavior was not intended to persist, I don&apos;t quite see why weighted pressure plates were created at all.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18847">MC-6184</key>
            <summary>Piston-pushed block behavior altered</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="zchambers">Zane Chambers</reporter>
                        <labels>
                            <label>piston</label>
                            <label>pressure-plate</label>
                            <label>redstone</label>
                    </labels>
                <created>Sat, 5 Jan 2013 06:37:17 +0100</created>
                <updated>Mon, 7 Sep 2015 19:50:26 +0200</updated>
                            <resolved>Sun, 6 Jan 2013 04:51:28 +0100</resolved>
                                    <version>Snapshot 13w01b</version>
                                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="33502" author="bljat" created="Sun, 6 Jan 2013 04:51:28 +0100"  >&lt;p&gt;Resolving as intended because of fixes of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-3287&quot; title=&quot;Inconsistency with pistons pushing items &quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-3287&quot;&gt;&lt;del&gt;MC-3287&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://bugs.mojang.com/browse/MC-5621&quot; title=&quot;Blocks like redstone dust, repeaters, doors, and levers don&amp;#39;t drop when the underlying block is pushed by a piston&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-5621&quot;&gt;&lt;del&gt;MC-5621&lt;/del&gt;&lt;/a&gt;. For feature suggestions/changes please use the &lt;a href=&quot;http://www.minecraftforum.net/forum/1-suggestions/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;MineCraft Forums: Suggestions&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="33493" author="banana478" created="Sun, 6 Jan 2013 04:34:12 +0100"  >&lt;p&gt;It seems intended to me too. Also, the reason it doesn&apos;t happen with item frames and paintings is that they are entities and don&apos;t update via the block update system. They constantly check for a block behind them and can easily miss the small amount of time in which there is no block behind them.&lt;/p&gt;</comment>
                            <comment id="33473" author="ppersonn" created="Sun, 6 Jan 2013 03:51:40 +0100"  >&lt;p&gt;I hope this isn&apos;t intended. This has been such a useful feature for me and I&apos;m not sure why it would ever be considered a bug..&lt;/p&gt;</comment>
                            <comment id="33329" author="zchambers" created="Sat, 5 Jan 2013 19:56:55 +0100"  >&lt;p&gt;Dangit, I hope not&lt;/p&gt;</comment>
                            <comment id="33078" author="howzieky" created="Sat, 5 Jan 2013 06:47:10 +0100"  >&lt;p&gt;I believe that is intended&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="18254">MC-5621</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="15271">MC-3287</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="17099" name="2013-01-05_00.09.08.png" size="472157" author="zchambers" created="Sat, 5 Jan 2013 06:37:18 +0100"/>
                            <attachment id="17100" name="2013-01-05_00.09.14.png" size="473657" author="zchambers" created="Sat, 5 Jan 2013 06:37:18 +0100"/>
                            <attachment id="17101" name="2013-01-05_00.20.50.png" size="318346" author="zchambers" created="Sat, 5 Jan 2013 06:37:18 +0100"/>
                            <attachment id="17102" name="2013-01-05_00.20.52.png" size="319226" author="zchambers" created="Sat, 5 Jan 2013 06:37:18 +0100"/>
                    </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_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>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0gjpb:</customfieldvalue>

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