For the users sakes, I think its acceptable to require the author to at least bump the toc for every major content patch (ie. again at 6.1). Doing that every 6 month shouldn't be too much to ask, and it sends a clear sign that its still working.
You do not have 103 addons with your name on them. I abandoned expansion TOC updates many, many expansions ago. Like I said before, I'd be happy to confirm that my addons are still working before an expansion if that meant you guys didn't mass-mark them as inactive.
Apparently the "Mature" status is intended only for libraries, but I fail to see why any such distinction should be made.
This is what I was trying to say. The lifecycle of libraries and addons is nearly identical:
Alpha, Beta, Release - The addon is under active development, the label indicates stability.
Mature - The addon is no longer under active development, but will receive maintenance updates if it breaks.
Inactive/abandoned - The addon is no longer supported by its developer. Either its functionality is no longer needed, a new addon has taken its place, or the developer has left WoW entirely and did not pass the addon to someone else to maintain.
What is wrong with mature addons? The mass majority of mine are this way. Hell, I have addons that have not been touched since wow 2.0 and work just fine to this day. Those addons are most certainly not abandoned and work perfectly fine, they do not warrant touching the files every 90 days.
Please keep the mature status around, it is very valid. I'll gladly verify that my "mature" addons still work every major patch if you guys drop this crazypants 90 day timer and leave the "mature" state in.
I mean, hell, sometimes wow doesn't even get a patch every 90 days!
Does curseforge have an endpoint I could point a webhook to? If there was such a thing, I'd set my github repos up to hit that and then curseforge could just pull from the repo and package from that.
I'm with Nevvy, it's rare for you to *need* to load properly in combat, so if you do you should be taking extra steps to ensure that works in the first place. Using both delayed and combat triggers will probably cover you, then if you log in mid-combat it loads immediately, otherwise it loads delayed.
Uhm, why are you loading addons this way in the first place. Declare proper deps in your TOC and the system will load the addons for you automatically.
In short, use pairs unless you care about reading an array-like table *in order*, then use ipairs. Use the `for i=1,#t do` loops only when performance matters (OnUpdates that aren't throttled).
0
You do not have 103 addons with your name on them. I abandoned expansion TOC updates many, many expansions ago. Like I said before, I'd be happy to confirm that my addons are still working before an expansion if that meant you guys didn't mass-mark them as inactive.
0
This is what I was trying to say. The lifecycle of libraries and addons is nearly identical:
Alpha, Beta, Release - The addon is under active development, the label indicates stability.
Mature - The addon is no longer under active development, but will receive maintenance updates if it breaks.
Inactive/abandoned - The addon is no longer supported by its developer. Either its functionality is no longer needed, a new addon has taken its place, or the developer has left WoW entirely and did not pass the addon to someone else to maintain.
0
Please keep the mature status around, it is very valid. I'll gladly verify that my "mature" addons still work every major patch if you guys drop this crazypants 90 day timer and leave the "mature" state in.
I mean, hell, sometimes wow doesn't even get a patch every 90 days!
0
Does curseforge have an endpoint I could point a webhook to? If there was such a thing, I'd set my github repos up to hit that and then curseforge could just pull from the repo and package from that.
0
The beta/ptr TOC is usually the one they use when they ship.
0
0
Yes.
> Without opening the tradeskill window
Nope, but you can open it, start the crafting, and close it: https://github.com/TekNoLogic/Panda/blob/master/ButtonFactory.lua#L60-L68
0
0
0
0
0
0
0
https://github.com/tekkub/bimbo/blob/master/Bimbo.lua#L83-94
Basically you compare the number of sockets on that specific item against the number of sockets on the basic untouched item.
0