I run Multiple Launchers at a time, because I log into servers with multiple accounts for testing and administration.
1. Chose profile
2. Login
3. Connect to server
4. open second launcher
5. choose different account
6. connect to server
Everything here is fine. You are on the server twice with two different accounts.
7. Disconnect with first account
8. Attempt to Reconnect
9. Client responds with Bad Login.
You have to log out on the launcher with that account and log back in to reconnect.
This isn't a new issue, and the new launcher makes it easier to deal with, before you had to close the launcher but this has been going on for the last two versions.
Linked issues
is duplicated by 1
Comments 9
Same here, It really bugs me that I purchased two accounts just to run my server online, and now I have to run it offline. Essentially I've wasted 25 dollars on something I can't even use now.
Chris: Update the affected versions when they come out, otherwise they may ignore the ticket.
I've been getting this for a while and finally decided to search for it. You don't even need multiple accounts for this to happen. A common workflow for me personally is that I make something on singleplayer creative and then copy my build in multiplayer survival onto a server (one Minecraft running full screen on each of my dual monitors).
If I log in and open a 1.7.2 singleplayer world and then open a second launcher with a 1.6.4 for multiplayer, the multiplayer one has the Bad Login error. As a workaround, I must connect to the 1.6.4 server FIRST and then open the second launcher for singleplayer and then everything works fine. Very annoying!
This really need to be addressed. I'm forced by Mojang to run an offline server simply because I can't even run two accounts at one time. This is a dumb reason to have to run offline true.
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Every time you open the launcher it invalidates the previous session. This is a nonoptional security feature and design choice.
okay at least now we know. could you make it configurable so devs can actually test things on online servers with multiple accounts?
This is not fixed. Or it returned. I am running on 1.2.1 and this exact bug is happening. And it is not related to MCL 602, let alone duplicated. 602 is about switching profiles (maybe offline<->online)
I am using two online mode accounts, they act as stated in this issue, the first one is getting logged out.
Edit: Oh, I didn't know I actually CAN update / add the affected version number(s)