Open
Description
- I searched the issue tracker for other issues covering my case
- This is a Launcher issue. (Usually if you can reproduce it with a fresh instance)
Describe the bug
For certain updates to ATM10, using "Change Modpack Version" breaks the profile. Each time this happens (and this is the third time in the last few months IIRC) I have to create an entirely new profile and manually transfer over my settings/configuration/etc.
To Reproduce
Steps to reproduce the behavior:
- Create a new profile with ATM10 - 2.25.
- Launch it, play a bit, and close it.
- Use "Change Modpack Version" to update the existing profile to 2.26
Expected behavior
Updating works.
Possible solutions
My guess is some component isn't being correctly updated based on the fact that creating a brand new profile on the new version works.
Operating System:
- OS: Windows 10
- Launcher Version: [e.g. v1.1.10]
- And whatever the defaults are for the ATM10 modpack.
Metadata
Metadata
Assignees
Labels
No labels