Authors CurseForge

We'll need a guide or something, I'm sure it will be asked a lot.

To my understanding:
1) Switch from WITHOUT Externals to WITH Externals
2) Delete all External/Libs folders
3) Let Curse Client do its thing upon first use

I got it correct?

Another question, when I tested it a few days ago, it only detected a few of the Add-Ons I have installed, not even close to half.

Secondly, the Curse Client will be downloading from the Curse Add-Ons page and not on WoWAce/CurseForge repository right?

Third, what if we want to download from the repository, bleeding edge and not on the Curse Add-On page which is 'released' quality?

Quote from Laibcoms

1) Switch from WITHOUT Externals to WITH Externals
2) Delete all External/Libs folders
3) Let Curse Client do its thing upon first use

At the moment we are all offered a premium subscription trial which results in the updater automatically downloading updates for all addons. If you "let Curse Client do its thing" it will guess at what addons you have installed and update them to the newest available addon at Curse which matches the guess. This results in addons being 'upgraded' a few years into the past and some changed into completely different addons like Panda being changed from this to this in my case.
There are a lot of workarounds but they only work if you don't do as I did and just accept the scan. I guess the easiest solution is to not allow CC to do the scan.

I think in order for it to work properly, the current cc system of using the date as version will have to change. So that it checks for the real version of the addon(as set by the author). If a newer version is found it can be updated. If an older(yes, curse has alot of old versions) or current version is found, it will not update.

Hmm, still looks the best course of action is to hold of on using CC until it is actually declared ready for "prime time". Remember CC is still beta. Let's repeat that again:

The Curse Client is still Beta

kolie and Co. will let us know when pulling from CurseForge/WoWAce is built in and ready. I did read sometime back on the old WoWAce forums where the Curse admins are going to be having a big "housecleaning" to get rid of all the old detritus. When they do start that, its going to take a while as Curse does have 2-3 years worth of mods to clear out.

The authors will have to make sure to add proper metadata into the mod then ;)

The client will need a major rewrite in my opinion.. even the latest beta is crap.

And don't you dare use a MAC, a client supported by Blizzard.

It's been less than 16 hours and I already miss being able to run my wowace.py script that I used to sync my addons. I also lose the ability to keep my mods organized accurately, as I refused to let externals into my mods (I want 1 copy of a library on my disk, not 20 that have to be loaded than unloaded as the game starts).

Guess the good ole days are gone, I'm not even sure where to go from here. I definitely am not going to pay to be able to do 1 click updating, heck I don't even want to do a click. *sigh*

But hey we're all better off for this change right?

Quote from zaphon

And don't you dare use a MAC, a client supported by Blizzard.

It's been less than 16 hours and I already miss being able to run my wowace.py script that I used to sync my addons. I also lose the ability to keep my mods organized accurately, as I refused to let externals into my mods (I want 1 copy of a library on my disk, not 20 that have to be loaded than unloaded as the game starts).

Guess the good ole days are gone, I'm not even sure where to go from here. I definitely am not going to pay to be able to do 1 click updating, heck I don't even want to do a click. *sigh*

But hey we're all better off for this change right?

I'm sorry you and I don't have a functioning updater and that we'll have to pay to update unless we want to use multiple clicks. At least we don't have to Wowace to keep their old servers up and running.

I hope we get to see the mac client very soon so that we can start playing with it. I hate running embedded, but that is what I'm currently doing (during the transition).

No question about being "beta", that is not a problem at all (at least for me, I test bleeding edge addons myself), but it is a week, two, or three away to Patch 3.0.2, and so far, as testing in PTR goes, only 1 out of 10 addons will work (and that isn't "properly" to begin with).

So, my main concern is and I believe all the others as well, how to update properly?

I agree, when I tested it, it pulled old versions of certain addons, or it pulled unofficial modifications.


Okay, so, with all the replies, it is evident that we have to go back to manual downloading then?

My follow question will be, when we download via the new WoWAce Projects page or CurseForge, the LIBs are embedded right? (Sorry, I'm confused with what I'm reading about authors should not include the libs or something.)

Again, Beta or Bleeding Edge is not a problem for me, in fact, I prefer those than the ones found in Curse.com (I don't use it actually, I use wowinterface.com :p )

Just a quick note guys, files from wowace won't appear in the CC until tomorrow afternoon.

Quote from zaphon

It's been less than 16 hours and I already miss being able to run my wowace.py script that I used to sync my addons......

The Historian by Elizabeth Kostova is a pretty good read.

I always use times like this as an opportunity to start from scratch.

Quote from Kaelten

Just a quick note guys, files from wowace won't appear in the CC until tomorrow afternoon.

Thanks for the update.

Quote from lindalas

I hate running embedded, but that is what I'm currently doing (during the transition).

Quote from ArcadianDelSol

I always use times like this as an opportunity to start from scratch.

Yeah, I've been building a new UI from scratch on my beta client, made up of WotLK-tagged addons on wowinterface and a few Ace3 addons from wowace whose changelogs showed beta support.

I'm running embedded on beta because it makes it easier to swap in new versions of addons and enable/disable them. Surpisingly, it seems to load damn fast - either it's because I'm running fewer addons, or because Blizz optimized addon load times somehow.

I'll pray for the latter Hunter :P

Due to the fact that the Curse Client still auto-matches similarly named addons without user confirmation, I won't be using it. I use enough addons that aren't hosted on WowAce/Curse -- and indeed already had the client overwrite one addon with something else that hadn't been updated since well before the Burning Crusade expansion -- that I'm not interested in saving a few minutes by using the client, only to discover in the middle of a boss fight that the addon I thought I had was suddenly gone and replaced by something totally useless.

Quote from Phanx

Due to the fact that the Curse Client still auto-matches similarly named addons without user confirmation, I won't be using it. I use enough addons that aren't hosted on WowAce/Curse -- and indeed already had the client overwrite one addon with something else that hadn't been updated since well before the Burning Crusade expansion -- that I'm not interested in saving a few minutes by using the client, only to discover in the middle of a boss fight that the addon I thought I had was suddenly gone and replaced by something totally useless.

Ugh! I thought that got fixed :( That issue is what has kept me from trying it for months now.

Will that still be like that after all the files from here get transferred?

What addon is it getting wrong?

Panda. Basically addons from different sites, that have an addon with a different function but the same name from curse.