Addon Interpretation
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? |
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.
Try out patch 2.2.1 and see if it's any better. |
Here is a screenshot of what Minon is doing with my Macaroon addons -
Minion sits in this state, unchanging. A few things I notice - My main Macaroon addon, Macaroon! itself, does not show on the list. All the Macaroon addons look like they are waiting for Macaroon!, but most are contained in Macaroon: Xtras Macaroon: Extensions is in it's own project. 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. |
Quote:
|
Quote:
|
Quote:
But it does not work for me lol. And those are the same versions as available for download here on WoWI, for those that are available :) |
Quote:
|
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" |
Seems to be happening with other special characters in the .toc tile as well, for instance : "AddonName [<whatever>]".
|
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> Code:
##Hosted-Site-ID-1: wowi:7798 As for Sub Modules or LoD stuff just a simple: Code:
##Parent Addon: <AddonName> |
Quote:
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. |
All times are GMT -6. The time now is 06:34 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI