MCL-6151"id": "1.5.2" altered to "id": "legacy" in versions 1.5.2 and prior [i.e., can't start Minecraft versions older than 1.6]
I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here: MCL-5837
The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:
1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beginning of the .json file needs to match the versions' name as well.
The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.
Environment
Windows 7, Java 8.0.1210.13
Linked Issues
is duplicated by2
MC-115685
Created Issue:
"id": "1.5.2" altered to "id": "legacy" In Versions 1.5.2 And Prior
I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here: https://bugs.mojang.com/browse/MCL-5837
The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beggining of the .json file needs to match the versions' name as well.The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.Environment
Windows 7, Java 8.0.1210.13
I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here: https://bugs.mojang.com/browse/MCL-5837
The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beggining of the .json file needs to match the versions' name as well.The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here:
MCL-5837The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beggining of the .json file needs to match the versions' name as well.The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here:
MCL-5837The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beggining of the .json file needs to match the versions' name as well.The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.I was asked by Kumasasa on my previous ticket to create a separate one on this issue, since they are considered separate problems. The previous one can be found here:
MCL-5837The day the new launcher was released a change took place in the 1.5.2 (and older versions) .json file from "id": "1.5.2" to "id": "legacy", of course that's not the only difference, but it is the first and most notable change, and it must have something to do with the problems people are getting when installing modded versions of the game on those versions.
Now, of course mods are not officially supported, but the problem here is with the new launcher and the changes it brought (the old launcher did not have these problems).
When creating a new profile for a modded version, of course, the first step is to create a copy of the version needed to install the mod in the .minecraft/versions file. After that it is required to make the following changes:1. The user has to change the version (in my case 1.5.2) name to something else, as well as the .jar and .json
2. After that, the "id": "(version)" right at the beginning of the .json file needs to match the versions' name as well.The problem here lies in the fact that some sort of change was made that screwed up this process, One of the changes being the alteration of the "id": "1.5.2" into "id": "legacy" in the new launchers' version of the .json file.
This can't be ignored as a non-Launcher issue, because as soon as the update took place, 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.
"id": "1.5.2" altered to "id": "legacy"InVersions 1.5.2AndPrior"id": "1.5.2" altered to "id": "legacy" in versions 1.5.2 and prior [i.e., can't start Minecraft versions older than 1.6]
is duplicated by
is duplicated by
Duplicate of MCL-6151. Please go and upvote that ticket instead.
So something that I've observed is the fact that when you attempt to mod an older version, then launch it? The game log actually claims that it has some sort of invalid hash, deletes the modded .jar file, then downloads an unmodded one and names it after the deleted modded one, so it appears that I can't mod the .jar file at all. I was only trying to install optifine to version 1.2.5.
I will be closing this bug as it's fairly old and the launcher has had numerous changes since this was reported. If you feel that this is still considered a bug, feel free to create a new bug.
While we should aim to simplify modding Minecraft, we reserve the right to change internal states and files for our own use. Any modifications would have to follow along with these changes, as they are in fact, modifications of the original.