Twitch App WoW Dependencies
I'm seeing a number of issues related to World of Warcraft addons and the dependencies as they are handled by the Twitch app. I wanted to start by opening the issue on the Curseforge side and go from there:
Please review my projects - I have a number of them all with the word "TomCat's" in the name.
In particular, one addon named "TomCat's Tours: Complete" intends to allow some of my more loyal end users to be able to have all of the TomCat's Tours addons installed and kept up to date without having to look for new addons all the time. TomCat's Tours: Complete lists all of the other TomCat's Tours addons as dependencies via the curseforge dependencies system. Unfortunately things are broken.
User starts with no addons installed
User installs TomCat's Tours: Complete via Twitch.
All other TomCat's Tours addons are then automatically installed with it.
The end user sets TomCat's Tours: Complete to be updated automatically. Their global automatic update is off.
I provide an update to one of the other addons (variant scenario 1), optionally also an update to TomCat's Tours: Complete (variant scenario 2).
In variant 1, the addon I provided an update for is not automatically downloaded, but some users might have expected that dependencies are automatically kept up to date if the addon that depends on them is set to automatically update. This may seem subjective, but if users newly downloading TomCat's Tours: Complete would get the latest version of the dependency, users on autoupdate for TomCat's Tours: Complete should get the dependency updated.
In variant 2, when TomCat's Tours: Complete automatically updates, its dependency is not updated, not even if the update to the dependency was published first.
Additional note: If the user does not have any autoupdate set, manually clicking update for TomCat's Tours: Complete also will not provide for the latest version of the dependencies to be installed unless there was no version of the dependency installed. In other words, it will accept an outdated/old version and not update it.
Second set of issues - relates to removing/deleting the addons:
Assuming the user has all of the TomCat's Tours addons installed via TomCat's Tours: Complete, there are different behaviors depending on which method the user uses to remove the addons.
Method 1: User right clicks the addon and chooses delete. The user is prompted with a warning about the dependencies being removed. and given a choice if they want to remove them.
Method 2: The user clicks the addon and then clicks the delete button (X) from the top bar. The addon and all of its dependencies are uninstalled without warning.
The flaw in either scenario is that sometimes the user may have installed a dependency separately. Addons which are dependencies for other addons also often have functionality on their own or work with addons that didn't list them as dependencies. Take HandyNotes for example. If a 3rd party author created a HandyNotes plugin (also an addon) and listed HandyNotes as a dependency, the user may be surprised to find HandyNotes missing one day because they meant to only remove the 3rd party plugin. Addons that the user installed separately probably should not be harmed in this way.
Hello, and thank you for taking the time to submit your idea! We are looking into this suggestion internally and will update this page once a final decision has been made. Please add any additional details that you think would be helpful in the comments! We are Listening!