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
Unable to load the mod for forge 1.12.2 #1
Comments
I assume my forge version is not the same as the mod |
No, it is because the jar the HeadlessMc-Launcher uses to remove the rendering contains a class which is java 9. BUT, this does not crash you, right? From my observations it should not matter. |
You are not putting the headlessmc-lwjgl.jar in your mods folder manually? That is only meant in case you want to launch headlessly with other launchers. |
I thought it was to use the commands such as
Because I don't have those |
The hmc-specifics jar (https://github.com/3arthqu4ke/HMC-Specifics/releases) yes, the lwjgl.jar no. |
You should have those commands if you place the 1.12.2-b2 hmc-specifics jar in your mod folder. The Excpetion from this issue might occur but it wont stop anything from working. |
I had the hmc specifics 1.12.2 b2 full mod in my mods folder The issues happened when I placed it in |
Yeh but the game should resume and after some time gui and click commands should be available? |
My bad I had to launch with But I don't see the commands to control the game |
You do not need to launch with |
Are you using other mods than the HMC-Specifics? Is this on the docker image? |
Yes, let me test with only this mod |
Same thing with no mods |
What does the command look like that you use to launch Minecraft with HeadlessMc? |
Can you elaborate on what you meant ? |
My bad, got it |
Can you do Also if you list versions via |
Same thing with the latest forge |
Is it possible that you send the full log? Check that it does not contain any personal info. |
Or do you see anything like this in the log: |
No I don't see this error |
|
For some reason the jar file is empty |
Oh, I feel dumb, I curled the release with -O instead of -LO Issue fixed |
The text was updated successfully, but these errors were encountered: