In order to manually install mods you have to first make a copy of the version that you are modding; e.g. the 1.4.7 folder in the .minecraft\versions folder, then you have to rename the folder and files inside to e.g. 1.4.7-forge, then open the json file in a text editor and search for "client.jar" (without quotes) and delete the entire "downloads" (in quotes) section that encloses it, then edit the following line, which will be "id": "1.4.7" so "1.4.7" matches the name you used before (e.g. "id": "1.4.7-forge").
Here is an example, (using my own mod for 1.6.4 but the same applies to any version):
Before editing the json (note that the json has everything on one line):
After editing (anything not shown here should not be changed):
"assets": "legacy",
"id": "TMCWv4",
Also, it is very highly recommended, if not practically essential, to make a custom profile/installation with its own game directory as otherwise the game will likely crash if you previously ran a newer version in the same directory (see MCL-5837 and MC-38527), or worse, you can accidentally open a world in the wrong version, ruining it:
Note: versions prior to 1.6 do not properly support custom directories so you will need to run 1.4.7 in the default directory and run newer versions in their own directories:
In order to manually install mods you have to first make a copy of the version that you are modding; e.g. the 1.4.7 folder in the .minecraft\versions folder, then you have to rename the folder and files inside to e.g. 1.4.7-forge, then open the json file in a text editor and search for "client.jar" (without quotes) and delete the entire "downloads" (in quotes) section that encloses it, then edit the following line, which will be "id": "1.4.7" so "1.4.7" matches the name you used before (e.g. "id": "1.4.7-forge").
Here is an example, (using my own mod for 1.6.4 but the same applies to any version):
Before editing the json (note that the json has everything on one line):
After editing (anything not shown here should not be changed):
Also, it is very highly recommended, if not practically essential, to make a custom profile/installation with its own game directory as otherwise the game will likely crash if you previously ran a newer version in the same directory (see MCL-5837 and MC-38527), or worse, you can accidentally open a world in the wrong version, ruining it:
Note: versions prior to 1.6 do not properly support custom directories so you will need to run 1.4.7 in the default directory and run newer versions in their own directories:
Hello there. I've tried to do the same steps that you said, but looks like minecraft dont want us to play older version anymore x.x
In my case, i want to play the 1.4.2 version with some old mods. Here is the part of json file that says download:
You definitely can still play older versions; I've ever had any issues whatsoever playing 1.6.4 with my own mods installed in the manner described; even when they changed the json format to add in the downloads stuff older jsons continued to work.
As for editing the json , you want to completely remove the entire "downloads" section that refers to "client.jar" - just select the lines and press delete, as I showed in my previous example. Here are the exact lines that you want to remove:
It should now look like this (based on what you posted, which suggests that the json format for 1.4.2 is not the same as 1.6.4 or newer versions, where the "downloads" section comes between "assets" and "id":):
Don't forget to change the "id": line (NOT the id for assets, which sounds suspicious since it should be "legacy", not "pre-1.6", and what you posted can't be the entire json file, which is around 10KB for 1.6.4 and includes a bunch of libraries that the game needs to run) and rename the files as otherwise the launcher will still redownload a clean copy (this has been the case since the 1.6 launcher).
Also, if you are having issues launching 1.4.7, namely crashes, you need to run older versions in a separate game directory, which can easily be set by editing the installation (the importance of this cannot be understated; if you open a world in the wrong version it will be corrupted, or you'll be unable to downgrade):
If the player wants to change the .minecraft file path, they can turn on the "Game directory" option. Now, navigate to the folder where the player wishes to relocate the .minecraft folder. The player can also open the Minecraft profile by clicking the green arrow-shaped "Go to folder" button.
Alternatively, use a third-party launcher like MultiMC, which were designed for running modded versions; you don't even need to modify the jar or edit any files, just select the mods from a list and they will automatically be loaded when you launch the game, much like how Forge itself loads mods from a "mods" folder. They can also replicate the "classic" (pre-1.6) .minecraft folder structure (some mods, such as ModLoader, do not work with the current structure; there is a patch available but I don't know if it still works. All of these issues are simply because Mojang does not support mods and do not make any attempts to ensure they keep working, and most modders don't bother updating mods for old versions to fix them - most game developers don't even let you play older versions at all).
When I replace the files 1.4.7.jar on files from the forge archive, it still runs vanilla. I don't understand how to install forge on older versions
P.S. Maybe bad eng
trying textures eeeeeeeehhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
In order to manually install mods you have to first make a copy of the version that you are modding; e.g. the 1.4.7 folder in the .minecraft\versions folder, then you have to rename the folder and files inside to e.g. 1.4.7-forge, then open the json file in a text editor and search for "client.jar" (without quotes) and delete the entire "downloads" (in quotes) section that encloses it, then edit the following line, which will be "id": "1.4.7" so "1.4.7" matches the name you used before (e.g. "id": "1.4.7-forge").
Here is an example, (using my own mod for 1.6.4 but the same applies to any version):
Before editing the json (note that the json has everything on one line):
After editing (anything not shown here should not be changed):
Also, it is very highly recommended, if not practically essential, to make a custom profile/installation with its own game directory as otherwise the game will likely crash if you previously ran a newer version in the same directory (see MCL-5837 and MC-38527), or worse, you can accidentally open a world in the wrong version, ruining it:
https://minecraft.gamepedia.com/Java_Edition_launcher#Installations
Note: versions prior to 1.6 do not properly support custom directories so you will need to run 1.4.7 in the default directory and run newer versions in their own directories:
MCL-1394 Custom Directory not used when using old game versions
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Hello there. I've tried to do the same steps that you said, but looks like minecraft dont want us to play older version anymore x.x
In my case, i want to play the 1.4.2 version with some old mods. Here is the part of json file that says download:
"mainClass": "net.minecraft.launchwrapper.Launch",
"minimumLauncherVersion": 4,
"assets": "pre-1.6",
"downloads": {
"client": {
"url": "https://launcher.mojang.com/v1/objects/42d6744cfbbd2958f9e6688dd6e78d86d658d0d4/client.jar",
"sha1": "42d6744cfbbd2958f9e6688dd6e78d86d658d0d4",
"size": 4928385
},
"server": {
"url": "https://launcher.mojang.com/v1/objects/5be700523a729bb78ef99206fb480a63dcd09825/server.jar",
"sha1": "5be700523a729bb78ef99206fb480a63dcd09825",
"size": 2018455
},
"windows_server": {
"url": "https://launcher.mojang.com/v1/objects/5c94ac0043dc21bc71b8e1fa3fbac62139c820fe/windows_server.exe",
"sha1": "5c94ac0043dc21bc71b8e1fa3fbac62139c820fe",
"size": 2199703
}
},
"assetIndex": {
"totalSize": 49381897,
"id": "pre-1.6",
"known": true,
"url": "https://launchermeta.mojang.com/v1/packages/4759bad2824e419da9db32861fcdc3a274336532/pre-1.6.json",
"sha1": "4759bad2824e419da9db32861fcdc3a274336532",
"size": 73813
}
}
Where is the parts that i should change in order to make this work?
You definitely can still play older versions; I've ever had any issues whatsoever playing 1.6.4 with my own mods installed in the manner described; even when they changed the json format to add in the downloads stuff older jsons continued to work.
As for editing the json , you want to completely remove the entire "downloads" section that refers to "client.jar" - just select the lines and press delete, as I showed in my previous example. Here are the exact lines that you want to remove:
It should now look like this (based on what you posted, which suggests that the json format for 1.4.2 is not the same as 1.6.4 or newer versions, where the "downloads" section comes between "assets" and "id":):
Don't forget to change the "id": line (NOT the id for assets, which sounds suspicious since it should be "legacy", not "pre-1.6", and what you posted can't be the entire json file, which is around 10KB for 1.6.4 and includes a bunch of libraries that the game needs to run) and rename the files as otherwise the launcher will still redownload a clean copy (this has been the case since the 1.6 launcher).
Also, if you are having issues launching 1.4.7, namely crashes, you need to run older versions in a separate game directory, which can easily be set by editing the installation (the importance of this cannot be understated; if you open a world in the wrong version it will be corrupted, or you'll be unable to downgrade):
Alternatively, use a third-party launcher like MultiMC, which were designed for running modded versions; you don't even need to modify the jar or edit any files, just select the mods from a list and they will automatically be loaded when you launch the game, much like how Forge itself loads mods from a "mods" folder. They can also replicate the "classic" (pre-1.6) .minecraft folder structure (some mods, such as ModLoader, do not work with the current structure; there is a patch available but I don't know if it still works. All of these issues are simply because Mojang does not support mods and do not make any attempts to ensure they keep working, and most modders don't bother updating mods for old versions to fix them - most game developers don't even let you play older versions at all).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Thanks! I'll try do that and then post the results asap