A custom launcher for Minecraft that allows you to easily manage multiple installations of Minecraft at once
Go to multimc.org to get the binaries. See changelog for changes.
This release brings initial support for Microsoft accounts, along with a nice pile of modpack platform changes and improved Java runtime detection.
What comes next:
This is the first release with Microsoft accounts in.
Implementation is loosely based on documentation available from wiki.vg with some notable changes:
More complete implementation including getting and displaying GamerTags (see XR-046).
Using the OAuth Device Flow instead of closely integrating with a browser engine.
MultiMC asks you to open a Microsoft login web page and put in a code that lets MultiMC authenticate.
This lets you authenticate on a completely separate device like your phone, leaving code we ship and the computer you may not even trust out of the picture.
As part of this, the skin fetching no longer uses a third party service and instead gets skins directly from Mojang.
Capes can also be selected in MultiMC now. With how many people will now get one for migrating their accounts, it only makes sense.
Because of issues with the Microsoft accounts, we now have two builds on macOS:
The old build with Qt 5.6 that does not work with Microsoft accounts, but can run on macOS older than 10.13.
A new build with Qt 5.15.2 that does work with Microsoft accounts, can use the new macOS dark theme and highlight colors, but requires at least macOS 10.13.
MultiMC will update to the 5.15.2 builds when it detects that this is possible. It may look like it is updating twice, just let it do its thing.
Similar approach got attempted on Windows, aiming to fix various display scaling and theming issues, but it ran into too many problems and will be attempted later, with more caution.
In general, the modpack platform pages have been made more consistent with each other (GH-3118, GH-3720, GH-3731).
FTB improvements:
Modpack file downloads are now checked with checksums and cached.
GH-1949: Allow Legacy FTB and FTB pack downloads to be aborted.
CurseForge improvements:
CurseForge modpack platform is now presented as CurseForge, not Twitch.
UI has been updated to match other platforms
Added sorting
GH-3667: Added version selection
GH-3611: Added ability to install beta versions
GH-3633: When a CurseForge pack is available for multiple Minecraft versions, we assume the latest one.
ATLauncher improvements:
Fixed bugs in FTB platform search.
Forge installation is disabled on Minecraft 1.17+ because of incompatible/unresolved changes on the Forge side.
We're going to aim for fixing it in time for 1.18. Thankfully, 1.17 is more of a in-between release, so go play some 1.16.x packs!
GH-2529: On macOS, MultiMC will ask to move all the instance data to a new Data folder in order to fix long load times caused by macOS checking all files.
Detection of a large amount of various Java runtime flavors have been added.
It is now possible to join servers when starting an instance:
From command line via the --launch and --server arguments.
Or by setting this up in the instance settings page.
This may not work correctly in some cases, because it is a rarely used feature and modders do not test with it.
MultiMC now prints resolved IP addresses of Minecraft services into the game log for diagnostic purposes.
Updated instance icons based on Minecraft textures.
Forge mods.toml files are now used for displaying mods in the UI.
Datapack button is now disabled when no world is selected.
MultiMC warns about GLFW and OpenAL workarounds being enabled in the game log.
Languages in the translations list are now sorted by their two/three letter key
GH-3450: Displaying and recording gameplay time is now optional and can be turned off.
GH-3930: MultiMC can now track the gameplay time of the last session.
GH-3033: The version pages of instances now have a filter bar.
GH-2971: UI descriptions of texture and resource packs no longer mention mods.
Quick and dirty minimum Java runtime versions checks have been added. This needs to be expanded in the future.
After roughly one year of maintenance and development work by various contributors, we're just calling it a good time to release.
What got added since the last time? Quite a bit! But in general, this is more of a spring cleaning before the major changes that we need to make come in.
What comes next after this:
We'll probably call it 0.7 once all these are in place.
We've added a whole bunch of new modpack platforms to pick from right into the new instance dialog. If you run into any unusual issues with the imported packs, report them on the bug tracker.
Added a CurseForge pack browser
GH-3095: Added an FTB pack browser
Temporarily, MultiMC ignores download failures for FTB packs (GH-3304). This is because the platform has consistency issues.
GH-469: Added a Technic/Solder pack browser
GH-405: Added a ATLauncher pack browser
Added the option to not use OpenAL and/or GLFW libraries bundled with the game.
This is interesting if you have ones that come with your system and work better.
Skins (the part used for account icons) are now rendered with the overlay on.
GH-3130: Skin upload has been switched over to the new Mojang API and should have less issues.
MultiMC now shows world icons and allows resetting world icons in View Worlds.
GH-3229: Copy seed button has been updated to be compatible with newer versions of the game.
GH-3427: View Worlds now has a very simple Datapacks button - it just opens the system file browser.
GH-3189: Updated nbt library - this makes View Worlds work properly again for newer versions of the game.
Fixed online saving in Classic versions.
GH-3131: Fixed not working with proxy ports greater than 32767.
Proxy login details are no longer logged in files.
GH-3467: The launch could stall in the ScanModFolders task if the mod folders didn't exist yet.
GH-3602: Pre-launch commands could fail on first launch of the instance because the .minecraft folder has not been created yet.
GH-3234: At build time, the meta URL can be changed.
Removed some hacks previously required to get Forge working
MultiMC no longer contains pack200 and the custom lzma format support used by Forge only.
Some preparations have been done to allow downloading Java runtimes from Mojang - support for the Piston repository.
Compatibility with unusual build environments has been increased
Yep. That is all.
See full changelog: https://github.com/MultiMC/MultiMC5/blob/d58481e0de15ec4f1eb60de9a42c6cc9ec330d86/changelog.md
See full changelog: https://github.com/MultiMC/MultiMC5/blob/c291946d2a8c3e03940da4070533e124283d303c/changelog.md
MultiMC now has FTB integration:
Version lists now show release dates where available.
New instance dialog:
Other Logs page:
Icon selection dialog now has a button for opening the icons folder.
MultiMC now has a shinier, updated logo.
GH-2150: Custom commands have been split from the java settings into a new page.
The use of variables in custom commands is now better documented.
The label shows that they need to be prefixed by $.
Player name is no longer censored in logs.
MultiMC now probes the system for the name of the linux distribution as part of analytics. This will be used to focus future packaging efforts.
Secret cheat code has been added... What does it do?
VisualVM integration now works when VisualVM is bundled inside the MultiMC folder (uses a relative path).
When reinstalling a component, or changing a component version, the custom version is now removed first.
GH-2134: Fix multiple issues with the skin upload:
file:// URL scheme, it will now work correctly.GH-2143: Mojang services status display now reflects the current set of services.
GH-2154: MultiMC now ignores the hidden flag of instance folders and they should show up correctly.
When migrating Legacy instances, custom minecraft.jar will be preserved.
This is a release mostly aimed at getting all the small changes and fixes out of the door.
Local libraries are only loaded from inside the instances now.
Before, MultiMC allowed loading local libraries from the main libraries folder.
This in turn allowed existence of instances which could not be transported from one installation of MultiMC to another.
GH-2475: A bug that allowed the launch to continue with missing local libraries has also been fixed.
Effectively, you will get errors from launching such instances. You can fix the errors by copying the libraries to the locations indicated in the error log.
FTB import now has support for third party modpack codes.
Better late than never?
Instance creation can now be interrupted / aborted.
GH-2053: You can now inspect and change the servers.dat file from MultiMC.
MultiMC now uses the https protocol for many more network requests.
GH-2352: There is now a button to open the .minecraft folder inside the selected instance.
GH-2232: MultiMC can now use .gif icons (not animated).
GH-2101: Instance renaming is now done inline, in the actual instance list.
GH-2452: When deleting a group, MultiMC asks for confirmation.
GH-1552: PermGen is no longer shown when it's not appropriate (java 8 and up).
GH-2144: When changing versions of a component like Forge, the current version is marked with (installed).
GH-2374: World list has been improved:
GH-2384: When installing a mod, existing mod with the same file name will be replaced.
The background cat sometimes wears a silly hat.
GH-2252: Fixed odd drag and drop behaviour on Windows
Drag and drop of URLs from a browser locked up the browser. This needs further fixes on macOS.
Instance naming fixes:
GH-2412: MultiMC no longer leaves behind zombie processes after launch on linux.
GH-2382: Version filter for the forge/liteloader version lists was not matching the whole version name.
GH-2488: More issues with broken relative URL redirection in Qt have been fixed.
Some memory leaks of downloaded data have been fixed.
MultiMC now handles instance groups and instance group saving better.
Long deleted groups no longer persist in the group list.
GH-2467: Broken (and nonsensical) sorting indicators have been removed from the versions page header.
FTB API location has changed
MultiMC now uses the new location and should keep working.
Translations have been overhauled, again
It is now possible to put the translation source .po files into the translations folder and see changes in MultiMC immediately.
The new translation workflow is like this:
.po file from here the translations repository.template.pot and start a new translation based on it.translations folder.When using a .po file, MultiMC logs which strings are missing from the translation on the currently displayed UI screen(s), and which one are marked as fuzzy. This should make it easy to determine what's important.