<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:07:31 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-5321] noClip not honored for entity collisions</title>
                <link>https://bugs.mojang.com/browse/MC-5321</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;When determining entity-on-entity collisions noClip isn&apos;t checked, resulting in a collision when there shouldn&apos;t be one.  Discovered by setting noClip=true, collisionsBox=null, canPush=false, and canCollide=false on an entity and setting width &amp;gt; 3, you can&apos;t approach the entity any closer than the bounding box.&lt;/p&gt;

&lt;p&gt;Work-around:  added check for noClip in World.java:getCollidingBoundingBoxes @ 4465 when iterating through bounding boxes (yes, I know this is from a decompile, but that should put you in the ballpark).&lt;/p&gt;

&lt;p&gt;Application:  parent entity with multiple child entities must have a bounding box encompassing all children, otherwise the collision detection doesn&apos;t work correctly (separate bug?).  my parent entity is longer than it is wide, but bounding box uses width X width for size, so there&apos;s a lot of &quot;empty space&quot; on the sides.  actual collision detection is handled by child entities, so parent entity needs to ignore collisions (hence use of noClip et al).&lt;/p&gt;</description>
                <environment>Linux, Sun Java 1.6, Forge 770</environment>
        <key id="17913">MC-5321</key>
            <summary>noClip not honored for entity collisions</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>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="awger">Steve Edwards</reporter>
                        <labels>
                            <label>world</label>
                    </labels>
                <created>Mon, 24 Dec 2012 20:14:34 +0100</created>
                <updated>Sun, 3 May 2015 06:22:25 +0200</updated>
                            <resolved>Sat, 5 Jul 2014 18:04:50 +0200</resolved>
                                    <version>Minecraft 1.4.5</version>
                    <version>Minecraft 1.4.6</version>
                    <version>Minecraft 1.4.7</version>
                    <version>Minecraft 1.5.1</version>
                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="170984" author="torabi" created="Sat, 5 Jul 2014 18:04:51 +0200"  >&lt;p&gt;Even if it wasn&apos;t a modded client, it&apos;s not clear how this applies to vanilla Minecraft.&lt;/p&gt;</comment>
                            <comment id="170921" author="themeaningofblah" created="Sat, 5 Jul 2014 15:56:37 +0200"  >&lt;p&gt;I think the mods probably didn&apos;t have a good look at the enviroment:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;Environment:
Linux, Sun Java 1.6, *Forge 770*&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Therefore, this ticket should&apos;ve been invalid in the first place, as it relates to a modified client, unless it can be reproduced in Vanilla.&lt;/p&gt;</comment>
                            <comment id="159940" author="jar_" created="Sun, 25 May 2014 09:37:47 +0200"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;14w21b&lt;/b&gt; / Launcher version &lt;b&gt;1.4.4&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="148636" author="jar_" created="Sun, 23 Mar 2014 10:42:42 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;14w11b&lt;/b&gt; / Launcher version &lt;b&gt;1.3.11&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="121432" author="talven81" created="Tue, 26 Nov 2013 21:06:19 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.7.4&lt;/b&gt; / Launcher version &lt;b&gt;1.3.8&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="60102" author="awger" created="Sat, 13 Apr 2013 03:31:16 +0200"  >&lt;p&gt;Work-around now @ line 1695:&lt;/p&gt;

&lt;p&gt;if (axisalignedbb1 != null &amp;amp;&amp;amp; !((Entity)list.get(j2)).noClip &amp;amp;&amp;amp; axisalignedbb1.intersectsWith(par2AxisAlignedBB))&lt;/p&gt;</comment>
                            <comment id="60100" author="awger" created="Sat, 13 Apr 2013 03:19:24 +0200"  >&lt;p&gt;Verified, still a problem in 1.5.1&lt;/p&gt;</comment>
                            <comment id="59469" author="awger" created="Tue, 9 Apr 2013 02:01:09 +0200"  >&lt;p&gt;Still a problem in 1.4.7 ... catching up on changes in Forge for 1.5.1, will update after testing.&lt;/p&gt;</comment>
                            <comment id="30895" author="awger" created="Wed, 26 Dec 2012 18:55:46 +0100"  >&lt;p&gt;I don&apos;t understand your question.&lt;/p&gt;

&lt;p&gt;My reading of the code suggests that there are two separate boxes in play: a bounding box (indicating the size extents of the entity) and a collision box (indicating the boundary where a collision should be applied).  In common usage, the two are the same.  For my code, they are not the same.&lt;/p&gt;

&lt;p&gt;noClip is a property of an entity, indicating that collisions shouldn&apos;t be applied to this entity.  canCollide and canPush are similar (but subtly different) indicators.  To my thinking, setting noClip on an entity should allow it to pass through any other entity or block, regardless of the other entity&apos;s noClip setting, and this is not the behavior I&apos;m seeing.&lt;/p&gt;

&lt;p&gt;The code reference I cited checks bounding boxes and then collision boxes, without checking any of the flags.  It may be more proper to not check the bounding box at all, but this is in a utility function that is checking for intersecting boxes, which may be used elsewhere for purposes other than determining whether or not there was a collision.  Checking noClip when iterating through the bounding boxes fixed my fringe case, but I don&apos;t know if it broke anything else.&lt;/p&gt;

&lt;p&gt;The dragon is an entity and uses noClip, but collision detection is &quot;lazy&quot; in that 1) you can&apos;t push it, 2) it&apos;s handled as a square cube (head to tail distance is nominally the same as wingspan), and 3) you&apos;re not going to get close enough to notice the discrepancy &amp;#8211; but if the dragon were to stay still, you would not be able to stand directly in front of or behind the wing because the bounding box would keep you from approaching any closer.&lt;/p&gt;</comment>
                            <comment id="30689" author="zuriki" created="Tue, 25 Dec 2012 15:19:18 +0100"  >&lt;p&gt;Does noClip apply to entity collisions or just world-based collisions (ie. Ender Dragon)?&lt;/p&gt;</comment>
                    </comments>
                    <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_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0drz3:</customfieldvalue>

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