Not Issue: Recomendation: Take a look at PackWrap

[Merith-TK]

https://github.com/Merith-TK/packwiz-wrapper/tree/main/cmd/pw

This is a tool i made in golang that wraps around the existing packwiz command, has a few features that I would reccomend taking a look at for inspiration,

A few of the ones I would reccomend looking at is reinstall.go, which I find useful when changing modloader or mc versions as it can reinstall the entire list and remove ones that dont port directly (which if you use git to track, makes it easy to tell which ones dont have support or have alternatives)

packwiz.go is just my handler for wrapping around packwiz, and its toml formats

modlist.go generates a modlist that can be helpful for people who dont want to do the modpack and instead want to manually do it (there are weirdos who insist for some reason)

main.go is the entrypoint of the program, just lits the args and the batch mode

import.go is helpful if the user has alot of open tabs and uses a tablist extension to export the tablist to import it en-mass

detectURL.go will attempt to autodetect the public url of the pack.toml file, based off where it was tracked with git.

build.go you might wanna look into for the multimc export option, since i noticed your tool doesnt actually handle that

[AmberIsFrozen]

Thanks, I'll take a look at it at a later date :)

Originally I envisioned PW-GUI to be a GUI for the official packwiz executable itself and nothing more than that, although indeed I also recognize the value of having these features available for a complete modpack authoring exlerience (And if anything we are already doing more than packwiz itself, so it shouldn't be a big problem)

[Merith-TK]

Yep, my tool is meant for a use-case like https://github.com/merith-tk/modpack-template in format, or managing multiple modpacks at once in bulk (hence the batch command function)

[AmberIsFrozen]

I've implemented a mod list generation
As for reinstalling, I didn't implement it 1:1 as that would reset any user-configured metadata (e.g. description, optional), but rather:

• Perform a regular update
• Find unchanged mods
• Try installing each unchanged mods to a temp directory
• • If it succeeds, then that unchanged mod supports our new minecraft version
• • Otherwise, that mod is incompatible with our new version
    Follow up dialog will be shown regarding the incompatible mods.
    Not ideal (And takes slightly longer), but I think it's the best we can do at the moment

Could you elaborate more on the MultiMC export option?

[Merith-TK]

So multimc requires three items at the root of the zip file
.minecraft/, this is where the minecraft files are, including the packwiz jar
instance.cfg, this is the basic "configs" for the instance, such as the instance type, its name, icon, wether or not it has custom commands and what they are,

[General]
InstanceType=OneSix
iconKey={ICONNAME}_icon
name=Modpack Template
OverrideCommands=true
PreLaunchCommand="$INST_JAVA" -jar packwiz-installer-bootstrap.jar {PACKURL}

and then mmc-pack.json

{
    "components": [
        {
            "uid": "net.minecraft",
            "version": "1.21.3"
        },
        {
            "uid": "org.lwjgl3",
            "version": "3.2.2"
        },
        {
            "uid": "net.fabricmc.fabric-loader",
            "version": "0.16.9"
        }
    ],
    "formatVersion": 1
}

edits:

the "reinstall" function of packwrap was meant to be the "well everything is fucked, start from scratch" feature, such as when transitioning between major minecraft versions or modloaders,