-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Per Modpack import configuration #213
Comments
IntroThe config file contains:
json may be the logical choice, but I do like the way our global config file is parsed so maybe that would be a cleaner choice. For huge modpacks this will still be a bit clunky, but it feels like a good balance between usability and flexibility. Config generation
This would result in a configuration file being generated after completing normal "import procedures" Config use
a --use-configurationfiles type flag to override --all is also a nice option Scratchpad for command ideas:
|
dry-run is done, next up is saving the information somewhere instead of doing absolutely nothing |
any updates on this btw? or any other method of not needing to reinstall all mods with all options manually? i think in most guides for textools, they just tell you to combine all installed modpacks into one giant modpack which you can then install again |
Thanks for nagging a bit! Truth be told, I recently became a parent and am therefore a bit behind on many things I'd like to do - this is one of them. The other main contributor - @shinnova - is the other parent, so in general FFMT will move at a pretty slow pace when it comes to large changes. With all that said, I've looked a bit at the framework and I wonder if we could throw together a relatively simple "make modpack" command which takes everything you have enabled and makes it a valid modpack for you to later import again, like you mentioned. @shinnova, you are much better versed in the framework than I am, what do you think? Could we throw together a barebones command to make a modpack out of all your imported mods? |
It looks really easy to implement a simple version of modpack creation. I'll make a quick version which will make a modpack out of your currently enabled mods. |
Modpack creation is currently being worked on in #8 If something like this issue is still needed I'd rather cache the previous selection and ask if the user would like to re-use that during wizard import (and with a flag). |
This is now partially resolved with the in https://github.com/fosspill/FFXIV_Modding_Tool/releases/tag/v0.9.10 |
Yes, I also agree that the Dry Run options could be an excellent solution, combined with your idea above of separate configs per-modpack. Big full-wizard modpacks like the Hair Defined would be so much more manageable that way.
Originally posted by @taylor85345 in #212 (comment)
The text was updated successfully, but these errors were encountered: