I can see the Minion has a few issues identifying what addons belong to each folder.
Is there anything that addon devs can put in the TOC file to help the detection process?
Maybe a url to the preffered download site?

And the others (Minimap, Units and News & Info) are working alpha versions not packaged anywhere.

As an author, I myself would not mind if the condition to upload files to projects is that WoWI inject a .toc line so that Minion can better determine where an addon is on WoWI. Others might mind, but it wouldn't hurt to put the question forward to the author community here.

Injecting a .toc line would also help identify if an addon is part of a compilation or not.

I have considered this on several occasions, but I really don't want to force addon authors to have to do things to get it to detect properly.

There are several addons that are hosted across multiple addon hosting sites, or may not host it on wowinterface at all, in which case the minion should not try and find a similar addon hosted here to 'update'/replace it with.

There are several addons that are hosted across multiple addon hosting sites, or may not host it on wowinterface at all, in which case the minion should not try and find a similar addon hosted here to 'update'/replace it with.

Wanted to add something I noticed. The issue I posted seems to affect any addon that has a ":" in it's .toc title. The same thing is happening with Button Facade skins where it indicates "Waiting for ButtonFacade", so it may be a parsing issue.

I also have a series of un-released chat addons (Tungsten) and they all have .toc title entries of "Tungsten: <module name>" and they also indicate they are "Waiting for Tungsten"

TBH i don't see why a unified method can't be adopted. As long as it's not a requirement to have. It would make things simpler on just about every site, as each site must use a UID to identify an addon internally. I think the curse/ace-Forge packager does this already.

Something as simple as:

Code:

##Hosted-Site-ID: <Site> : <ID>

Is all it would really take, and it's not like this is going to change often if at all. IE in my own addon "Sick Of Clicking Dailies" all i'd have to add to the toc is 2 fairly static lines.

That way the toc file for the submodules reference the parent addon that it belongs to (Distributed package wise). For addons that are modules of another but are not explicitly packaged with it won't use this. Like Grid Modules, a lot are not part of the proper Grid addon, but follow it's naming method, these packages would not use this. But Grid's naturally packaged LoD Modules would.

TBH i don't see why a unified method can't be adopted. As long as it's not a requirement to have. It would make things simpler on just about every site, as each site must use a UID to identify an addon internally. I think the curse/ace-Forge packager does this already.

I agree with this.
If the updaters supported it I would quickly throw an extra few lines in my addons if it meant better detection and less false-positives.