When the minecraft authority servers (I guess, might be other servers) are having problems, people are unable to connect to 1.6.4 multiplayer servers. See https://mojang.atlassian.net/browse/MC-40683 .
Expected behaviour: Client should report that mojang's server XYZ is timing out, overloaded, or similar. User expects more accurate error messages to avoid them wasting time reinstalling, or changing passwords, restarting routers, disabling firewalls, when none of those actions will resolve the problem.
Actual behaviour: Client reports Bad Login
Attachments
Comments 9
Screenshots showing misleading error message from minecraft when running with 1.6.4 profile attempting to connect to 1.6.4 servers. First two screenshots show twitter reports showing problems affecting people worldwide.
What is that meant to mean?
Is minecraft 1.6.4 not being supported any longer?
Please see attached screenshot showing the problem is affecting many people today.
As stated in MC-40683 please wait patiently until Mojang fixes legacy sessions.
Howevery there won't be any changes to 1.6.4 clients as those are outdated.
I'm confused how you can mark this problem as Resolved, yet tell us to "... wait patiently until Mojang fixes legacy sessions." Your comment contradicts the status of the bug.
Just because it's legacy doesn't mean it shouldn't be tracked... right?
<sigh>
If you just kept one of these many bug reports open until it’s actually resolved then maybe people would stop creating them. This kind of behaviour doesn’t make Mojang popular. I would love to move on to 1.7.2, but unfortunately that requires (thanks to Mojang’s terrain fiddling) opening our 1.6.2 world in 1.6.4...which we can’t do since no one can login. And yes, I know there are workarounds, but what about all those people running CraftBukkit who don’t have access to 1.7.2 yet?
Epic fail just made worse by ‘resolving’ all these bugs. Unintentional, I’m sure, but it just makes people feel utterly alienated. Not good PR.
More reports from around the world, yet MojangSupport still unaware that the fix they point to does not work: https://twitter.com/search?q=mojangsupport&src=typd
Please tell us HOW to report this to the right place.
It's called "legacy" for a reason.