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'll assume this behavior is correct.
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.
Currently, it goes like this:
A logs in to S.
B logs in to S.
Since B's name is the same as A's, S kicks A, and lets B in.
What it should really be is this:
A logs in to S.
B logs in to S.
Since B's name is the same as A's, S checks the IP addresses of both A and B.
S kicks B, and keep A in, because their IP addresses are a match.
OR in the case of different users, it should use its old method:
S kicks A, and let B in, because their IP addresses are not a match.
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.
Linked issues
is duplicated by 1
Comments 9
To Cad'ika Orade,
Just to clarify, I am only specifically talking about logging into two Minecraft programs in a single computer. I didn't say logging into Minecraft on two or more separate computers, else it wouldn't be a problem in the first place.
I believe that this wont get recognized here, because its a feature request, not a bug. : /
The current behaviour is what most programms (not only Minecraft) do if the same persons joins the same server.
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 'realizes' that the first player is a ghost and so it kicks him.
At least I've seen this happen on IRC servers, people getting disconnected while they still appear to be in chat.
To Raphael,
I don't believe this warrents a feature request, but rather, it's a suggestive workaround to this "problem". May I ask where should I rephrase so that it doesn't sound like it's a feature request?
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.
No matter how you wrap it, its still a request. As Dinnerbone said, theres a purpose for that behaviour.
To Dinnerbone,
There is however another valid scenario, and that's when the session server is down. If that happens, two instances of Minecraft can't check the user, and allows the user to play Minecraft offline.
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.
Weird.
How is it that someone is using your account to log into the same server as you? Was your account stolen?
EDIT: Kudos on making a decent report! 😃