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
We should consider using the current wizard import logic for regular modpack imports when using the --custom flag instead of/as alternative to the config files that are in use currently.
Describe the solution you'd like
Allow picking what modifications to import when importing a modpack through the same selection method as the wizard import.
The text was updated successfully, but these errors were encountered:
My suggestion would be to "fake" pages. Maybe with up to 50 on each:
> ffmt -t HUGE.ttmp --custom
Starting import...
Extracting data from testwizard.ttmp2...
Starting wizard...
Name: testwizard
Version: 1.0.0
Author: nova
This is to test multi options in a modpack wizard
The test group
Page: 1 out of 10
Choices:
0 - Nr 1
this is nr 1
1 - Nr 2
and number two
2 - Nr 3
dis be 3
Choose one or multiple (eg: 1 2 3, 0-3, *): 2
Page: 2 out of 10
Choices:
0 - Nr 1
this is nr 1
1 - Nr 2
and number two
2 - Nr 3
dis be 3
Choose one or multiple (eg: 1 2 3, 0-3, *): 2
We should get rid of --custom all together and give a proper option when importing a simple modpack.
> ffmt -t HUGE.ttmp
Starting import...
Extracting data from testwizard.ttmp2...
Simple Modpack detected
Use Wizard?
(Y)es, let me select the mods.
(N)o, import everything.
We should consider using the current wizard import logic for regular modpack imports when using the --custom flag instead of/as alternative to the config files that are in use currently.
Describe the solution you'd like
Allow picking what modifications to import when importing a modpack through the same selection method as the wizard import.
The text was updated successfully, but these errors were encountered: