PolyMC Update 1.4.2, now available
releaseIt has been a while.
With this wonderful new version you get many cool things, like bug fixes and also bug fixes!
If you were building PolyMC yourself, make sure your compiler supports C++17, as it is a requirement from now on.
Thanks to all contributors, who have worked on this release!
Changelog
Added
- [OpenBSD] Add root path detection by @Scrumplex in #1019
Changed
- Bump to C++17 by @Scrumplex and @LennyMcLennington in #941
- Hide 'More news...' button if the news aren't loaded yet by @flowln in #1049
- Make 'About' dialog smaller by @DioEgizio in #1107
- Make Coremods / Mods separation more clear by @Scrumplex in #1035
- Update copyright notices by @DioEgizio in #1073
- [macOS] Downgrade to Qt 6.3.0 by @DioEgizio in #1014
Fixed
- Allow user to interrupt launch after 3 tries by @Scrumplex in #1018
- Cleanup old mod metadata by @flowln in #1017 #1044
- Disable "Check for Updates" while the game is running or if all mods are removed by @Gingeh in #1007
- Fix crashes in mod updater by @flowln in #965
- Fix errors when extracting some modpacks by @flowln in #1095
- Fix major version filter in mod downloader by @flowln in #997 #1118
- Fix some icon cache problems by @flowln in #920 #1080
- Fix UTF-8 decoding in log by @magneticflux- in #968
- Make world safety nag popup title text match the action by @budak7273 in #1039
- Make URLs in the FTB Legacy browser clickable by @DioEgizio in #1087
- [Linux] Implement workaround for Ubuntu 22.04 OpenSSL issues by @DioEgizio in #1006
- [Linux] Update AppStream info by @DioEgizio in #1058
Full Changelog: https://github.com/PolyMC/PolyMC/compare/1.4.1...1.4.2
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.