<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:52:53 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-979] Players get kicked automatically if another player with the same name joins a server. It should be the opposite.</title>
                <link>https://bugs.mojang.com/browse/MC-979</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Players are able to run two or more instances of Minecraft on a single computer, and were able to login successfully in the instances of Minecraft running on that computer. (Hence, the environment is generic.) I&apos;ll assume this behavior is correct.&lt;/p&gt;

&lt;p&gt;Since they are able to run two or more instances of Minecraft, they have the ability to join a server with matching account names. The first instance of Minecraft is named as A, the second instance is named as B, and the server that both instances, A and B, wants to log into is named as S.&lt;/p&gt;

&lt;p&gt;Currently, it goes like this:&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;A logs in to S.&lt;/li&gt;
	&lt;li&gt;B logs in to S.&lt;/li&gt;
	&lt;li&gt;Since B&apos;s name is the same as A&apos;s, S kicks A, and lets B in.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;What it should really be is this:&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;A logs in to S.&lt;/li&gt;
	&lt;li&gt;B logs in to S.&lt;/li&gt;
	&lt;li&gt;Since B&apos;s name is the same as A&apos;s, S checks the IP addresses of both A and B.&lt;/li&gt;
	&lt;li&gt;S &lt;b&gt;kicks B&lt;/b&gt;, and keep A in, because their IP addresses are a match.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;em&gt;OR in the case of different users, it should use its old method:&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;S &lt;b&gt;kicks A&lt;/b&gt;, and let B in, because their IP addresses are not a match.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;This affects only a minority of the Minecraft players out there, but this is still an issue that exists since Alpha 1.1_02, meaning that it affects all versions of Minecraft. This issue was not visible to Mojang in GetSatisfaction due to low vote counts and low comments.&lt;/p&gt;</description>
                <environment>* Any OS&lt;br/&gt;
* Any graphics card with OpenGL 2.0 or above&lt;br/&gt;
* Any CPU with at least 1 GHz.&lt;br/&gt;
&lt;br/&gt;
In short, it a generic category.</environment>
        <key id="12276">MC-979</key>
            <summary>Players get kicked automatically if another player with the same name joins a server. It should be the opposite.</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="tom_mai78101">Tom Lee</reporter>
                        <labels>
                            <label>multiplayer</label>
                            <label>server</label>
                    </labels>
                <created>Sun, 28 Oct 2012 04:21:32 +0100</created>
                <updated>Sat, 9 Feb 2013 23:20:27 +0100</updated>
                            <resolved>Tue, 30 Oct 2012 09:07:47 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="15328" author="dinnerbone" created="Tue, 30 Oct 2012 09:07:41 +0100"  >&lt;p&gt;But that&apos;s the issue of the server. The server would have been set to offline mode to let them on, and we do not support offline mode. Yes, it&apos;s insecure and annoying that it&apos;ll kick some users off, but that&apos;s the very nature and purpose of offline mode.&lt;/p&gt;

&lt;p&gt;Closing this off.&lt;/p&gt;</comment>
                            <comment id="15157" author="tom_mai78101" created="Mon, 29 Oct 2012 20:36:15 +0100"  >&lt;p&gt;To Dinnerbone,&lt;/p&gt;

&lt;p&gt;There is however another valid scenario, and that&apos;s when the session server is down. If that happens, two instances of Minecraft can&apos;t check the user, and allows the user to play Minecraft offline.&lt;/p&gt;

&lt;p&gt;When both instances of Minecraft, with offline statuses and running on the same computer, log into the same server, it is possible that it will happen with the way I describe it.&lt;/p&gt;</comment>
                            <comment id="15001" author="bahzur" created="Mon, 29 Oct 2012 15:01:26 +0100"  >&lt;p&gt;No matter how you wrap it, its still a request. As Dinnerbone said, theres a purpose for that behaviour.&lt;/p&gt;</comment>
                            <comment id="14963" author="dinnerbone" created="Mon, 29 Oct 2012 12:50:15 +0100"  >&lt;p&gt;It works this way because the only valid scenario where you will have two authorized users with the same details on the same server is because a session was cut short and the newer one is to replace the old one. I see no reason to change this.&lt;/p&gt;</comment>
                            <comment id="14936" author="tom_mai78101" created="Mon, 29 Oct 2012 10:23:56 +0100"  >&lt;p&gt;To Raphael,&lt;/p&gt;

&lt;p&gt;I don&apos;t believe this warrents a feature request, but rather, it&apos;s a suggestive workaround to this &quot;problem&quot;. May I ask where should I rephrase so that it doesn&apos;t sound like it&apos;s a feature request?&lt;/p&gt;</comment>
                            <comment id="14705" author="daedalusyoung" created="Sun, 28 Oct 2012 15:04:19 +0100"  >&lt;p&gt;This possibly works like this because when a player crashes, or loses network connection or otherwise gets disconnected, but this update does not reach the server, it still thinks the player is logged in. Then when the player relogs and gets back on the server, the server &apos;realizes&apos; that the first player is a ghost and so it kicks him.&lt;/p&gt;

&lt;p&gt;At least I&apos;ve seen this happen on IRC servers, people getting disconnected while they still appear to be in chat.&lt;/p&gt;</comment>
                            <comment id="14703" author="bahzur" created="Sun, 28 Oct 2012 15:00:41 +0100"  >&lt;p&gt;I believe that this wont get recognized here, because its a feature request, not a bug. : /&lt;br/&gt;
The current behaviour is what most programms (not only Minecraft) do if the same persons joins the same server.&lt;/p&gt;</comment>
                            <comment id="14681" author="tom_mai78101" created="Sun, 28 Oct 2012 13:24:22 +0100"  >&lt;p&gt;To Cad&apos;ika Orade,&lt;/p&gt;

&lt;p&gt;Just to clarify, I am only specifically talking about logging into two Minecraft programs in a single computer. I didn&apos;t say logging into Minecraft on two or more separate computers, else it wouldn&apos;t be a problem in the first place. &lt;/p&gt;</comment>
                            <comment id="14609" author="cadika_orade" created="Sun, 28 Oct 2012 05:08:13 +0100"  >&lt;p&gt;Weird.&lt;/p&gt;

&lt;p&gt;How is it that someone is using your account to log into the same server as you? Was your account stolen?&lt;br/&gt;
EDIT: Kudos on making a decent report! &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/biggrin.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>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="14044">MC-2418</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_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|i0myyn:</customfieldvalue>

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