<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:49:50 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-106] Spawn Mob with Stripped metadata crashes the client</title>
                <link>https://bugs.mojang.com/browse/MC-106</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;The client is sensitive to missing metadata in packets sent from the server.&lt;/p&gt;

&lt;p&gt;A typical example is to strip out the metadata and only send the metadata structure with 0 keys.&lt;/p&gt;

&lt;p&gt;Also adding extra values, leaving the existing ones there too does crash the client too. Example in the second attachment, there I added the int value of 123 to the key 73.&lt;/p&gt;</description>
                <environment>java version &amp;quot;1.7.0_07&amp;quot;&lt;br/&gt;
OpenJDK Runtime Environment (IcedTea7 2.3.2) (7u7-2.3.2a-1ubuntu1)&lt;br/&gt;
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)</environment>
        <key id="11351">MC-106</key>
            <summary>Spawn Mob with Stripped metadata crashes the client</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="6" iconUrl="https://bugs.mojang.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="7">Invalid</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="nuxas">Nuxas</reporter>
                        <labels>
                            <label>client</label>
                            <label>crash</label>
                            <label>packets</label>
                    </labels>
                <created>Wed, 24 Oct 2012 19:58:05 +0200</created>
                <updated>Thu, 7 Aug 2014 05:09:58 +0200</updated>
                            <resolved>Thu, 8 Nov 2012 06:30:52 +0100</resolved>
                                    <version>Minecraft 1.4.1</version>
                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="14964" author="dinnerbone" created="Mon, 29 Oct 2012 12:52:35 +0100"  >&lt;p&gt;Some things it needs to know. If you don&apos;t tell it these things, it can&apos;t function. This is just how it is.&lt;/p&gt;</comment>
                            <comment id="14677" author="nuxas" created="Sun, 28 Oct 2012 13:16:55 +0100"  >&lt;p&gt;@Ray Well our proxy is only causing it when I tell it to such as when I want to generate the crash log for this report.&lt;/p&gt;

&lt;p&gt;Yes the Minecraft protocol does change and we catch up all the time, but the development would have been a lot easier if the vanilla client simply disconnected rather than crashed and held the computer for half a minute.&lt;/p&gt;

&lt;p&gt;I did send a similar report for another but that was closed since it did not affect vanilla client &amp;lt;-&amp;gt; vanilla server. I&apos;m still stand that ones client should not crash for packets it receive over the internet, hover since you are of a different opinion you should close this issue too.&lt;/p&gt;

&lt;p&gt;At least it makes a good tool for putting force into the /ban command &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="14669" author="ray73864" created="Sun, 28 Oct 2012 11:46:52 +0100"  >&lt;p&gt;Sounds like the proxy you have developed is causing the issues. Just because the proxy has been working for over a year doesn&apos;t mean it can&apos;t eventually cause an issue, especially when the MC protocols themselves change.&lt;/p&gt;</comment>
                            <comment id="12680" author="cloudy" created="Thu, 25 Oct 2012 00:42:15 +0200"  >&lt;p&gt;While I appreciate the vigor, unless it happens in vanilla and can be caused in vanilla, it isn&apos;t really a bug. The client side doesn&apos;t need to be robust enough to handle these issues, as they will never happen. If a client could trigger this behaviour on the server side though, then I would be worried.&lt;/p&gt;</comment>
                            <comment id="12337" author="nuxas" created="Wed, 24 Oct 2012 20:42:26 +0200"  >&lt;p&gt;I&apos;ve developed a proxy that if nothing else passes on the messages as is. it has been working for over a year so I am rather sure the test changes I do to trigger these bugs are bugs in the client.&lt;/p&gt;</comment>
                            <comment id="12294" author="cloudy" created="Wed, 24 Oct 2012 20:00:59 +0200"  >&lt;p&gt;Does this bug occur in vanilla without interference? How did you &quot;strip out the metadata&quot; or &quot;add extra values&quot;?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="10665" name="mcbug.txt" size="1788" author="nuxas" created="Wed, 24 Oct 2012 19:58:05 +0200"/>
                            <attachment id="10666" name="mcbugwithextra.txt" size="7205" author="nuxas" created="Wed, 24 Oct 2012 19:58:05 +0200"/>
                    </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|i0g0z3:</customfieldvalue>

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