It would be useful to be able to configure packwiz-installer from the GUI, particularly for per-user configuration options (#52 #42), and remembering previous choices the user has made in the UI (#47). In accordance with some WIP pack format reworks, I'm considering putting this in a file under _packwiz/.checkout/vendor/packwiz-installer/, maybe falling back to a global configuration file (both of which can be overridden by arguments passed to the bootstrap).
This would also allow configuration of the download path from the GUI, so a single Prism instance template can be used for all packwiz-installer packs, and in future the Git branch to use could be reconfigured.
It would be useful to be able to configure packwiz-installer from the GUI, particularly for per-user configuration options (#52 #42), and remembering previous choices the user has made in the UI (#47). In accordance with some WIP pack format reworks, I'm considering putting this in a file under
_packwiz/.checkout/vendor/packwiz-installer/
, maybe falling back to a global configuration file (both of which can be overridden by arguments passed to the bootstrap).