You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per-version renderer overrides (#1975): Renderer settings were previously a single global (or per-instance) value, forcing repeated trips into the settings page whenever versions using different renderers were switched; overrides are now supported per version — Profile gained a rendererOverrides map (version id → renderer id), persisted with the config JSON and independent of "Enable per-instance settings"; launch resolution hooks into getLaunchOptions at a single point with the priority override > per-instance setting > global; a new renderer entry at the bottom-left of the version list opens a "Renderer Overrides" dialog listing every version in the current config with a per-row dropdown to assign a renderer, defaulting to "Follow settings" (no override); when an override exists and the renderer is changed elsewhere (global settings page, per-instance settings page, or long-press launch), a masking prompt offers "Update override / Clear override / Keep override" — the global settings page only checks the currently selected version and merges the prompt with the existing "this version uses independent settings" notice; when long-press launch is interrupted by the prompt it does not auto-launch, and choosing to update/clear the override continues the launch with the newly chosen renderer; an override pointing to an uninstalled or disabled renderer is treated as no override (launch resolution no longer falls back to the default renderer), and the overrides dialog clears stale overrides and persists when opened; choosing "Cancel" on the masking prompt rolls back the renderer just written into the version's settings, so abandoning the launch leaves no leftover changes
"Launch progress overlay" toggle under the in-game DEBUG category (#2005): The game menu settings gained showLaunchProgress (on by default, persisted with the menu settings) — when on, the launch shows the overlay background and progress spinner (the existing default behavior); when off, no overlay is shown and the game screen appears directly from the first frame; also fixed the first-frame misdetection in the log window's auto-show logic: GameMenu now records a graphicOutput flag set by onGraphicOutput as the "game has rendered its first frame" stage marker, log window visibility switches only take effect immediately before the first frame is rendered, and toggling after the first frame no longer interrupts the current state
⚡ Improvements
Task-list rows are now refreshed in batches (#2010): The TaskDialog task list used to refresh the whole ListView immediately on every task-row add/remove event, and high-speed downloads' frequent row changes made the page janky; task-row add/remove is now merged into 100ms batch refreshes so frequent changes only refresh once per frame; on release, task listeners are detached before the batch queue is cleared, so operations queued during the window before detaching cannot trigger a refresh after release
Unpacking built-in jars at launch now skips files already released via .sha1 comparison: The built-in jars in assets (MioLaunchWrapper.jar, MioLibPatcher.jar) now ship with .sha1 checksum files (generated and renewed automatically by the new updateBuiltinJarSha1 build task); before unpacking, the target file's digest is compared and identical files are skipped, so subsequent launches no longer rewrite them
Removed the artificial delay for small files during runtime extraction: The loop unpacking the runtime environment in RuntimeUtils used to sleep 25ms for every file of ≤20KB (a legacy trick to smooth the progress display); removed, so extraction time now reflects real IO
🐛 Bug Fixes
Cancellation is now allowed while waiting for authorization during Microsoft account re-login, fixing the dialog getting stuck after leaving the login page (#2013): OAuthAccountLoginDialog disabled the cancel button as soon as re-login started, so during the device-code authorization wait (which can take minutes) there was no way out and the dialog got stuck after leaving the login page; the cancel button now stays available while waiting, and tapping it cancels the in-progress login task and closes the dialog silently (no error dialog); authorization timeouts (NoSelectedCharacterException) also close silently; after a failed login shows the error dialog, the confirm button becomes available again so the login can be retried directly
Controlify requiring a controller reconnection before direct input worked (synced from ZalithLauncher2 PR #2204): SDL's Android backend throttles its initial device scan by 3 seconds and does not reset that across SDL_Quit, so at game start it could miss already-connected controllers or keep stale devices from the previous session; the HIDDeviceManager (USB/Bluetooth hotplug broadcast receiver and hidapi channel) that SDLActivity.onCreate normally creates was missing from this project's launch path, and since Controlify force-enables HIDAPI, hid_init failed silently without it; now SdlBridge proactively syncs the SDL device list once right after JNI setup (any difference from the actual devices is turned into hotplug events directly, so Controlify's initial discovery works), acquires the HIDDeviceManager manually (created once per process, its broadcast receiver staying alive after leaving the game to keep sensing hotplugs), and registers a system InputManager device listener that syncs the SDL device list on controller plug/unplug
Minecraft snapshots 13w16a~13w23b failing to launch (#2002): This batch of snapshots lacks the external language resource packs for non-English languages, so writing the lang (language) setting before launch made the game hang on the Mojang loading screen; these snapshots no longer get lang written, and any lang already written historically is reset to default English; the has_custom_resolution feature flag is also version-gated — versions before 1.6 (snapshot 13w25a) do not support custom resolution arguments and no longer receive them. Reference: HMCL (HMCL-dev/HMCL@087b2b6)
Runtime installation failures were impossible to diagnose (#2011): When a runtime component failed to install, RuntimeFragment's dialog only showed error.toString(), and since an exception's message can be empty (e.g. ROM-level IO errors), there was nothing to go on; the failure is now logged at SEVERE level under the component's name and the dialog shows the full stack trace
In-game control buttons casting a shadow (#2007#2008): Custom buttons floating over the game screen drew a projection shadow because of their elevation, adding a blurry dark edge; ControlButton now sets an empty outline (a ViewOutlineProvider returning an empty outline) so buttons no longer cast shadows, while elevation keeps only the buttons' stacking order
Main-screen version card icons squashed when non-square: The version card icon was previously carried as a background drawable, so the fixed 30dp×30dp size stretched non-square icons out of shape; it now uses setImageDrawable with fitCenter proportional scaling, so icons of any aspect ratio are no longer squashed (the default grass-block icon shown with no version selected is fixed the same way)
HMCL/MultiMC modpacks failing to launch with an NPE: When LauncherHelper was migrated to Kotlin, createCompletionTask was mistakenly treated as non-nullable, but HMCL/MultiMC modpacks have no completion task and the provider returns null, crashing at launch; the nullable contract is restored and null results are simply not added to the task list
Color clash of the inline dropdowns in the renderer overrides dialog: The dialog's FCLSpinner auto text tinting clashed with the dialog's fixed background (contrast-colored text was unreadable); the inline spinners now disable automatic text coloring