Support unsup component when importing prism instances

[MattiDragon]

The Problem

Prism Launcher has a special component when can be used to include Unsup in an instance. Unsup allows for automatic pack updates on startup and is used among other things for in-dev modfest modpacks. Currently ATLauncher ignores this component, requiring users to notice that their pack is empty and manually install unsup.

The Solution

Installing unsup when the com.unascribed.unsup.stable or com.unascribed.unsup.experimental components are present should fix the issue. The installed components can be found in the mmc-pack.json file and their definitions within the patches folder of a Prism export.

Additional Information

You can find an example pack from modfest carnival here: https://github.com/ModFest/modfest-carnival/releases
Make sure to get the ModFest.-.Carnival.zip file. Also note that while the unsup jar is included in the pack, it is not necessary for prism to correctly import the pack.

Have you checked this issue doesn't already exist?

• I am sure this issue doesn't exist already

Code of Conduct

• I agree to follow this project's Code of Conduct

[RyanTheAllmighty]

So got this working, the modfest carnival one was broken and doesn't work even in Prism, so used https://github.com/ModFest/blanketcon-25/releases and that's working correctly and can connect to the server, so assuming everything installed correctly.

Any agents coming from a MultiMC import should work (no other custom components for the moment). This isn't something that's editable from the UI or will exist in an export (even if done for MultiMC format), but should resolve people getting empty packs with it

[atlauncher-bot]

This has been fixed with version 3.4.40.0