Chaoschaot234

@Chandler - It is a bug as I never close my client. I only idle in the main menu and also your comment is not even telling me why you are stating that it is not a bug means that you must provide additional explenation why YOU are thinking that THIS is not a bug, thanks.

@Dhranios - And here is the law breaking thing: Mojang and/or MS has no right to limit me in the usage of only ONE client! If my PC can handle 100 Clients I am allowed to play online with my MC Account on all these 100 clients without beeing forced to re-authenticate every time.

It is my right since I purchcased MC to play it which does not exclude the usage of one account and multiple MC Instances running parralel, they are included with the purchcase I did in the past. And due to new EU Law for selling digital content Mojang/MS is not allowed to set limits here.

This means that this Bug is not even resolved and was never fully investigated. I refuse to close this as long as there is no fully, detailed review about that bug. And since I am the also called reporter I strictly prohibit any markings as resolved or similar without that what I have requested, otherwise it will show that either MS nor Mojang cares about there players

Oh, you overreaded also that I mentioned that the Timeout also occours with other launchers. I am not so stupied to forgett to test it with the original ones, like stated in the comments.

This is for you the indication that either modded/vanilla MC nor the used launcher causes this problem even if Third-party launchers not supported here but since it is reproduceable
with the original ones, which is indeed supported here, all should be fine. Sorry if my compare between the original and 3rd party ones irritated you, that wasn't my intension.

@violine1101

Ah yes, I restart the game every time this ERROR occours ... also it has happened not only with your client and a vanilla server, it also happens with the use of
MultiMC (which is much better as your client), FTB/ATLauncher and also with the Curse Launcher and it does not matter if the game is modded or even still vanilla.

Losing more than three times a day the session isn't funny and is at last a bug and will be ever a bug as long as you not going to look after it. Because such many
Sessiontimeouts can't be existing since this is a game and not an online banking portal and no, my Internet connection is stable, not jamed (spelled correctly?) or otherwise
disrupted which results again in the fact tha your session servers are worse and bugy. Not to forgett to mention that no playing a paid game is possible in multiplayer as long as
the sessions server responding with an 500 HTTP Error, which is also a bug, becaus it is stupied to block it only while smth. isn't working?

I know that it is possible to renew the session without restarting the game but you are to lazy to implement it because: "Why should we do this even if we can do it. Should the player
deal with it an restart the game and if he has mods installed, blame the authors for it and laugh while the player must restart the client with a dozen mods."

Sorry but this is definitly not high quallity support but collecting the money from the player ... rly nice Mojang, rly nice.

However, I'll respond or even reopen every time I get a session timeout a bug ticket as long as this isn't resolved since you are exactly know how to resolve it.

Cheers

@Neko

This is not only a suggestion, it is the only solution to this bug because if I have the client still open in the menu my seesion will become still invalide
without using another client on the same account.

Means in fact that this is a bug because why should a session timeout? Only if someone trashes all registered sessions.

Summery: It is still a bug, pls take a look into it.

Hello fienxjox,

thanks for your replay including the link to the correct bugtracker 🙂.