Skip to content

Java8 321 has issues with forge 1.7.10 (perhaps others) #4444

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
bombcar opened this issue Jan 22, 2022 · 1 comment
Closed
1 task done

Java8 321 has issues with forge 1.7.10 (perhaps others) #4444

bombcar opened this issue Jan 22, 2022 · 1 comment
Labels
external

Comments

@bombcar
Copy link

bombcar commented Jan 22, 2022 •
edited
Loading

Operating System

Windows

Description of bug

Windows auto updated a user to Java8 u321 which hit: GTNewHorizons/GT-New-Horizons-Modpack#9532

Steps to reproduce

Latest mutlimc, latest Java8 u321 set as main java, try to run a 1.7.10 pack that uses awt (in this case gtnh 2.1.2.0).

Suspected cause

This is the same as McModLauncher/modlauncher#91 and apparently can be fixed in the launcher as such: https://github.com/McModLauncher/modlauncher/pull/92/files

This issue is unique

  • I have searched the issue tracker and did not find an issue describing my bug.
@bombcar bombcar added the bug label Jan 22, 2022
@phit
Copy link
Contributor

phit commented Jan 22, 2022

no it needs to be fixed by Forge, nothing for MultiMC to do about it, just use an older Java version until Forge is fixed

@phit phit closed this as completed Jan 22, 2022
@phit phit added external and removed bug labels Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
external
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bombcar @phit