Major Overhaul (Java autoprovisionning, in-game config)#36
Major Overhaul (Java autoprovisionning, in-game config)#36Rongmario merged 10 commits intoCleanroomMC:masterfrom
Conversation
|
As both a player and a modpack developer, I’d love to see the |
What purpose would this feature serve? only one value should be present imo |
I have Adoptium installed, while one player might have Zulu and another GraalVM. As I understand it, if I set the parameter to Adoptium, the Relauncher will download an additional Java version for those other players. There is almost no difference between these three vendors, so why limit it to just one? I agree that a single value should be used for downloading, but for the local search on the user's device, I’d like to be able to specify multiple options. |
|
you can set preferred vendor to |
Oh, I see. I hadn't looked at the code, so I wasn't aware of that feature. |
You are correct, that's the progress bar for downloading libraries, it mistakenly fired even when there's nothing to download. Fixed now.
Don't know what else to call it, as this configuration pane is more targetted towards pack devs. |
Yeah makes sense too. Casual players won't even click that in-game config button I guess. Also what do you think about "Discard Changes" instead of "Cancel Configuration"? |
|
that's a good one, actually. |
|
Currently the relauncher seems to re-download Java even if it has already downloaded Java to |
| @Mod.EventHandler | ||
| public void preInit(FMLPreInitializationEvent event) { | ||
| MinecraftForge.EVENT_BUS.register(new OptionsMenuHandler()); | ||
| CleanroomRelauncher.LOGGER.info("Pre-Init Event has fired Relauncher"); | ||
| } |
There was a problem hiding this comment.
Should move this to CleanroomRelauncher, and that file should be marked as @Mod instead, as this one is just an event handler.
There was a problem hiding this comment.
Also, should enable use_tags in gradle.properties and use the constants from generated Tags for @Mod values.
There was a problem hiding this comment.
Should move this to
CleanroomRelauncher, and that file should be marked as@Modinstead, as this one is just an event handler.
I think it might be better to keep it in that file, for readability?
Some of the files are kinda huge already..
There was a problem hiding this comment.
It's not about readability, it's about naming. It's not clear that OptionsMenuHandler is a Forge mod entrypoint from the name. Please instead name it CleanroomRelauncherMod, or write a new class with that name which registers OptionsMenuHandler as a supplementary event handler.
yeah, i'm able to reproduce it now... |
Rongmario
left a comment
There was a problem hiding this comment.
Merging it first for a beta




Overview
This PR introduces a major overhaul of the Cleanroom Relauncher's user experience. It transitions the configuration process from a pre-launch GUI to a seamless install process with minimal user interaction.
Changelog
Relauncher can now do autoprovisionning of Java installations with FooJay API. it can be overriden by selecting
manual selection.The settings GUI now has argument checkboxes, to make the process of argument optimisations automated.
Relauncher now has new workflows:
Automatic Install, the relauncher.json can now be shipped with the pack to automatically trigger autoprovisionning, and requires 0 input from the user.Instead of always provisionning new java installs, polluting the environnement of the user, Relauncher will first check for java installations that matches
targetVersionandtargetVendor.Relauncher can be toggled in game, in both Cleanroom and Forge environnement, directly from an in-game Options menu.
Screenshots