Prism Launcher Release 6.2, now available
releaseHello!
This is a small update that fixes some issues, most notably a nasty issue when importing .mrpack file.
Thanks to all contributors!
Changelog
Added
- Make use of logging categories for authentication data logging by @Scrumplex in #684
Changed
- Detect jars from within build folder for development builds by @Ryex in #781
- Improve the reliability of the Task's stack overflow test by @flowln in #804
- Correctly parse metadata from some misbehaving Forge mods by @flowln in #743
- Remove commit hash from builds where git wasn't installed at build time by @getchoo in #666
- Skip some HTML in markdown rendering by @redstrate in #713
- Update application metadata by @AshtakaOOf in #680
- Update copyright notice by @RaptaG in #746
- Use Qt logging facilities instead of our own by @flowln in #665
- [Windows] Let Qt handle dark mode titlebar by @TheLastRar in #726
- [Windows] Update MSVC builds to Qt 6.4.2 by @DioEgizio in #716
Fixed
- Better check file paths in .mrpack import and json components by @flowln and @Scrumplex in #810
- Fix crashes when running a lot of concurrent tasks by @flowln in #758 #784
- Fix importing 1.16+ Forge Technic Launcher packs by @byquanton in #710
- Improve handing of ZLib submodule by @TheLastRar in #772 #779
- [Windows] Fix random ResourceFolderModel test failures on some Windows builds by @flowln in #731
Full Changelog: https://github.com/PrismLauncher/PrismLauncher/compare/6.1...6.2
You can grab the latest download here for your respective platform.
- Next: [SECURITY UPDATE] Prism Launcher Release 6.3, now available
- Previous: Prism Launcher Release 6.1, now available
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.