We really need to know if this is going to happen, and if it is, when. There are loads of developers and server owners who need to plan around this. The lack of communication is appalling.
@Ned Loynd It's definitely being worked on. I don't see why they would say "no ETA" if they were planning on just closing this issue without fixing it.
Are we all talking about the same issue here? Like I said in my previous comment, login.minecraft.net doesn't work at all. That's the problem. Maybe session.minecraft.net doesn't work all the time, but that isn't the subject of this issue.
The issue is that beta servers have to use third party plugins/software to authenticate players. We can't run our servers in online mode, because login.minecraft.net is down. That's why this post was made.
Hey Pokechu, while you're here I have a question; Is the web team bogged down with other issues, or is there something about this issue that makes it complicated to fix? I'm just wondering what's going on, because its been a while since we got an update.
That wouldn't solve the issue. That would require the user to enter information into chat before being able to play. If we wanted that, we would just continue using AuthMe. We want real, seamless authentication. The only way that can be achieved is by bringing the old authentication servers back online, or making a new one that follows the same specification. That is what we want.
Making a new authentication server following the old specification would be way easier. You could do it in an hour with a couple PHP scripts, and it wouldn't require any chat commands or tabbing out of the game.
And as a server owner who is very invested in this issue, I would much prefer that outcome. I know I can also speak on behalf of OP in that regard.
Several working solutions have been created & posted here. What could possibly be holding this up? There isn't even a point in writing this comment. I might as well be talking to a brick wall.
In light of the recent announcement about forcing paying customers to migrate their account against their will, I feel someone should ask; How does it affect this issue? I imagine it would be quite difficult to retro-fit old versions for Microsoft account support, so where does that leave communities like ours?
Unwise decision, Mojang. Very unwise. Seems to be a trend recently. We are getting sick of being treated like we don't matter, and I am seriously considering moving my community away from official account support if this attitude doesn't change. We don't require your consent to continue existing, so for your sake I hope this decision is reconsidered.
Legacy auth, Mojang auth, and Microsoft auth work in dramatically different ways, but rather than debating that point here and flooding inboxes in the process, I'm just going to wait for a Mojang employee to respond to my question. I highly doubt either of you have more info than I do considering the announcement was made only 2 days ago.
Exactly. People seem to misunderstand what the migration really is, and it's just changing what you use to authenticate yourself.
Have you not considered that some people would like a choice? Some of us would actually prefer to keep our Mojang accounts. I know that might be a little bit hard to comprehend, but it's true. Some of us, believe it or not, would rather not have to create a Microsoft account or agree to their ToS just to continue playing a block game we bought a decade ago.
This is exactly what I expected. I have no doubt the engineers at Mojang are fully capable of solving this problem with minimal effort, yet for some reason it still hasn't been deemed worthy of fixing. They have repeatedly let my players down, and I see no reason why my server should support Mojang/Microsoft moving forward.
I don't mean to be rude, Codie. But we've already tried everything to get them to fix this issue, including offering to fix it ourselves. It's been over 3 years, and I can all but guarantee it will be at least another 3 before something actually meaningful happens. As disappointing as it is, I think the community ought to focus on building out our cracked infrastructure as best we can to mitigate the problems caused by this issue. It's really the better alternative, because then at least we don't have to rely on unreliable developers. "If you want something done right, do it yourself" as the saying goes.
Deleting this page & doing it ourselves would make everything so much better, that's my only point. You don't have to reiterate info people already know, Codie. Edit: You aren't the first to make such offers about fixing the problem, and you won't be the last. Mojang doesn't care, and the sooner we move on from it the better. We have alternative solutions that I think are preferable in light of forced migration.
We really need to know if this is going to happen, and if it is, when. There are loads of developers and server owners who need to plan around this. The lack of communication is appalling.
@Ned Loynd It's definitely being worked on. I don't see why they would say "no ETA" if they were planning on just closing this issue without fixing it.
The DNS record for login.minecraft.net doesn’t even exist, so it couldn’t possibly work.
Are we all talking about the same issue here? Like I said in my previous comment, login.minecraft.net doesn't work at all. That's the problem. Maybe session.minecraft.net doesn't work all the time, but that isn't the subject of this issue.
I'm friends with the OP, and have discussed this issue with them at length. The authentication servers in question have been offline for years.
The issue is that beta servers have to use third party plugins/software to authenticate players. We can't run our servers in online mode, because login.minecraft.net is down. That's why this post was made.
Hey Pokechu, while you're here I have a question; Is the web team bogged down with other issues, or is there something about this issue that makes it complicated to fix? I'm just wondering what's going on, because its been a while since we got an update.
Well it was worth asking. Thank you, and have a good rest of your day.
@mrbengtsson
That wouldn't solve the issue. That would require the user to enter information into chat before being able to play. If we wanted that, we would just continue using AuthMe. We want real, seamless authentication. The only way that can be achieved is by bringing the old authentication servers back online, or making a new one that follows the same specification. That is what we want.
Making a new authentication server following the old specification would be way easier. You could do it in an hour with a couple PHP scripts, and it wouldn't require any chat commands or tabbing out of the game.
And as a server owner who is very invested in this issue, I would much prefer that outcome. I know I can also speak on behalf of OP in that regard.
Several working solutions have been created & posted here. What could possibly be holding this up? There isn't even a point in writing this comment. I might as well be talking to a brick wall.
In light of the recent announcement about forcing paying customers to migrate their account against their will, I feel someone should ask; How does it affect this issue? I imagine it would be quite difficult to retro-fit old versions for Microsoft account support, so where does that leave communities like ours?
Unwise decision, Mojang. Very unwise. Seems to be a trend recently. We are getting sick of being treated like we don't matter, and I am seriously considering moving my community away from official account support if this attitude doesn't change. We don't require your consent to continue existing, so for your sake I hope this decision is reconsidered.
Alright, and how did you come to that conclusion?
Legacy auth, Mojang auth, and Microsoft auth work in dramatically different ways, but rather than debating that point here and flooding inboxes in the process, I'm just going to wait for a Mojang employee to respond to my question. I highly doubt either of you have more info than I do considering the announcement was made only 2 days ago.
Exactly. People seem to misunderstand what the migration really is, and it's just changing what you use to authenticate yourself.
Have you not considered that some people would like a choice? Some of us would actually prefer to keep our Mojang accounts. I know that might be a little bit hard to comprehend, but it's true. Some of us, believe it or not, would rather not have to create a Microsoft account or agree to their ToS just to continue playing a block game we bought a decade ago.
This is exactly what I expected. I have no doubt the engineers at Mojang are fully capable of solving this problem with minimal effort, yet for some reason it still hasn't been deemed worthy of fixing. They have repeatedly let my players down, and I see no reason why my server should support Mojang/Microsoft moving forward.
Another "work planned", I see. I'll just go ahead and expect the same when summer rolls around.
I'll celebrate when it happens. IF it happens.
If they don't fix it soon I might be inclined to start rapid-firing links about the Gates Foundation.
I don't mean to be rude, Codie. But we've already tried everything to get them to fix this issue, including offering to fix it ourselves. It's been over 3 years, and I can all but guarantee it will be at least another 3 before something actually meaningful happens. As disappointing as it is, I think the community ought to focus on building out our cracked infrastructure as best we can to mitigate the problems caused by this issue. It's really the better alternative, because then at least we don't have to rely on unreliable developers. "If you want something done right, do it yourself" as the saying goes.
Deleting this page & doing it ourselves would make everything so much better, that's my only point. You don't have to reiterate info people already know, Codie. Edit: You aren't the first to make such offers about fixing the problem, and you won't be the last. Mojang doesn't care, and the sooner we move on from it the better. We have alternative solutions that I think are preferable in light of forced migration.