-
-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minecraft 1.17+ not working Mac OS Mojave #4320
Comments
please provide a log https://github.com/MultiMC/Launcher/wiki/Minecraft-Logs#uploading-logs |
I see log provided as pastebin link. I have same issue:
The issue is that it tries to load LWJGL 3.2.2 but M1 support was added only in 3.3.0 |
See LWJGL/lwjgl3#601 |
you need to download Java x86_64 not for ARM (M1) |
I have an M1 Mac |
Minecraft does not support ARM as of now, neither does MultiMC. Use x64 Java and the game will work just fine through Rosetta. |
Issue is not in Java. Issue is in LWJGL |
I guess I will just have to play using the normal launcher, because Using 84_64 java did not work, and I have no idea if I even installed it correctly, though if it is an issue LWJGL couldn't that be tested in the dev version, the normal launcher works just fine, but it also installs java for it self |
the other Java does work just fine, provide a log with it not working otherwise I'll assume you didnt pick it after installing it |
The thing is I don't know if I installed it correctly, as I don't know how to install java from azul, I got 1.17 from oracle |
nope thats still for ARM, if you want Oracle https://www.oracle.com/java/technologies/downloads/#jdk17-mac |
Ok it did work thanks for your help |
Operating System
macOS
Description of bug
I cannot open Minecraft 1.17 or Minecraft 1.18 on MultiMC, I have Java 17 installed and I am having it use Java 17 for both
https://paste.ee/p/htnhs
Steps to reproduce
Use a Mac with Mojave, open Multi MC, create a 1.17 or 1.18 instance and force it to use Java 17, or have Java 17 as your default, try launching Minecraft 1.17 or 1.18, and you will find it does not work
Suspected cause
No response
This issue is unique
The text was updated successfully, but these errors were encountered: