-
Notifications
You must be signed in to change notification settings - Fork 13
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
Modpacks #4
Comments
Plan for implementationCreating/Editing the packWhen create pack is pressed ask for pack name and description. Then copy the Mods folder and paste it in the Managed folder and rename it to PackName. Then get the mods in PackName and add it to Loading the packTo load the pack, Scarab will replace the current mods folder with the Pack folder and then do the required steps to make it match with Sharing the packTo share the pack, there will be a button in the pack list that when pressed will use the Manual SharingSince catbox and pastebin don't have usability garuntees (because they are free) there will be an option for manual sharing which will just just zip the pack folder and ask where to save it. Then user can manually share it and the other user can press import pack and install it UIInitial UI design idea: https://www.figma.com/community/file/1251576832566083349 Basic UI Requirements are:
|
I suppose the mods that are in modlinks and aren't prevented from auto-updaing could be stored as simply a list (probably .json) of names rather than copying the whole thing |
Yea that was thought of initially but what then came up is it shouldn't be a task to change a modpack. Copying the folder locally regardless if it wants to be fixed version or not would greatly improve pack changing speed |
TODO
The text was updated successfully, but these errors were encountered: