The JVM argument I mentioned is actually what you don't want to have; the official launcher, and possibly others, always add it even if you don't specify it or have an Intel GPU, as seen in the launcher log; I only added the last four:
Otherwise, it seems that I can just make the "test" version the "official" version, it even lets me remove the class I originally modified to fix the issue, with the new fix placed in one I'd already modified (whether this is all that is needed would need further testing, given I haven't seen any other reports that the original fix didn't work, which I've recommended to a lot of people on e.g. Reddit. I also updated the original download for the Intel fix (reply 294) to include the new one).
When I have time, I can test the new version on a few other devices and see if everything renders properly. I'll use both the official Minecraft launcher and MultiMC for the test.
It's nice to be able to play your Minecraft version on so many devices, even if I don't have much time right now, it's something to look forward to !
This has probably been asked a lot, but I wanted to know if there's a possible way to get rid of the black "missing light" parts when new chunks are loaded.
For example, when I play in Creative Mode with 16 chuncks render distance and I fly around and let's say find a beautiful cliff, parts of it would be black/dark since the light needs time to generate. This makes filming sometimes difficult because not everything is visible.
One solution is to fly closer or even enter the "black" area and the light will then generate, but it's not always the case.
One solution is to fly closer or even enter the "black" area and the light will then generate, but it's not always the case.
It should eventually fix itself, as long as you are within 7 chunks, the area within which the game runs relight checks post-generation (the area is the "active chunk" area, where the game also randomly updates blocks like crops). You can also press F4 to speed up the relight checks and/or restart them at any time (I'd already made them 8 times faster than in vanilla, which takes about 10 minutes to check every block, the fast checks are 4 times faster still, taking 72 and 18 seconds respectively).
Otherwise, the main issue with lighting is that it can't be run unless chunks are fully loaded around the block being updated (within 14 blocks, or the maximum range of a light source, e.g. from 15 at the current block to 1 14 blocks away), vanilla doesn't even try updating the light level of the current block, which is guaranteed to be loaded (this is the cause of some odd lighting glitches, like obsidian that has replaced lava having a light level of 15, such lighting errors won't go away even if you cover it up. My code does set the light level of the block, but still won't update light around it). I did add a special lighting method which can update light to the edge of loaded chunks, which I use when placing certain light sources during world generation, but it is slower as it has to check every block, and still can't cross into unloaded chunks.
Also, the server doesn't seem to send lighting to the client, aside from the initial chunk packet, likely to reduce network traffic from all the block updates, as otherwise this could be used to update it much faster (in vanilla the server updates light 22.5 times faster than the client since it processes all 225 ticking chunks every tick while the client only processes 10, I only made it 4 times faster, which is still 12.25 times faster than the client, taking 6.4 seconds (this is not impacted by fast relight checks, F4 does recalculate server-side lighting; the reason why vanilla has persistent lighting errors is because it doesn't save whether a chunk had its light checked and chunks can often become unloaded before having had any checks at all due to the view distance being 3 chunks larger than the update distance and/or the player moving back and forth. There are also still some cases where lighting issues can persist, due to flowing liquids after world generation, but they are much less common than in vanilla*).
*A comparison of the Nether in vanilla and TMCW, where lighting issues are most pronounced, the Nether is also quite laggy in vanilla in part because the client is told to always recalculate lighting every time a chunk is loaded in the Nether, not just when it has been newly generated, but the errors are never fixed server-side:
Vanilla (this also shows some other issues, chunks randomly loading towards the north and west due to misplaced features, and less often to the south and east due to flowing liquids not checking for loaded chunks; both of which can cause lag during world generation):
TMCW; only the outermost chunks haven't been fully lit (the render distance was 8 so only the outermost ring of chunks won't receive updates):
As always, thank you so much for the detailed replay.
I got back from work an hour ago and tested it real quickly. So spamming F4 and being within a 6-8 chunk area of the parts you're trying to relight definitely works to 90% + .
I'm not sure if aiming actively with your pointer/cursor towards a specific blackened part of the map helps or not. It probably doesn't do anything.
I will make some further tests on the weekend if I have time. I also plan to test TMCW on several laptop devices and record/film it. But sadly with Germany's slow internet and lack of time due to real life, it's just not possible right now...
My earlier comment reported success, but I'm struggling more now that I attempted it on forge. I did the JVM arguments, added both fixes to the file, and have tried using both the opengl_fix json and the forge json (I'm. Every time I try to open the game, it crashes with exit code 1. I'm not sure what's causing the issue. Any ideas? Sorry to bug you.
My earlier comment reported success, but I'm struggling more now that I attempted it on forge. I did the JVM arguments, added both fixes to the file, and have tried using both the opengl_fix json and the forge json (I'm. Every time I try to open the game, it crashes with exit code 1. I'm not sure what's causing the issue. Any ideas? Sorry to bug you.
"Exit code (number)" is not a valid crash reason, all that means is that an error occurred (code 0 means no error), the actual cause will be in a crash report (located in the crash-reports folder) or shown in the game output (you'll need to edit the launcher settings to show the game output window).
Otherwise, only the "OpenGlHelper" fix has been known to work with Forge (at least, with this single post confirming it, and nothing about what mod(s) they used, which will likely be a major issue since "jar" mods are extremely incompatible with any other mods, I was actually a bit surprised that Forge started up at all; this was back when I only had the "OpenGlHelper" fix, which is also a much simpler class than "Tessellator", either of which can fix the issue, just that the "Tessellator" fix seems to work on more drivers/GPUs, but is also a much more complex class, which Forge itself may alter in some way).
I found the cause of the problem, and it's weird, because it seems like the JVM arguments should have overridden this error message.
"2024-08-17 16:45:18 [SEVERE] [ForgeModLoader] There is a binary discrepency between the expected input class bma (bma) and the actual class. Checksum on disk is b4fc8afc, in patch c5ffcc5c. Things are probably about to go very wrong. Did you put something into the jar file?
2024-08-17 16:45:18 [SEVERE] [ForgeModLoader] The game is going to exit, because this is a critical error, and it is very improbable that the modded game will work, please obtain clean jar files."
Are you sure you entered them correctly? You can look at the launcher log to see what the arguments passed to the game are; e.g. they look like this, with the last few being custom arguments (the others are added by the launcher):
I did identify one possible issue, I say to enter the arguments like this:
You will need to add "-Dfml.ignorePatchDiscrepancies -Dfml.ignoreInvalidMinecraftCertificates" to the JVM
arguments in order to get Forge to accept the modifications to the jar.
You do not include the quotes though (which I updated this to note):
hi, here to say that i just saw the 1.6.4 glfix after searching on google for hours and i thought it was amazing, vanilla finally works as it was intended, however ive noticed that forge still needs some work since after replacing the jar and json u only get the vanilla version rather than the patched version with forge. if u only replace the jar, youll just get the unpatched version of forge. no matter what i do forge just doesn't launch with the patch applied, i tried the launch args but its like theyre not even there as the launcher still tries to redownload the forge version without the new class applied
hi, here to say that i just saw the 1.6.4 glfix after searching on google for hours and i thought it was amazing, vanilla finally works as it was intended, however ive noticed that forge still needs some work since after replacing the jar and json u only get the vanilla version rather than the patched version with forge. if u only replace the jar, youll just get the unpatched version of forge. no matter what i do forge just doesn't launch with the patch applied, i tried the launch args but its like theyre not even there as the launcher still tries to redownload the forge version without the new class applied
You may need to edit the Forge json (you can use a simple text editor, like Notepad) to remove the "downloads" section which includes the client jar, which looks like this:
After removing it the json should look like this (I included stuff immediately before and after the downloads section to show how they should join afterwards. I assume that the "id": "1.6.4" part is the name of the Forge version, I don't know exactly what it looks like, you could also send me the file so I could edit it (it is a text file so you could even just post it in a spoiler, then paste my changed version into the original file, making sure to keep a copy so it can be restored if needed):
ty for replying so quickly, i tried doing what you mentioned and replaced the file with
{"assets": "legacy", "id": "forge-9.11.1.1345"}
but the game would quickly crash upon doing this, i also tried clearing the entire downloads section but the same issue happened, here ill send the normal forge json for 1.6.4
ty for replying so quickly, i tried doing what you mentioned and replaced the file with
First of all, you weren't supposed to replace the entire file like that - I only showed the part you needed to change.
As for the Forge json, I can see the problem; "inheritsFrom": "1.6.4" and "jar": "1.6.4" means that they are simply extending the original json and jar instead of using their entirely original versions (like the one I provide); the only way to fix this would be to merge both files; I knew that newer versions of Forge had started doing this but I didn't think they did it until much later than 1.6.4 (I once used Forge on 1.6.2, back when that was the current version, so very old, and it had its own json and jar files, which I'd edited to include my own jar mods); based on the "time" this version of Forge was released in 2015, which probably explains it. An older version might still use the old way but I don't know when this change was made or if it matters for mods (some might need the latest version).
I did try merging the files, adding the libraries which appear to have been added by Forge (everything before "jopt-simple-4.5.jar") and the "--tweakClass" argument; this needs to be saved as "forge-9.11.1.1345.json" and if not present copy the 1.6.4 jar and give it the same name (Forge does not directly modify the jar, it is added as the first library in the list when the game launches, this was true even back in 1.6.2):
There is also a way to add a jar mod as a library, which I'd actually used for 1.6.2, for both Optifine and my own mods, but it is even more complicated to set up:
hey, ty for the help but i managed to sort it out by adding optifine and replacing its bma.class with yours, this worked like a charm and finally fixed the issue on forge (still couldnt get it to happen with just forges jar)
hey, ty for the help but i managed to sort it out by adding optifine and replacing its bma.class with yours, this worked like a charm and finally fixed the issue on forge (still couldnt get it to happen with just forges jar)
Does this actually work? I'd expect it to have caused issues because Optifine makes some changes to the same class, including a call to "Config.initDisplay()" and a couple fields added for "brightness"; at the least it seems like a lot of Optifine code isn't being properly initialized, and if anything tries to access the nonexistent fields the game will crash:
Actually, the "lastBrightnessX / Y" fields seem to be some unused code as I searched the Optifine source and didn't find any references to them outside of OpenGlHelper, which only sets them, so only the call to "Config.initDisplay" is an issue (at the least, it seems that antialiasing will not work, and some possibly of its other special settings, but e.g. "smooth world" only works on single-core CPUs anyway).
surprised me that it worked too but it worked fine, maybe its cuz of the optifine version i was using which was HD U D1 but it hasnt caused any crashes and as far as i can tell optifine works as it should
I made a video response, in order to not spam with tons of pictures. Thank you so much for the help!
The JVM argument I mentioned is actually what you don't want to have; the official launcher, and possibly others, always add it even if you don't specify it or have an Intel GPU, as seen in the launcher log; I only added the last four:
Otherwise, it seems that I can just make the "test" version the "official" version, it even lets me remove the class I originally modified to fix the issue, with the new fix placed in one I'd already modified (whether this is all that is needed would need further testing, given I haven't seen any other reports that the original fix didn't work, which I've recommended to a lot of people on e.g. Reddit. I also updated the original download for the Intel fix (reply 294) to include the new one).
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?
Thank you so much!
When I have time, I can test the new version on a few other devices and see if everything renders properly. I'll use both the official Minecraft launcher and MultiMC for the test.
It's nice to be able to play your Minecraft version on so many devices, even if I don't have much time right now, it's something to look forward to
!
This has probably been asked a lot, but I wanted to know if there's a possible way to get rid of the black "missing light" parts when new chunks are loaded.
For example, when I play in Creative Mode with 16 chuncks render distance and I fly around and let's say find a beautiful cliff, parts of it would be black/dark since the light needs time to generate. This makes filming sometimes difficult because not everything is visible.
One solution is to fly closer or even enter the "black" area and the light will then generate, but it's not always the case.
It should eventually fix itself, as long as you are within 7 chunks, the area within which the game runs relight checks post-generation (the area is the "active chunk" area, where the game also randomly updates blocks like crops). You can also press F4 to speed up the relight checks and/or restart them at any time (I'd already made them 8 times faster than in vanilla, which takes about 10 minutes to check every block, the fast checks are 4 times faster still, taking 72 and 18 seconds respectively).
Otherwise, the main issue with lighting is that it can't be run unless chunks are fully loaded around the block being updated (within 14 blocks, or the maximum range of a light source, e.g. from 15 at the current block to 1 14 blocks away), vanilla doesn't even try updating the light level of the current block, which is guaranteed to be loaded (this is the cause of some odd lighting glitches, like obsidian that has replaced lava having a light level of 15, such lighting errors won't go away even if you cover it up. My code does set the light level of the block, but still won't update light around it). I did add a special lighting method which can update light to the edge of loaded chunks, which I use when placing certain light sources during world generation, but it is slower as it has to check every block, and still can't cross into unloaded chunks.
Also, the server doesn't seem to send lighting to the client, aside from the initial chunk packet, likely to reduce network traffic from all the block updates, as otherwise this could be used to update it much faster (in vanilla the server updates light 22.5 times faster than the client since it processes all 225 ticking chunks every tick while the client only processes 10, I only made it 4 times faster, which is still 12.25 times faster than the client, taking 6.4 seconds (this is not impacted by fast relight checks, F4 does recalculate server-side lighting; the reason why vanilla has persistent lighting errors is because it doesn't save whether a chunk had its light checked and chunks can often become unloaded before having had any checks at all due to the view distance being 3 chunks larger than the update distance and/or the player moving back and forth. There are also still some cases where lighting issues can persist, due to flowing liquids after world generation, but they are much less common than in vanilla*).
*A comparison of the Nether in vanilla and TMCW, where lighting issues are most pronounced, the Nether is also quite laggy in vanilla in part because the client is told to always recalculate lighting every time a chunk is loaded in the Nether, not just when it has been newly generated, but the errors are never fixed server-side:
TMCW; only the outermost chunks haven't been fully lit (the render distance was 8 so only the outermost ring of chunks won't receive updates):
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?
As always, thank you so much for the detailed replay.
I got back from work an hour ago and tested it real quickly. So spamming F4 and being within a 6-8 chunk area of the parts you're trying to relight definitely works to 90% + .
I'm not sure if aiming actively with your pointer/cursor towards a specific blackened part of the map helps or not. It probably doesn't do anything.
I will make some further tests on the weekend if I have time. I also plan to test TMCW on several laptop devices and record/film it. But sadly with Germany's slow internet and lack of time due to real life, it's just not possible right now...
Anyways, cheers!
Your post about fixing the graphic issues in MC 1.6.4 is almost a year old now but I'm replying anyways to thank you for this. Thank you for the help.
My earlier comment reported success, but I'm struggling more now that I attempted it on forge. I did the JVM arguments, added both fixes to the file, and have tried using both the opengl_fix json and the forge json (I'm. Every time I try to open the game, it crashes with exit code 1. I'm not sure what's causing the issue. Any ideas? Sorry to bug you.
"Exit code (number)" is not a valid crash reason, all that means is that an error occurred (code 0 means no error), the actual cause will be in a crash report (located in the crash-reports folder) or shown in the game output (you'll need to edit the launcher settings to show the game output window).
Otherwise, only the "OpenGlHelper" fix has been known to work with Forge (at least, with this single post confirming it, and nothing about what mod(s) they used, which will likely be a major issue since "jar" mods are extremely incompatible with any other mods, I was actually a bit surprised that Forge started up at all; this was back when I only had the "OpenGlHelper" fix, which is also a much simpler class than "Tessellator", either of which can fix the issue, just that the "Tessellator" fix seems to work on more drivers/GPUs, but is also a much more complex class, which Forge itself may alter in some way).
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?
I found the cause of the problem, and it's weird, because it seems like the JVM arguments should have overridden this error message.
"2024-08-17 16:45:18 [SEVERE] [ForgeModLoader] There is a binary discrepency between the expected input class bma (bma) and the actual class. Checksum on disk is b4fc8afc, in patch c5ffcc5c. Things are probably about to go very wrong. Did you put something into the jar file?
2024-08-17 16:45:18 [SEVERE] [ForgeModLoader] The game is going to exit, because this is a critical error, and it is very improbable that the modded game will work, please obtain clean jar files."
Are you sure you entered them correctly? You can look at the launcher log to see what the arguments passed to the game are; e.g. they look like this, with the last few being custom arguments (the others are added by the launcher):
I did identify one possible issue, I say to enter the arguments like this:
You do not include the quotes though (which I updated this to note):
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?
hi, here to say that i just saw the 1.6.4 glfix after searching on google for hours and i thought it was amazing, vanilla finally works as it was intended, however ive noticed that forge still needs some work since after replacing the jar and json u only get the vanilla version rather than the patched version with forge. if u only replace the jar, youll just get the unpatched version of forge. no matter what i do forge just doesn't launch with the patch applied, i tried the launch args but its like theyre not even there as the launcher still tries to redownload the forge version without the new class applied
You may need to edit the Forge json (you can use a simple text editor, like Notepad) to remove the "downloads" section which includes the client jar, which looks like this:
After removing it the json should look like this (I included stuff immediately before and after the downloads section to show how they should join afterwards. I assume that the "id": "1.6.4" part is the name of the Forge version, I don't know exactly what it looks like, you could also send me the file so I could edit it (it is a text file so you could even just post it in a spoiler, then paste my changed version into the original file, making sure to keep a copy so it can be restored if needed):
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?
ty for replying so quickly, i tried doing what you mentioned and replaced the file with
but the game would quickly crash upon doing this, i also tried clearing the entire downloads section but the same issue happened, here ill send the normal forge json for 1.6.4
First of all, you weren't supposed to replace the entire file like that - I only showed the part you needed to change.
As for the Forge json, I can see the problem; "inheritsFrom": "1.6.4" and "jar": "1.6.4" means that they are simply extending the original json and jar instead of using their entirely original versions (like the one I provide); the only way to fix this would be to merge both files; I knew that newer versions of Forge had started doing this but I didn't think they did it until much later than 1.6.4 (I once used Forge on 1.6.2, back when that was the current version, so very old, and it had its own json and jar files, which I'd edited to include my own jar mods); based on the "time" this version of Forge was released in 2015, which probably explains it. An older version might still use the old way but I don't know when this change was made or if it matters for mods (some might need the latest version).
I did try merging the files, adding the libraries which appear to have been added by Forge (everything before "jopt-simple-4.5.jar") and the "--tweakClass" argument; this needs to be saved as "forge-9.11.1.1345.json" and if not present copy the 1.6.4 jar and give it the same name (Forge does not directly modify the jar, it is added as the first library in the list when the game launches, this was true even back in 1.6.2):
{
"name": "net.minecraftforge:minecraftforge:9.11.1.1345",
"url": "https://modloaders.forgecdn.net/647622546/maven/"
},
{
"name": "net.minecraft:launchwrapper:1.8",
"serverreq": true
},
{
"name": "org.ow2.asm:asm-all:4.1",
"serverreq": true
},
{
"name": "org.scala-lang:scala-library:2.10.2",
"url": "https://modloaders.forgecdn.net/647622546/maven/",
"serverreq": true,
"clientreq": true
},
{
"name": "org.scala-lang:scala-compiler:2.10.2",
"url": "https://modloaders.forgecdn.net/647622546/maven/",
"serverreq": true,
"clientreq": true
},
{
"name": "lzma:lzma:0.0.1",
"serverreq": true
},
{"downloads": {"artifact": {"path": "net/sf/jopt-simple/jopt-simple/4.5/jopt-simple-4.5.jar", "sha1": "6065cc95c661255349c1d0756657be17c29a4fd3", "size": 61311, "url": "https://libraries.minecraft.net/net/sf/jopt-simple/jopt-simple/4.5/jopt-simple-4.5.jar"}}, "name": "net.sf.jopt-simple:jopt-simple:4.5"}, {"downloads": {"artifact": {"path": "com/paulscode/codecjorbis/20101023/codecjorbis-20101023.jar", "sha1": "c73b5636faf089d9f00e8732a829577de25237ee", "size": 103871, "url": "https://libraries.minecraft.net/com/paulscode/codecjorbis/20101023/codecjorbis-20101023.jar"}}, "name": "com.paulscode:codecjorbis:20101023"}, {"downloads": {"artifact": {"path": "com/paulscode/codecwav/20101023/codecwav-20101023.jar", "sha1": "12f031cfe88fef5c1dd36c563c0a3a69bd7261da", "size": 5618, "url": "https://libraries.minecraft.net/com/paulscode/codecwav/20101023/codecwav-20101023.jar"}}, "name": "com.paulscode:codecwav:20101023"}, {"downloads": {"artifact": {"path": "com/paulscode/libraryjavasound/20101123/libraryjavasound-20101123.jar", "sha1": "5c5e304366f75f9eaa2e8cca546a1fb6109348b3", "size": 21679, "url": "https://libraries.minecraft.net/com/paulscode/libraryjavasound/20101123/libraryjavasound-20101123.jar"}}, "name": "com.paulscode:libraryjavasound:20101123"}, {"downloads": {"artifact": {"path": "com/paulscode/librarylwjglopenal/20100824/librarylwjglopenal-20100824.jar", "sha1": "73e80d0794c39665aec3f62eee88ca91676674ef", "size": 18981, "url": "https://libraries.minecraft.net/com/paulscode/librarylwjglopenal/20100824/librarylwjglopenal-20100824.jar"}}, "name": "com.paulscode:librarylwjglopenal:20100824"}, {"downloads": {"artifact": {"path": "com/paulscode/soundsystem/20120107/soundsystem-20120107.jar", "sha1": "419c05fe9be71f792b2d76cfc9b67f1ed0fec7f6", "size": 65020, "url": "https://libraries.minecraft.net/com/paulscode/soundsystem/20120107/soundsystem-20120107.jar"}}, "name": "com.paulscode:soundsystem:20120107"}, {"downloads": {"artifact": {"path": "argo/argo/2.25_fixed/argo-2.25_fixed.jar", "sha1": "751761ce15a3e3aaf3fc75b9f013ff8f7b88a585", "size": 74953, "url": "https://libraries.minecraft.net/argo/argo/2.25_fixed/argo-2.25_fixed.jar"}}, "name": "argo:argo:2.25_fixed"}, {"downloads": {"artifact": {"path": "org/bouncycastle/bcprov-jdk15on/1.47/bcprov-jdk15on-1.47.jar", "sha1": "b6f5d9926b0afbde9f4dbe3db88c5247be7794bb", "size": 1997327, "url": "https://libraries.minecraft.net/org/bouncycastle/bcprov-jdk15on/1.47/bcprov-jdk15on-1.47.jar"}}, "name": "org.bouncycastle:bcprov-jdk15on:1.47"}, {"downloads": {"artifact": {"path": "com/google/guava/guava/14.0/guava-14.0.jar", "sha1": "67b7be4ee7ba48e4828a42d6d5069761186d4a53", "size": 2189111, "url": "https://libraries.minecraft.net/com/google/guava/guava/14.0/guava-14.0.jar"}}, "name": "com.google.guava:guava:14.0"}, {"downloads": {"artifact": {"path": "org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar", "sha1": "905075e6c80f206bbe6cf1e809d2caa69f420c76", "size": 315805, "url": "https://libraries.minecraft.net/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar"}}, "name": "org.apache.commons:commons-lang3:3.1"}, {"downloads": {"artifact": {"path": "commons-io/commons-io/2.4/commons-io-2.4.jar", "sha1": "b1b6ea3b7e4aa4f492509a4952029cd8e48019ad", "size": 185140, "url": "https://libraries.minecraft.net/commons-io/commons-io/2.4/commons-io-2.4.jar"}}, "name": "commons-io:commons-io:2.4"}, {"downloads": {"artifact": {"path": "net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar", "sha1": "39c7796b469a600f72380316f6b1f11db6c2c7c4", "size": 208338, "url": "https://libraries.minecraft.net/net/java/jinput/jinput/2.0.5/jinput-2.0.5.jar"}}, "name": "net.java.jinput:jinput:2.0.5"}, {"downloads": {"artifact": {"path": "net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar", "sha1": "e12fe1fda814bd348c1579329c86943d2cd3c6a6", "size": 7508, "url": "https://libraries.minecraft.net/net/java/jutils/jutils/1.0.0/jutils-1.0.0.jar"}}, "name": "net.java.jutils:jutils:1.0.0"}, {"downloads": {"artifact": {"path": "com/google/code/gson/gson/2.2.2/gson-2.2.2.jar", "sha1": "1f96456ca233dec780aa224bff076d8e8bca3908", "size": 189285, "url": "https://libraries.minecraft.net/com/google/code/gson/gson/2.2.2/gson-2.2.2.jar"}}, "name": "com.google.code.gson:gson:2.2.2"}, {"downloads": {"artifact": {"path": "org/lwjgl/lwjgl/lwjgl/2.9.0/lwjgl-2.9.0.jar", "sha1": "5654d06e61a1bba7ae1e7f5233e1106be64c91cd", "size": 994633, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl/2.9.0/lwjgl-2.9.0.jar"}}, "name": "org.lwjgl.lwjgl:lwjgl:2.9.0", "rules": [{"action": "allow"}, {"action": "disallow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"artifact": {"path": "org/lwjgl/lwjgl/lwjgl_util/2.9.0/lwjgl_util-2.9.0.jar", "sha1": "a778846b64008fc7f48ead2377f034e547991699", "size": 173360, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl_util/2.9.0/lwjgl_util-2.9.0.jar"}}, "name": "org.lwjgl.lwjgl:lwjgl_util:2.9.0", "rules": [{"action": "allow"}, {"action": "disallow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"classifiers": {"natives-linux": {"path": "org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-linux.jar", "sha1": "2ba5dcb11048147f1a74eff2deb192c001321f77", "size": 569061, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-linux.jar"}, "natives-osx": {"path": "org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-osx.jar", "sha1": "6621b382cb14cc409b041d8d72829156a87c31aa", "size": 518924, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-osx.jar"}, "natives-windows": {"path": "org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-windows.jar", "sha1": "3f11873dc8e84c854ec7c5a8fd2e869f8aaef764", "size": 609967, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl-platform/2.9.0/lwjgl-platform-2.9.0-natives-windows.jar"}}}, "extract": {"exclude": ["META-INF/"]}, "name": "org.lwjgl.lwjgl:lwjgl-platform:2.9.0", "natives": {"linux": "natives-linux", "osx": "natives-osx", "windows": "natives-windows"}, "rules": [{"action": "allow"}, {"action": "disallow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"artifact": {"path": "org/lwjgl/lwjgl/lwjgl/2.9.1-nightly-20130708-debug3/lwjgl-2.9.1-nightly-20130708-debug3.jar", "sha1": "884511652c756fac16b37236f863f346bd1ea121", "size": 996625, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl/2.9.1-nightly-20130708-debug3/lwjgl-2.9.1-nightly-20130708-debug3.jar"}}, "name": "org.lwjgl.lwjgl:lwjgl:2.9.1-nightly-20130708-debug3", "rules": [{"action": "allow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"artifact": {"path": "org/lwjgl/lwjgl/lwjgl_util/2.9.1-nightly-20130708-debug3/lwjgl_util-2.9.1-nightly-20130708-debug3.jar", "sha1": "fb693ba4e22a85432a32e8a048893dc7a92f42ac", "size": 173338, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl_util/2.9.1-nightly-20130708-debug3/lwjgl_util-2.9.1-nightly-20130708-debug3.jar"}}, "name": "org.lwjgl.lwjgl:lwjgl_util:2.9.1-nightly-20130708-debug3", "rules": [{"action": "allow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"classifiers": {"natives-osx": {"path": "org/lwjgl/lwjgl/lwjgl-platform/2.9.1-nightly-20130708-debug3/lwjgl-platform-2.9.1-nightly-20130708-debug3-natives-osx.jar", "sha1": "a9b83ad85742cad09c3574a91b0423bac3f7a0f5", "size": 458181, "url": "https://libraries.minecraft.net/org/lwjgl/lwjgl/lwjgl-platform/2.9.1-nightly-20130708-debug3/lwjgl-platform-2.9.1-nightly-20130708-debug3-natives-osx.jar"}}}, "extract": {"exclude": ["META-INF/"]}, "name": "org.lwjgl.lwjgl:lwjgl-platform:2.9.1-nightly-20130708-debug3", "natives": {"linux": "natives-linux", "osx": "natives-osx", "windows": "natives-windows"}, "rules": [{"action": "allow", "os": {"name": "osx", "version": "^10\\.5\\.\\d$"}}]}, {"downloads": {"classifiers": {"natives-linux": {"path": "net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-linux.jar", "sha1": "7ff832a6eb9ab6a767f1ade2b548092d0fa64795", "size": 10362, "url": "https://libraries.minecraft.net/net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-linux.jar"}, "natives-osx": {"path": "net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-osx.jar", "sha1": "53f9c919f34d2ca9de8c51fc4e1e8282029a9232", "size": 12186, "url": "https://libraries.minecraft.net/net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-osx.jar"}, "natives-windows": {"path": "net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-windows.jar", "sha1": "385ee093e01f587f30ee1c8a2ee7d408fd732e16", "size": 155179, "url": "https://libraries.minecraft.net/net/java/jinput/jinput-platform/2.0.5/jinput-platform-2.0.5-natives-windows.jar"}}}, "extract": {"exclude": ["META-INF/"]}, "name": "net.java.jinput:jinput-platform:2.0.5", "natives": {"linux": "natives-linux", "osx": "natives-osx", "windows": "natives-windows"}}], "mainClass": "net.minecraft.client.main.Main", "minecraftArguments": "--username ${auth_player_name} --session ${auth_session} --version ${version_name} --gameDir ${game_directory} --assetsDir ${game_assets} --tweakClass cpw.mods.fml.common.launcher.FMLTweaker", "minimumLauncherVersion": 4, "releaseTime": "2013-09-19T15:52:37+00:00", "time": "2013-09-19T15:52:37+00:00", "type": "release"}
There is also a way to add a jar mod as a library, which I'd actually used for 1.6.2, for both Optifine and my own mods, but it is even more complicated to set up:
https://minecraft.wiki/w/Mods/Installing_OptiForge/Forge_Installer?oldid=1063125
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?
hey, ty for the help but i managed to sort it out by adding optifine and replacing its bma.class with yours, this worked like a charm and finally fixed the issue on forge (still couldnt get it to happen with just forges jar)
Does this actually work? I'd expect it to have caused issues because Optifine makes some changes to the same class, including a call to "Config.initDisplay()" and a couple fields added for "brightness"; at the least it seems like a lot of Optifine code isn't being properly initialized, and if anything tries to access the nonexistent fields the game will crash:
Actually, the "lastBrightnessX / Y" fields seem to be some unused code as I searched the Optifine source and didn't find any references to them outside of OpenGlHelper, which only sets them, so only the call to "Config.initDisplay" is an issue (at the least, it seems that antialiasing will not work, and some possibly of its other special settings, but e.g. "smooth world" only works on single-core CPUs anyway).
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?
surprised me that it worked too but it worked fine, maybe its cuz of the optifine version i was using which was HD U D1 but it hasnt caused any crashes and as far as i can tell optifine works as it should