Contrary to your public twitter post and what you may believe you have NOT fixed the launcher issues. We are still unable to launch the game with mods from the curse client with this sorry excuse for a new launcher you have forced on us. If you can't bug test something before release then you have no business releasing an update, especially one such as this that you are forcing on users and not even giving us an option of opting out of until it is working properly. You NEED to get this fixed immediatly or allow us to revert back to the last version of the old launcher which I believe was 1.67 or something like that. The progress bar is forever stuck on "Preparing" this IS a minecraft/mojang/microsoft issue and NOT an issue with my computer.
Linked issues
Comments 12
The fact of you helping with mods or not is irrelevant! There should never have been a game breaking release of a new forced launcher and it's as simple as that. This is a fault of minecraft/mojang or microsoft not anyone else. Leaving well enough alone is all that was necessary however these so called improvements had to be made for no foreseeable benefit other than to break customers games.
Then care to explain how exactly to go about getting the old launcher back for my fiances computer that we play modded minecraft on via the curse client? I tried for about 3 hours today before even making this post and another hour or two after that and was still unable to find a way to roll back to one that actually worked.
Oh and btw this is NOT resolved as the status you changed it to states.....If it were indeed resolved we would be able to play minecraft and I wouldn't be sitting here on this bug report forum.
So if as Mustek said it's possible to get the old launcher back then how do I do it? And again...modding is irrelevant so you can drop that part of your argument and simply tell me how to get the old launcher back as I....a paying customer have requested.
1) You posted this in the Minecraft bugtracker, not in the launcher one. (https://bugs.mojang.com/browse/MCL)
2) A lot of us are volunteers so please lower your tone
3) https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.exe
I'm just going to step in to make some observations. First Mojang has no reason to support 3rd parties but they are graceful enough to do so, this however does not mean the support for this is official in any way. This bug tracker and the issues in it are for issues regarding the official game. Any issues regarding 3rd party interactions with the game or parts of the game (including the launcher) are out of scope for this bug tracker. Mojang has no responsibility to test issues against 3rd party applications before releases.
This is duplicating MCL-5312
Well Urielsalis it is a bug with the game therefore posted here. As for the "tone" if I would have gotten a fix to the problem then all would be just fine but seeing as I got the general run around and the shifting of blame to anything other than minecraft/mojang that's where the tone/attitude comes from. Brought it on yourselves.
Lutzee, Mojang has every reason to make sure their updates don't break mod support entirely as they are the ones who chose to allow mods in the first place therefore they are in fact "supporting" mods and the modding community. The "official" game supports mods therefore it's the responsibility of this site to assist with issues that arise due to a problem with the base game and it's functioning and this is one such problem.
Finally, Kumasasa Thank You for finally being the one to help fix the problem/point me in the direction of the fix. It's nice when someone who knows gets a moment and actually can help resolve a situation instead of buck passing and blame game.
Now I'm finally off to play minecraft...
We dont help with mods here, curse are working for a fix that is going to land in their Alpha soon