I took a few looking around and this seemed the appropriate forum to ask this (since, >= 1.8 it would otherwise probably qualify as a modified client due to the now included microsoft-built speciality Java runtime), but to get to the point;
Has anyone successfully managed to utilize OpenJDK on windows for Minecraft >= 1.8.x? I used it (over the Oracle-official package) for a long long time and the performance differences were absolutely fantastic, but now it seems since the release of 1.8 w/ microsoft that Minecraft now ships with it's own all-built-in Java runtime to the point where you can't even trickingly otherwise put in OpenJDK over it and hope it might work.
Without OpenJDK though Minecraft is an absolutely sluggish beast and barely plays half as well as it used to pre-1.8, so figured I'd ask if anyone had any success in doing so as Googling and searching these forums gave me nothing in relation to this particular branch release.
New Windows launcher (and Curse Voice) does not ship ANY custom "special Microsoft built" Java runtime.
It's bundled with bog standard Oracle Java 8 update 25. And you can easily switch it to whatever you want. The launcher itself did not change one bit, its just set to use that bundled Java by default.
If you want complain about someone using custom Java builds then go to Apple. They did eventually abandon their custom Java 6 and allowed Java 8.
Strange, I did attempt to otherwise 'switch' it but the launcher always pulls from \Minecraft\runtime\jre-x64\1.8.0_25, and if I attempt to replace the libs in there with OpenJDK, MinecraftLauncher.exe complains about a "Corrupted runtime". So it would definitely seem it's not a case of easily switched, and gives me the impression of an otherwise specifically-modeled Java.
I should note my last time I played Minecraft really was just right around the time Microsoft did the acquisition, which had no included runtime at all, it simply used whatever Java it found in %PATH% or at most could be manually triggered by pointing a shortcut file to the OpenJDK javaw.exe w/ the minecraft binary as a parameter.
I did just realize though my OpenJDK is a 1.7.x based (though it seems they've backported some Java 1.8.x things), I suppose that could be the reason, perhaps lacking something it expects.
Let me see if I can find the not-windows installer version, as that seems to be what it pulled when I updated 1.7.
Edit: Ah yeah I had to click the "Show all downloads" link on the actual main site to get the original Minecraft.exe which is indeed using my OpenJDK (though it admittedly complains about the version but meh it works).
I took a few looking around and this seemed the appropriate forum to ask this (since, >= 1.8 it would otherwise probably qualify as a modified client due to the now included microsoft-built speciality Java runtime), but to get to the point;
Has anyone successfully managed to utilize OpenJDK on windows for Minecraft >= 1.8.x? I used it (over the Oracle-official package) for a long long time and the performance differences were absolutely fantastic, but now it seems since the release of 1.8 w/ microsoft that Minecraft now ships with it's own all-built-in Java runtime to the point where you can't even trickingly otherwise put in OpenJDK over it and hope it might work.
Without OpenJDK though Minecraft is an absolutely sluggish beast and barely plays half as well as it used to pre-1.8, so figured I'd ask if anyone had any success in doing so as Googling and searching these forums gave me nothing in relation to this particular branch release.
Strange, I did attempt to otherwise 'switch' it but the launcher always pulls from \Minecraft\runtime\jre-x64\1.8.0_25, and if I attempt to replace the libs in there with OpenJDK, MinecraftLauncher.exe complains about a "Corrupted runtime". So it would definitely seem it's not a case of easily switched, and gives me the impression of an otherwise specifically-modeled Java.
I should note my last time I played Minecraft really was just right around the time Microsoft did the acquisition, which had no included runtime at all, it simply used whatever Java it found in %PATH% or at most could be manually triggered by pointing a shortcut file to the OpenJDK javaw.exe w/ the minecraft binary as a parameter.
I did just realize though my OpenJDK is a 1.7.x based (though it seems they've backported some Java 1.8.x things), I suppose that could be the reason, perhaps lacking something it expects.
Let me see if I can find the not-windows installer version, as that seems to be what it pulled when I updated 1.7.
Edit: Ah yeah I had to click the "Show all downloads" link on the actual main site to get the original Minecraft.exe which is indeed using my OpenJDK (though it admittedly complains about the version but meh it works).