Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
Shared instances are unreliable, but the only current way to share private modpacks and push updates without making players install/update mods manually. (Difficult for friends who aren't as savvy)
Describe the solution you'd like
Add more control for mrpack exports/shared instances;
-
Export .mrpack as an 'update' instead of a FULL pack, containing only the ADDED or UPDATED mods/files. (Still allows selecting specific files and folders as per current exports)
-
Exporting an 'update' should add, remove or update any mods that have changed since the last export (starting with a mrpack export, and going off of any ".mrupdate" exports after that)
-
Exporting 'push updates' as a manual mrpack file as an option, in case of API failure/errors in 'Push Updates'
-
Could call the files 'my_pack.mrupdate' or similar
-
May need optional 'automatic' version handling based on the exports,
-
a 'namespace' for the pack that doesn't change unlike the title.
-
when a 'mrupdate' is dragged/double clicked, Modrinth will ask 'Which Your_Pack instance would you like to update?' in case of multiple instances.
-
should show what was added, updated and removed, much like shared instances
Basically, just a less API/network reliant private/unpublished modpack update system. There may be better solutions for this (like shared instances not having issues frequently)
Even if shared instances worked flawlessly 99% of the time, it'd be good to have the 'backup' modpack update system in case someone has issues updating an instance
Describe alternatives you've considered
Additional context
No response
Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
Shared instances are unreliable, but the only current way to share private modpacks and push updates without making players install/update mods manually. (Difficult for friends who aren't as savvy)
Describe the solution you'd like
Add more control for mrpack exports/shared instances;
Export .mrpack as an 'update' instead of a FULL pack, containing only the ADDED or UPDATED mods/files. (Still allows selecting specific files and folders as per current exports)
Exporting an 'update' should add, remove or update any mods that have changed since the last export (starting with a mrpack export, and going off of any ".mrupdate" exports after that)
Exporting 'push updates' as a manual mrpack file as an option, in case of API failure/errors in 'Push Updates'
Could call the files 'my_pack.mrupdate' or similar
May need optional 'automatic' version handling based on the exports,
a 'namespace' for the pack that doesn't change unlike the title.
when a 'mrupdate' is dragged/double clicked, Modrinth will ask 'Which Your_Pack instance would you like to update?' in case of multiple instances.
should show what was added, updated and removed, much like shared instances
Basically, just a less API/network reliant private/unpublished modpack update system. There may be better solutions for this (like shared instances not having issues frequently)
Even if shared instances worked flawlessly 99% of the time, it'd be good to have the 'backup' modpack update system in case someone has issues updating an instance
Describe alternatives you've considered
Additional context
No response