what happened
LoaderProfileJson only parses the legacy flat "gameArguments" format and does not handle the modern "arguments" object format. Loader profiles for Forge 1.17+ use: arguments : {"game": [...], "jvm": [...]}
But the parser only checks gamearguments: [...]
this cause two issues:
- "arguments.jvm" (e.g. --add-opens flags required for Java 17+) are silently dropped, causing Forge to crash on Java 17+ with IllegaAccessError
- "arguments.game" is also sliently dropped if the profile dosen't include the legacy "gameArguments" fallback.
steps to reproduce
- Create a Forge 1.20.1 ( need 1.17+) instance ( Forge)
- Set Java 17+ (Of course, need a correct java version to launch game)
- Launch - Forge crashes with module access error
rmcl version
0.3.0
operating system
Linux
additional context
(This issue was written with AI assistance for English translation.)
what happened
LoaderProfileJson only parses the legacy flat "gameArguments" format and does not handle the modern "arguments" object format. Loader profiles for Forge 1.17+ use:
arguments : {"game": [...], "jvm": [...]}But the parser only checks
gamearguments: [...]this cause two issues:
steps to reproduce
rmcl version
0.3.0
operating system
Linux
additional context
(This issue was written with AI assistance for English translation.)