im trying to download the evil minecraft mod for 1.2.5, but every time i try to load it, the files in the .jar get replaced! how do i stop this from happening so i can play some nostalgia?
The reason I suggested another launcher is that the Mojang launcher now has a repair ability. If you change/delete/modify a file in the launcher, it will repair itself when opened. I do believe that older versions of MC (like 1.2.5) required modification of MC files to play modded. I think this is what your experiencing.
Rollback Post to RevisionRollBack
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
You can easily bypass the "repair ability" of Mojang's launcher; I have been playing with mods for 4+ years with no issues at all.
First, make a copy of the 1.2.5 versions folder
Second, rename it to something like 1.2.5-modname, as well as the jar and json file inside
Third, open the json file and search for "id":"1.2.5" and replace "1.2.5" with the name you used in step 2
Fourth, search the json for "downloads" and delete the section which contains the URL for "client.jar" (a bunch of random numbers and letters before this), making sure that you only delete the contents between (and including) the opening and closing brackets; {}
You should now be able to modify the jar without the launcher overwriting it; the launcher will complain that it can't download the modded jar but it shouldn't stop it from launching as it uses the local copy:
I even provide a pre-modified json with my mod so you can just drop it in after renaming the folder/files as before without having to edit it (this part is the biggest point of failure as it is easy to edit/delete the wrong lines (there is another "id" section that identifies the assets used) or miss a bracket); of course, an automated installer (e.g. Optifine/Forge, though I believe only since 1.6) is ideal (Optifine 1.6.4 has one but I just extract the jar and add the files directly as I believe it only works on vanilla jars and I have other mods installed).
You can easily bypass the "repair ability" of Mojang's launcher; I have been playing with mods for 4+ years with no issues at all.
First, make a copy of the 1.2.5 versions folder
Second, rename it to something like 1.2.5-modname, as well as the jar and json file inside
Third, open the json file and search for "id":"1.2.5" and replace "1.2.5" with the name you used in step 2
Fourth, search the json for "downloads" and delete the section which contains the URL for "client.jar" (a bunch of random numbers and letters before this), making sure that you only delete the contents between (and including) the opening and closing brackets; {}
You should now be able to modify the jar without the launcher overwriting it; the launcher will complain that it can't download the modded jar but it shouldn't stop it from launching as it uses the local copy:
I even provide a pre-modified json with my mod so you can just drop it in after renaming the folder/files as before without having to edit it (this part is the biggest point of failure as it is easy to edit/delete the wrong lines (there is another "id" section that identifies the assets used) or miss a bracket); of course, an automated installer (e.g. Optifine/Forge, though I believe only since 1.6) is ideal (Optifine 1.6.4 has one but I just extract the jar and add the files directly as I believe it only works on vanilla jars and I have other mods installed).
not sure if this is a glitch, but there are multiple downloads
""name": "net.java.jinput:jinput:2.0.5",
"downloads": {
"artifact": {
"size": 208338,
"sha1": "39c7796b469a600f72380316f6b1f11db6c2c7c4",
"path": "net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar",
"url": "https://libraries.minecraft.net/net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar"
}
}
},
{
"name": "net.java.jutils:jutils:1.0.0",
"downloads": {
"artifact": {
"size": 7508,
"sha1": "e12fe1fda814bd348c1579329c86943d2cd3c6a6",
"path": "net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar",
"url": "https://libraries.minecraft.net/net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar""
theres more than 2, this is just an example
not sure if this is a glitch, but there are multiple downloads
""name": "net.java.jinput:jinput:2.0.5",
"downloads": {
"artifact": {
"size": 208338,
"sha1": "39c7796b469a600f72380316f6b1f11db6c2c7c4",
"path": "net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar",
"url": "https://libraries.minecraft.net/net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar"
}
}
},
{
"name": "net.java.jutils:jutils:1.0.0",
"downloads": {
"artifact": {
"size": 7508,
"sha1": "e12fe1fda814bd348c1579329c86943d2cd3c6a6",
"path": "net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar",
"url": "https://libraries.minecraft.net/net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar""
theres more than 2, this is just an example
The only one you want to remove is the one that refers to "client.jar", which is the name of the Minecraft jar on Mojang's servers; for example, for 1.6.4 it is this; I believe that all versions use "client.jar":
This also includes the server download, which can probably be left in but there is no point in leaving it in for a modded version; I just removed everything seen here. The downloads for other files are not really needed either but unless you are modifying them for some reason they can be left in (e.g. making the game use a different version of LWJGL to fix issues on certain systems).
This confusion is also a perfect example of why I provide a pre-modified json with my mod, as this is likely the main reason why this method of modding fails (I've had people tell me before that they tried to install one of my mods and the version did not show up or had an error on launch, which were very likely caused by a malformed json file).
You'd also think that somebody would have made a generic installer for jar mods by now; essentially, something where you add your mod's files to a folder within the installer jar, along with a file that sets the name of the profile and such and you just run it like any other jar file to install it (I suppose that nobody ever made one because jar mods for current versions are not very common these days; most of the ones that are still being updated, like Optifine, have their own installers, and few modders support older versions of their mods).
The only one you want to remove is the one that refers to "client.jar", which is the name of the Minecraft jar on Mojang's servers; for example, for 1.6.4 it is this; I believe that all versions use "client.jar":
This also includes the server download, which can probably be left in but there is no point in leaving it in for a modded version; I just removed everything seen here. The downloads for other files are not really needed either but unless you are modifying them for some reason they can be left in (e.g. making the game use a different version of LWJGL to fix issues on certain systems).
This confusion is also a perfect example of why I provide a pre-modified json with my mod, as this is likely the main reason why this method of modding fails (I've had people tell me before that they tried to install one of my mods and the version did not show up or had an error on launch, which were very likely caused by a malformed json file).
You'd also think that somebody would have made a generic installer for jar mods by now; essentially, something where you add your mod's files to a folder within the installer jar, along with a file that sets the name of the profile and such and you just run it like any other jar file to install it (I suppose that nobody ever made one because jar mods for current versions are not very common these days; most of the ones that are still being updated, like Optifine, have their own installers, and few modders support older versions of their mods).
when i tried to run it, this error pops up
--- BEGIN ERROR REPORT 7cf3a456 ----------- BEGIN ERROR REPORT 7cf3a456 --------Generated 3/3/18 12:02 PM
Minecraft: Minecraft 1.2.5OS: Windows 7 (amd64) version 6.1Java: 1.8.0_25, Oracle CorporationVM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle CorporationLWJGL: 2.9.0OpenGL: GeForce GT 520/PCI/SSE2 version 4.1.0, NVIDIA Corporation
java.lang.NullPointerException at java.io.Reader.<init>(Reader.java:78) at java.io.InputStreamReader.<init>(InputStreamReader.java:97) at adn.a(SourceFile:62) at adn.a(SourceFile:99) at net.minecraft.client.Minecraft.a(SourceFile:262) at net.minecraft.client.Minecraft.run(SourceFile:657) at java.lang.Thread.run(Thread.java:745)--- END ERROR REPORT c6370beb ----------
(sorry for the late reply, i missed it when checking for replies on other threads)
when i tried to run it, this error pops up
--- BEGIN ERROR REPORT 7cf3a456 ----------- BEGIN ERROR REPORT 7cf3a456 --------Generated 3/3/18 12:02 PM
Minecraft: Minecraft 1.2.5OS: Windows 7 (amd64) version 6.1Java: 1.8.0_25, Oracle CorporationVM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle CorporationLWJGL: 2.9.0OpenGL: GeForce GT 520/PCI/SSE2 version 4.1.0, NVIDIA Corporation
java.lang.NullPointerException at java.io.Reader.<init>(Reader.java:78) at java.io.InputStreamReader.<init>(InputStreamReader.java:97) at adn.a(SourceFile:62) at adn.a(SourceFile:99) at net.minecraft.client.Minecraft.a(SourceFile:262) at net.minecraft.client.Minecraft.run(SourceFile:657) at java.lang.Thread.run(Thread.java:745)--- END ERROR REPORT c6370beb ----------
(sorry for the late reply, i missed it when checking for replies on other threads)
You need to run older versions in separate game directories; the game attempts to read invalid settings from options.txt and crashes as a result (this should not happen but Mojang apparently never thought to add in checks for invalid/uninterpretable values):
1.7.x will similarly crash if you set render distance to greater than 16, and even if the game doesn't crash it will reset many of the settings, forcing you to change them every time you switch versions.
Also, another thing to consider is that versions before 1.6 do not properly use custom directories; it is best to set them to the default directory (.minecraft) and use custom directories for newer versions:
You need to run older versions in separate game directories; the game attempts to read invalid settings from options.txt and crashes as a result (this should not happen but Mojang apparently never thought to add in checks for invalid/uninterpretable values):
1.7.x will similarly crash if you set render distance to greater than 16, and even if the game doesn't crash it will reset many of the settings, forcing you to change them every time you switch versions.
Also, another thing to consider is that versions before 1.6 do not properly use custom directories; it is best to set them to the default directory (.minecraft) and use custom directories for newer versions:
You need to run older versions in separate game directories; the game attempts to read invalid settings from options.txt and crashes as a result (this should not happen but Mojang apparently never thought to add in checks for invalid/uninterpretable values):
1.7.x will similarly crash if you set render distance to greater than 16, and even if the game doesn't crash it will reset many of the settings, forcing you to change them every time you switch versions.
Also, another thing to consider is that versions before 1.6 do not properly use custom directories; it is best to set them to the default directory (.minecraft) and use custom directories for newer versions:
ignore that last comment, that was me just being an idiot and not reading everything. whenever i try to start it with options having my us capitalized, this error shows up! how do i fix this one so i can go on a modding quest?
--- BEGIN ERROR REPORT 2f72aab9 ----------- BEGIN ERROR REPORT 2f72aab9 --------Generated 3/4/18 5:24 PM
Minecraft: Minecraft 1.2.4OS: Windows 7 (amd64) version 6.1Java: 1.8.0_25, Oracle CorporationVM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle CorporationLWJGL: 2.9.0OpenGL: GeForce GT 520/PCI/SSE2 version 4.1.0, NVIDIA Corporation
java.lang.IllegalArgumentException: URI is not hierarchical at java.io.File.<init>(File.java:418) at ModLoader.init(ModLoader.java:847) at ModLoader.addAllRenderers(ModLoader.java:156) at ahu.<init>(RenderManager.java:85) at ahu.<clinit>(RenderManager.java:12) at net.minecraft.client.Minecraft.a(Minecraft.java:323) at net.minecraft.client.Minecraft.run(Minecraft.java:684) at java.lang.Thread.run(Thread.java:745)--- END ERROR REPORT fc98a32a ----------
You need to run older versions in separate game directories; the game attempts to read invalid settings from options.txt and crashes as a result (this should not happen but Mojang apparently never thought to add in checks for invalid/uninterpretable values):
1.7.x will similarly crash if you set render distance to greater than 16, and even if the game doesn't crash it will reset many of the settings, forcing you to change them every time you switch versions.
Also, another thing to consider is that versions before 1.6 do not properly use custom directories; it is best to set them to the default directory (.minecraft) and use custom directories for newer versions:
ok. i think ive found the problem, but i dont know how to fix it. even with options.txt edited to en_US, it still gives the same error, even with seperate directories. do you know what could be causing this?
I have no idea what the second error you mention ("java.lang.IllegalArgumentException: URI is not hierarchical") means, nor can I find much information on it; I suspect it may be caused by the changes to the .minecraft folder since 1.5.2 (prior to then the Minecraft jar was inside a "bin" folder. From what I've found on this error it seems to be caused by accessing files that are in the wrong location; I did find an old thread about the same error and it seems to be caused by the changes the 1.6+ launcher made to the folder structure).
You may have to use a 3rd party launcher that can replicate the pre-1.6 environment (somebody posted a video in the aforementioned thread that has a fix but the video is unavailable, and the fix may not work since they have updated the launcher multiple times since then).
I have no idea what the second error you mention ("java.lang.IllegalArgumentException: URI is not hierarchical") means, nor can I find much information on it; I suspect it may be caused by the changes to the .minecraft folder since 1.5.2 (prior to then the Minecraft jar was inside a "bin" folder. From what I've found on this error it seems to be caused by accessing files that are in the wrong location; I did find an old thread about the same error and it seems to be caused by the changes the 1.6+ launcher made to the folder structure).
You may have to use a 3rd party launcher that can replicate the pre-1.6 environment (somebody posted a video in the aforementioned thread that has a fix but the video is unavailable, and the fix may not work since they have updated the launcher multiple times since then).
do you have any suggestions/links for any launchers like that?
im trying to download the evil minecraft mod for 1.2.5, but every time i try to load it, the files in the .jar get replaced! how do i stop this from happening so i can play some nostalgia?
Use a different launcher than Mojang's.
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
i dont quite understand what you mean. what other launchers are there for old minecraft mods?
Twitch, MultiMC are popular.
The reason I suggested another launcher is that the Mojang launcher now has a repair ability. If you change/delete/modify a file in the launcher, it will repair itself when opened. I do believe that older versions of MC (like 1.2.5) required modification of MC files to play modded. I think this is what your experiencing.
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
You can easily bypass the "repair ability" of Mojang's launcher; I have been playing with mods for 4+ years with no issues at all.
First, make a copy of the 1.2.5 versions folder
Second, rename it to something like 1.2.5-modname, as well as the jar and json file inside
Third, open the json file and search for "id":"1.2.5" and replace "1.2.5" with the name you used in step 2
Fourth, search the json for "downloads" and delete the section which contains the URL for "client.jar" (a bunch of random numbers and letters before this), making sure that you only delete the contents between (and including) the opening and closing brackets; {}
You should now be able to modify the jar without the launcher overwriting it; the launcher will complain that it can't download the modded jar but it shouldn't stop it from launching as it uses the local copy:
I even provide a pre-modified json with my mod so you can just drop it in after renaming the folder/files as before without having to edit it (this part is the biggest point of failure as it is easy to edit/delete the wrong lines (there is another "id" section that identifies the assets used) or miss a bracket); of course, an automated installer (e.g. Optifine/Forge, though I believe only since 1.6) is ideal (Optifine 1.6.4 has one but I just extract the jar and add the files directly as I believe it only works on vanilla jars and I have other mods installed).
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?
not sure if this is a glitch, but there are multiple downloads
""name": "net.java.jinput:jinput:2.0.5",
"downloads": {
"artifact": {
"size": 208338,
"sha1": "39c7796b469a600f72380316f6b1f11db6c2c7c4",
"path": "net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar",
"url": "https://libraries.minecraft.net/net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar"
}
}
},
{
"name": "net.java.jutils:jutils:1.0.0",
"downloads": {
"artifact": {
"size": 7508,
"sha1": "e12fe1fda814bd348c1579329c86943d2cd3c6a6",
"path": "net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar",
"url": "https://libraries.minecraft.net/net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar""
theres more than 2, this is just an example
The only one you want to remove is the one that refers to "client.jar", which is the name of the Minecraft jar on Mojang's servers; for example, for 1.6.4 it is this; I believe that all versions use "client.jar":
This also includes the server download, which can probably be left in but there is no point in leaving it in for a modded version; I just removed everything seen here. The downloads for other files are not really needed either but unless you are modifying them for some reason they can be left in (e.g. making the game use a different version of LWJGL to fix issues on certain systems).
This confusion is also a perfect example of why I provide a pre-modified json with my mod, as this is likely the main reason why this method of modding fails (I've had people tell me before that they tried to install one of my mods and the version did not show up or had an error on launch, which were very likely caused by a malformed json file).
You'd also think that somebody would have made a generic installer for jar mods by now; essentially, something where you add your mod's files to a folder within the installer jar, along with a file that sets the name of the profile and such and you just run it like any other jar file to install it (I suppose that nobody ever made one because jar mods for current versions are not very common these days; most of the ones that are still being updated, like Optifine, have their own installers, and few modders support older versions of their mods).
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?
when i tried to run it, this error pops up
--- BEGIN ERROR REPORT 7cf3a456 ----------- BEGIN ERROR REPORT 7cf3a456 --------Generated 3/3/18 12:02 PM
Minecraft: Minecraft 1.2.5OS: Windows 7 (amd64) version 6.1Java: 1.8.0_25, Oracle CorporationVM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle CorporationLWJGL: 2.9.0OpenGL: GeForce GT 520/PCI/SSE2 version 4.1.0, NVIDIA Corporation
java.lang.NullPointerException at java.io.Reader.<init>(Reader.java:78) at java.io.InputStreamReader.<init>(InputStreamReader.java:97) at adn.a(SourceFile:62) at adn.a(SourceFile:99) at net.minecraft.client.Minecraft.a(SourceFile:262) at net.minecraft.client.Minecraft.run(SourceFile:657) at java.lang.Thread.run(Thread.java:745)--- END ERROR REPORT c6370beb ----------
(sorry for the late reply, i missed it when checking for replies on other threads)
You need to run older versions in separate game directories; the game attempts to read invalid settings from options.txt and crashes as a result (this should not happen but Mojang apparently never thought to add in checks for invalid/uninterpretable values):
MCL-5837 Game versions 1.5.2 and lower crash when starting in a newer version's folder due to invalid language
1.7.x will similarly crash if you set render distance to greater than 16, and even if the game doesn't crash it will reset many of the settings, forcing you to change them every time you switch versions.
Also, another thing to consider is that versions before 1.6 do not properly use custom directories; it is best to set them to the default directory (.minecraft) and use custom directories for newer versions:
MCL-1394 Trouble with multiple custom directories
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?
is there a way to get older versions to handle custom directories and/or a guide to moving all my new mc version files to a different directory?
ignore that last comment, that was me just being an idiot and not reading everything. whenever i try to start it with options having my us capitalized, this error shows up! how do i fix this one so i can go on a modding quest?
--- BEGIN ERROR REPORT 2f72aab9 ----------- BEGIN ERROR REPORT 2f72aab9 --------Generated 3/4/18 5:24 PM
Minecraft: Minecraft 1.2.4OS: Windows 7 (amd64) version 6.1Java: 1.8.0_25, Oracle CorporationVM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle CorporationLWJGL: 2.9.0OpenGL: GeForce GT 520/PCI/SSE2 version 4.1.0, NVIDIA Corporation
java.lang.IllegalArgumentException: URI is not hierarchical at java.io.File.<init>(File.java:418) at ModLoader.init(ModLoader.java:847) at ModLoader.addAllRenderers(ModLoader.java:156) at ahu.<init>(RenderManager.java:85) at ahu.<clinit>(RenderManager.java:12) at net.minecraft.client.Minecraft.a(Minecraft.java:323) at net.minecraft.client.Minecraft.run(Minecraft.java:684) at java.lang.Thread.run(Thread.java:745)--- END ERROR REPORT fc98a32a ----------
ok. i think ive found the problem, but i dont know how to fix it. even with options.txt edited to en_US, it still gives the same error, even with seperate directories. do you know what could be causing this?
I have no idea what the second error you mention ("java.lang.IllegalArgumentException: URI is not hierarchical") means, nor can I find much information on it; I suspect it may be caused by the changes to the .minecraft folder since 1.5.2 (prior to then the Minecraft jar was inside a "bin" folder. From what I've found on this error it seems to be caused by accessing files that are in the wrong location; I did find an old thread about the same error and it seems to be caused by the changes the 1.6+ launcher made to the folder structure).
You may have to use a 3rd party launcher that can replicate the pre-1.6 environment (somebody posted a video in the aforementioned thread that has a fix but the video is unavailable, and the fix may not work since they have updated the launcher multiple times since then).
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?
do you have any suggestions/links for any launchers like that?