<replace this line with the file content>
Details
- Commits
- Restricted Diffusion Commit
Restricted Diffusion Commit - Task Type
- Feature
- Affected Gamemode(s)
- none/unspecified
- Reproducible
- uncertain
- Category
- Launcher
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
<replace this line with the file content>
Event Timeline
-QA Testing-
Seems to be not fixed.
Using custom Java:
Using bundled java:
It seems to pass two arguments as "undefined" too.
The -server option passed to the jvm is strangely not listed in your screenshot, but is present in the code.
Additionally, the listed arguments (left of the red box) are those passed to the jar, not to the jvm. It's confusing having two options with the same name in different places in the same command that do very different things. e.g. the jar's -server option hosts a dedicated server.
in particular, the launcher passes these options to the jar:
- -force (if not dedicatedServer)
- -server (if dedicatedServer)
- -gui (if dedicatedServer)
- -port
- -auth value
when not starting a dedicated server, two of these options (-server, -gui) are replaced with undefined -- i'll fix this in a future build! but it's pretty minor right now.
so this issue is definitely still fixed.
the jvm performance, however, might do better with some further scrutiny!
-QA Testing-
Okay, checked that again.
The -server option gets passed to the dedicated server part.
All fine then. =)