You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MultiMC Version: 0.6.12-devlop-2055
I've noticed a few inconsistencies when changing instance type in the new instance screen. ( vanilla, import from zip, ... )
When switching to (ATLauncher / FTB / Technic) pack selection after previously selecting a pack I've observed the following:
The OK button state is not updated
The pack icon fails to update properly, defaults to multimc icon or stays same if switching from Curseforge / FTB Legacy, also stays the same when switching from FTB to ATLauncher.
Steps to reproduce
Add Instance.
Select FTB and select any pack, so that OK button is enabled.
Change to any other install type, e.g. FTB Legacy. (2)
Change back to FTB.
OK button is disabled. (1) Icon is now MultiMC icon. (2)
Select a different pack such that the instance icon updates.
Switch to ATLauncher.
Instance Icon is still the FTB pack icon. (2)
Suspected cause
Not sure however these issues don't seem to affect Curseforge or FTB Legacy so I would refer to them.
This issue is unique
I have searched the issue tracker and did not find an issue describing my bug.
The text was updated successfully, but these errors were encountered:
FixesMultiMCGH-3118FixesMultiMCGH-3720FixesMultiMCGH-3731
Icons and Ok button state will now switch consistently when moving
between tabs. ATLaunchers packlist is now no longer redownloaded
each time you open its Tab. All lists are striped now. And all
search and filter fields now have a placeholder text.
Operating System
Windows
Description of bug
MultiMC Version:
0.6.12-devlop-2055
I've noticed a few inconsistencies when changing instance type in the new instance screen. ( vanilla, import from zip, ... )
When switching to (ATLauncher / FTB / Technic) pack selection after previously selecting a pack I've observed the following:
Steps to reproduce
Suspected cause
Not sure however these issues don't seem to affect Curseforge or FTB Legacy so I would refer to them.
This issue is unique
I have searched the issue tracker and did not find an issue describing my bug.
The text was updated successfully, but these errors were encountered: