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
I have a modlist with some disabled due to the lack of a suitable version for the time being.
Suggestion
Remove the mechanism where mods do not update when unchecked (disabled)
Benefit
The function that restricts mod updates in that situation is pointless.
This suggestion is unique
I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.
You may use the editor below to elaborate further.
I need to question why this restriction exists in the first place. It is more annoying that when someone initiates mass updates, they are constantly bombarded with a list of "mods cannot be updated when they are disabled". Especially when they are jumbled alongside mods that lack a valid update URL, or mismatch in Minecraft version.
If this is needed, there should be an opt-in parameter where the update mechanism can SILENTLY ignore mods that are not loaded into the instance.
The text was updated successfully, but these errors were encountered:
Role
I have a modlist with some disabled due to the lack of a suitable version for the time being.
Suggestion
Remove the mechanism where mods do not update when unchecked (disabled)
Benefit
The function that restricts mod updates in that situation is pointless.
This suggestion is unique
You may use the editor below to elaborate further.
I need to question why this restriction exists in the first place. It is more annoying that when someone initiates mass updates, they are constantly bombarded with a list of "mods cannot be updated when they are disabled". Especially when they are jumbled alongside mods that lack a valid update URL, or mismatch in Minecraft version.
If this is needed, there should be an opt-in parameter where the update mechanism can SILENTLY ignore mods that are not loaded into the instance.
The text was updated successfully, but these errors were encountered: