PolyMC Update 1.4.0, now available
releaseWhoa! There have been a few things since our last feature release almost two months ago!
Major new features include the new mod updater and Qt 6 support.
Don't worry, Qt 5 will still be supported and packages using it will still be available for some time.
If you are a macOS user, you might be delighted to hear, that this will be the first version that ships with an updater!
As a Linux user, you should definitely take a look at the new Performance tab in the settings.
No longer should you need to deal with wrapper commands to enable MangoHud, GameMode or to utilize your dedicated GPU in a hybrid GPU setup.
Thanks to all contributors, who have worked on this release!
Changelog
Added
- Add concurrent tasks by @flowln in #786
- Add more links to mod and modpack descriptions by @flowln and @DioEgizio in #634 #799
- Add news reader in the launcher by @flowln in #845
- Add on-disk mod metadata information by @flowln and @Scrumplex in #426 #714 #716 #759
- Implement mod updater by @flowln in #588
- Preliminary work for modpack updates by @jamierocks in #665
- Qt 6 support by @Scrumplex and @DioEgizio in #575 #902 #911 #922 #936
- [Linux] Add Performance settings (MangoHud, GameMode and PRIME) by @Jan200101 in #707
- [Linux] Add more metadata to Nix package by @TheOPtimal in #930
- [macOS] Implement updater using Sparkle by @kthchew and @Scrumplex in #479
- [OpenBSD] Readd support for OpenBSD by @Technous285 in #694
Changed
- Allow the cape to be changed without changing the skin by @Gingeh in #913
- Cleanup Java code by @Scrumplex and @icelimetea in #778 #785 #800 #863
- Hide channel from version for tagged commits by @Scrumplex in #810
- Improve handling of environment variables by @Scrumplex in #893
- Improve resolving of JARs by @Scrumplex in #794
- Improve the account selection window by @Gingeh and @Scrumplex in #855 #870
- Improve UX in the mod downloader by @flowln in #505
- Improvements for Modrinth/CurseForge modpacks by @flowln in #839
- Improvements around APIs page by @Scrumplex in #678
- Improvements to Windows installer by @kthchew in #788 #797
- Make version labels in About dialog selectable by @jn64 in #812
- Make FTB Classic layout the same as other platforms by @jopejoe1 in #884
- Refactor instance resources pages by @flowln and @Scrumplex in #652
- Refactor tests by @Scrumplex and @DarkKirb in #784 #869
- Replace old reference to launchermeta.mojang.com by @Scrumplex in #830
- Reword CurseForge warning by @DioEgizio in #834
- Separate launch and kill instance actions by @kthchew in #826
- Update license information by @DioEgizio in #905
- [Linux] Cleanup flake.nix by @gytis-ivaskevicius in #881
- [Linux] Rewrite polymc.6 in scdoc by @EliteTK in #847 #901
- [macOS] Build on macOS 12 in CI by @DioEgizio in #787
Fixed
- Always scale mod icons to the right size by @flowln in #818
- Don't censor offline access token by @ivanpu in #864
- Don't create unnecessary folders when extracting ZIPs by @flowln in #817
- Fix broken output in mod list by @flowln in #947
- Fix contrast of placeholder text with dark theme by @flowln in #929
- Fix duplicate name in window title by @jn64 in #811
- Fix hangs when aborting some tasks by @flowln in #831
- Fix missing instance version in status bar by @kthchew in #860
- Fix permanent mod-loaders for some modpacks by @Scrumplex in #880
- Fix "Play Offline" not working when auth servers are partially offline by @Scrumplex in #877
- Fix sorting for Modrinth resources by @DioEgizio in #837
- Fix Technic instances using Forge by @Scrumplex in #890
- Fix translations by @Scrumplex in #917 #938
- Fix warnings reported by LGTM.com by @Scrumplex in #808
- [Linux] Fix mods relying on
libstdc++on Nix by @virchau13 in #904 #934 - [Linux] Use our fork of libnbtplusplus on Nix by @Scrumplex in #932
- [macOS] Workaround Qt bug to fix menu bar separators by @kthchew in #827
Full Changelog: https://github.com/PolyMC/PolyMC/compare/1.3.2...1.4.0
You can grab the latest download here for your respective platform.
Comment Rules
By submitting a comment, you agree to uphold the Prism Launcher Code of Conduct.
✅ What user-contributed comments are for
- Share additional information relevant to the article.
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page, such as tutorials or articles.
- It is allowed to occasionally link to resources you've created. When doing so, you must disclose your affiliation with the resource in some way. However, linking to resources you've created should not represent the majority of your interactions with user notes. Excessive self-promotion is not allowed and will be moderated away.
🚫 What user-contributed comments are not for
- Do not point out something in the documentation being incorrect or outdated.
- Instead, open an issue on the prismlauncher.org issue tracker. If you can, please open a pull request to improve the documentation.
- You can use the Edit button at the bottom of each documentation page for this purpose.
- Do not ask support questions. Please use other community platforms instead.
- Do not submit bug reports. Please use the main Prism Launcher repository's issue tracker instead.
- Do not submit feature requests. Please use the Prism Launcher repository's issue tracker repository instead.
- Do not post off-topic comments. Comments must be strictly related to the page they are linked to.
Comments not following the above rules will be removed.
Licensing of user-contributed comments
Launcher contributors may occasionally go through the comments and may incorporate information from them in the documentation. By submitting a comment, you accept that it may be incorporated in unmodified or modified form in the launcher and/or documentation, subject to the GPL-3.0 license for the launcher and AGPL-3.0 license for the documentation.