Goncalo Virginia
- ParagoN
- paragon
- Europe/Stockholm
- Yes
- No
MCL-5837![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
A couple of days ago the launcher auto-updated to the new 2.0 version, and I tried to install a mod (Better Than Wolves) which I have done countless times. So I renamed the version, .jar and .json to the same name, and edited the "id" inside the .json file to match the name as well.
Usually, it would show "1.5.2" after the "id" at the beggining, but after installing the new launcher and 1.5.2, it says"legacy" on the id (I presume this is part of the problem with the new launcher). I changed it anyway and perfectly installed the mod like I should... and it simply would't show up in the versions list in the launcher, whereas with the previous launcher, it would work fine.I tried uninstalling and installing minecraft countless times, and yesterday (9th of February), if I tried to even select the 1.5.2 version from the version list and tried to install/play, it would instantly crash the game and wouldn't even start up.
Steps to Reproduce:
1. Create a new profile with the 1.5.2 version.
2. Launch it.
3. Watch it not even start up and crash.A couple of days ago the launcher auto-updated to the new 2.0 version, and I tried to install a mod (Better Than Wolves) which I have done countless times. So I renamed the version, .jar and .json to the same name, and edited the "id" inside the .json file to match the name as well.
Usually, it would show "1.5.2" after the "id" at the beggining, but after installing the new launcher and 1.5.2, it said "legacy" on the id (I presume this is part of the problem with the new launcher). I changed it anyway and perfectly installed the mod like I should... and it simply would't show up in the versions list in the launcher, whereas with the previous launcher, it would work fine.I tried uninstalling and installing minecraft countless times, and yesterday (9th of February), if I tried to even select the 1.5.2 version from the version list and tried to install/play, it would instantly crash the game and wouldn't even start up.
Steps to Reproduce:
1. Create a new profile with the 1.5.2 version.
2. Launch it.
3. Watch it not even start up and crash.I honestly dislike the new launcher style and functionality, I understand a lot of work has been put into this, but I believe a lot of people prefered the "old" 1.6 launcher 10x.
Version 1.5.2 Not AccessibleAnymore(Unable to start up)Versions 1.5.2 And Prior Not Accessible (Unable to start up)
Goncalo Virginia, please create a separate ticket about that "id:" thing (leave a reference to this ticket)
It is your job to deal with these kinds of problems, since the launcher can't literally launch versions prior to 1.5.2, so this is technically considered a launcher bug. The previous launcher worked perfectly with any older version, even back to Alpha, so there is no reason for it not to work with the new launcher (it's basically one of its' main features).
If this is really to be considered a new and improved launcher, then it should be able to do everything the previous one did, and nothing less.
This is not an issue related to an old version, this is an issue with a new launcher unable to startup the older versions, and it should be addressed immediately. Everything worked fine before and it just had to be screwed up.
I'm sure there's a simple fix to this problem, and it has something to do with the "id": "legacy" on the .json of older versions with the new launcher.
The launcher is unable to launch 1.5.2 anymore in order to show it crash (I wish I had saved a crash log from some days ago), so it doesn't create a crash log in my .minecraft of what happened. When I attempt to launch it, it just says "An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience."
So the only information I can show is with the Output Log when I try to start it up. Everything is ok until this happens in the Output Log:
13:56:10 launcher Version does not support log configuration, will assume one plaintext entry per line
13:56:10 game fev 12, 2017 1:56:10 PM net.minecraft.launchwrapper.LogWrapper log
13:56:10 game INFO: Using tweak class name net.minecraft.launchwrapper.VanillaTweaker
13:56:11 game fev 12, 2017 1:56:11 PM net.minecraft.launchwrapper.LogWrapper log
13:56:11 game INFO: Launching wrapped minecraft
13:56:12 launcher Process closed with exit code -1073740791
This just shows how bad it is at the moment.. it's unable to even launch the game and crash xD
Ok, now it's able to launch thanks to the nvidia driver fix. But it now crashes just like before I had installed the nvidia update. Here is the crash report (It says its probably modded, to which I guarantee it is not):
https://bugs.mojang.com/secure/attachment/133906/crash-2017-02-12_14.49.32-client.txt
Oh I forgot to mention that the crash happened on 1.5.2 and older versions, the latest one works just fine.
That's what I've tried countless times already, here is the new crash report:
https://bugs.mojang.com/secure/attachment/133918/crash-2017-02-12_16.39.46-client.txt
I'm really curious why the "id": on the .json file of every version before 1.5.2 (including 1.5.2) has been changed to "legacy" with this new launcher update. It's really nerve wracking because it's precisely the 1.5.2 version that I want to use. There needs to be a simple fix in order to play the older versions, it can't be that complicated.
Yes, the old launcher worked perfectly with every version available, including 1.5.2.
I always use the standard language: English (US).
Yes, there is an entry called lang:en_us in my options.txt, should I attempt to change it to en_US and launch 1.5.2 that way?
That simple entry actually enabled the game to launch now, but that still doesn't explain the change in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", since that must have something to do with modded versions not showing up anymore.
And you can't say that it's not a Launcher issue, because as soon as I updated to the new one, the change I described earlier happened, and no modded versions would show up in the new Launcher's versions list, even though they've worked for years with the previous launcher.
I'm well aware the problem isn't just (probably) with the .json file, but this change needs to be addressed since things worked perfectly before, and I've seen other people unable to use modded versions of 1.5.2 with the new launcher.
Everyone has heard this one before, but "If it isn't broken, don't fix it", referring to the old launcher of course.
I would like to know the reason behind the change in the 1.5.2 (and older) .json files, which changed the "id": "1.5.2" into "id": "legacy".
After the new launcher and that changed, modded versions of 1.5.2 stopped being able to show up on the versions list (in the launcher), which is a huge issue.
I understand that older versions are no longer supported, but that's not the problem in hand, since before this new launcher, modded versions would work fine and show up when creating a new profile. If that issue can be solved, then this launcher would definitely be an upgrade, but now it's just useless for people that want to play older modded versions.