Prism Launcher Release 7.1, now available
releaseHello!
This is a smaller release, with mostly bug fixes. There are also some minor improvements, like an easier way to open the launcher's data directory, and allowing users to edit instance settings even while an instance is running.
There is also an important fix for the .mrpack export on Windows. Previously, the launcher would bundle all mods into the final modpack ZIP. Now the launcher will correctly bundle the metadata instead. This bug caused trouble at Modrinth as people started uploading these modpacks there. We are very sorry for this bug and hope to catch these kinds of issues through our testing initiative on our Discord server.
Until next time!
Changelog
Added
- Add icons to export menu items by @leo78913 in #1162
- Add the launcher root folder to the Folders menu by @RedsonBr140 and @Scrumplex in #1063
- Higlight installed mods in download dialog by @Trial97 in #1135
Changed
- Don't hide the settings tab when an instance is running by @RedsonBr140 and @TheKodeToad in #1067
- Exclude
.git
directory from the source code tarball by @guihkx in #1140 - Make Konami Code a bit more obvious by @TayouVR in #1151
- Store logs in seperate directory by @Trial97 and @chmodsayshello in #1099
Fixed
- Fix error message about JavaVendor by @Scrumplex in #1195
- Fix parsing of settings file by @Trial97 in #1174 #1192
- Fix some crashes regarding high network usage by @Trial97 in #1145
- Fix trailing space in instance name by @TheKodeToad in #1198
- [Linux] Fix devShell for Nix users by @getchoo in #1159
- [Windows] Fix mrpack export bundling all mods by @TheKodeToad in #1166
Full Changelog: https://github.com/PrismLauncher/PrismLauncher/compare/7.0...7.1
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.