Well there have been changes to that functionality
* It no longer reinstalls the addon when it first discovers it
* You can disable the auto detection feature entirely, even before it runs once.
* It no longer offers to match things that are not exact matches
We also have more planned to help ensure accurate and truthfull matchings.
I don't want to disable auto-detection. I don't want to wade through thousands of addons to find the one I have installed, for the ~150 addons I have installed. The majority of the auto-matches will be correct. I just want the client to pop up the "accept this match" dialog that it already pops up when there are multiple possible matches, when there is only one possible match. I don't understand why that's such an impossible request.
Without TOC scanning, there is simply no way that the client can know that the "Panda" I have installed is or is not the "Panda" that's hosted on Curse. In this case I have no idea what the Curse "Panda" does, but it's not the addon by Tekkub.
I have to agree with Phanx on this one. The current CC beta is a total epic fail, an unmitigated disaster. I have over 150 addons as well, and it blindly replaced a bunch of them without asking me, with completely different addons or versions that were so old as to be useless. And I had absolutely no indication that this was happening, so out of my 150-200 addon folders, I had zero idea which ones were now screwed up. A large majority of my addons are Ace, so I hope that when those get turned on the updater will function much better. But prior to that, it's a disaster.
And yes -- it did ask me to confirm several addons -- several of which did not include the correct addon in the list. But it's the ones that did not get asked about that killed me. This was all yesterday.
So... it doesn't prompt now even when there are multiple possible choices? That's an even bigger problem, as the addons it did prompt me for frequently had something other than the correct match listed first. Given that prompting only occurs on first run, I can't see how "it's spammy" is a valid complaint. :confused:
No, it doesn't try to match them, I don't think its a valid solution either personally. I really think that long term we need a more accurate matching scheme.
My thoughts are to add some identifiers to the change log file, similar to how we did on the old wowace, that'd allow us to know for sure where the file came from.
My thoughts are to add some identifiers to the change log file, similar to how we did on the old wowace, that'd allow us to know for sure where the file came from.
No, it doesn't try to match them, I don't think its a valid solution either personally. I really think that long term we need a more accurate matching scheme.
My thoughts are to add some identifiers to the change log file, similar to how we did on the old wowace, that'd allow us to know for sure where the file came from.
Well, here are my thoughts on this:
Matching only needs to occur the first time you run the client, and it needs to figure out how to handle all preexisting addons.
At this point, there wouldn't necessarily be any identifiers for the client to use. There certainly wouldn't be anything in the changelog file if the addon had been downloaded from another site.
For people who use more than a dozen addons, going through the thousands of available addons to match each addon by hand just sounds like an unnecessarily tedious requirement.
Once an addon is known to the client, there shouldn't really ever be a need for the client to re-match it to a Curse source.
Hmm... as it appears, there is a huge clash between WoWAce users and Curse users.
The WoWAce community wants this (and that includes me :p ) but the Cuser users do not want that.
Maybe WAU should be re-designed to pull from the new WoWAce and/or CurseForge for the daring (like me) who prefers beta and bleeding edge addons, and for the rest, the Curse Client so they get the release quality addons?
Anyway, just a solution to the "can't please everybody", coz, as it appears, you are trying to convince two totally different and oppossing communities to use one client. If it goes down that path, one community must die lest the client becomes just a dream, it'll forever stay in SVN/CVS/GIT/Alpha/Beta etc.
And obviously, the Curse Community is given priority and more favor here, since the WoWAce community is now kinda "saved" by them. If they pull the plug, then we're dead, and I believe many WoWAce'ers are praying for some miracle that some rich guy or company out there will sponsor WoWAce so we can go back to the usual way ;)
Now of course, please don't be mistaken, "most" of us perfectly understood why things must be this way. All we can do is offer ideas and possible solutions.
With that said, I guess, back to manual downloading :p
PS
Could you add a "subsciption page" where all the projects we subscribed to shows up. I think I posted it as a ticket in CurseForge :p It will be very helpful.
Thanks a bunch. All I can offer right now, is prayers
I understand your concerns, and I'm actively working within curse to get things to a happy median. I see no reason why we can't have it work out of the box with the standard features for your average user and then have advanced options that we can tweak to make it into our little bitch... erm make it behave how we want it to.
It's just going to take time guys. I apologize that there is still so much to do. But rest assured, we ARE making progress.
No problem with that ^_^ As I've said, it is understandable. It will does take time. But hey, that's good hope, if the WoWAce Community can influence the Curse Client ;)
But don't go beyond to "protect" (for the lack of word) the WoWAce Community, you are working for Curse and we are getting their support for free (or cheap for those who will get the premium). Been there, done that, have to give in sooner or later.....
Or just develop a little UI management software for just handling versions check, clean save variables etc. Which provides the missing features of CC that WAU already have for years. While manual download won't be a big problem if we do exactly know which UI need upgrading with a glance.
And dealing with standalone lib, it would be solved if the software can scan our addon folder for identical folder and then delete them.
I understand your concerns, and I'm actively working within curse to get things to a happy median. I see no reason why we can't have it work out of the box with the standard features for your average user and then have advanced options that we can tweak to make it into our little bitch... erm make it behave how we want it to.
It's just going to take time guys. I apologize that there is still so much to do. But rest assured, we ARE making progress.
Sorry, but as much as I'm grateful for all the work you did in the past, I'm also very angry for the step BEHIND you're doing now.
- Premium account ? WTF is that, the door to pay to update addons that are done for FREE ?
- Externals: That was the FIRST thing to do. It's not an advanced setup. It's the way we can avoid old mods screwing new with outdated libraries.
- WoW addons on Curse are damn outdated. "syndicated by curse" means children-safe stuff, but also unacceptable delays. Btw, I've seen so many crap on curse that I hardly believe they can syndicate anything for real. Anyway, childrens doesn't use addons anyway.
- Curse addon is overbloated, MacOS version is still nowhere close to be a public beta (is there a public beta? No), and last but not least Curse updater is SLOW as molassa. Old JWoWUpdater was lightning fast.
Sorry, this is my 3rd post here and there (on curse and here too) saying the same, old stuff. I'm really disappointed, expecially with the patch knocking at our doors. Exactly when we needed rock-solid addon updating.
Could we have a sticky thread with announcements and changelogs for when new versions of the beta client are out? What is the latest version anyhow? 2.0.0.13?
No, it doesn't try to match them, I don't think its a valid solution either personally. I really think that long term we need a more accurate matching scheme.
My thoughts are to add some identifiers to the change log file, similar to how we did on the old wowace, that'd allow us to know for sure where the file came from.
Trying to match is going to always be problematic. A much simpler approach is to take advantage of the "Favorites" feature already present. Tying the client to Favorites removes all ambiguity.
Once that happens you are free to put the matching in a menu choice called: "Find existing addons..." which would locate addons not in the favorites list (and also not marked for ignoring) and allow the user to add them to their favorites list.
It's so blindingly simple, that we've all missed it.
- WoW addons on Curse are damn outdated. "syndicated by curse" means children-safe stuff, but also unacceptable delays. Btw, I've seen so many crap on curse that I hardly believe they can syndicate anything for real. Anyway, childrens doesn't use addons anyway.
- Curse addon is overbloated, MacOS version is still nowhere close to be a public beta (is there a public beta? No), and last but not least Curse updater is SLOW as molassa. Old JWoWUpdater was lightning fast.
Mac is in public beta, and I've not really noticed any speed issues. Any specific issues ?
Sorry, this is my 3rd post here and there (on curse and here too) saying the same, old stuff. I'm really disappointed, expecially with the patch knocking at our doors. Exactly when we needed rock-solid addon updating.
Sorry, but I'm totally disappointed.
We are working to fix issues man. Trust me when I say that we want the absolute best product possible.
Trying to match is going to always be problematic. A much simpler approach is to take advantage of the "Favorites" feature already present. Tying the client to Favorites removes all ambiguity.
Once that happens you are free to put the matching in a menu choice called: "Find existing addons..." which would locate addons not in the favorites list (and also not marked for ignoring) and allow the user to add them to their favorites list.
It's so blindingly simple, that we've all missed it.
favorites is an option. we're definately wanting to fix the problem overall though.
I think we've been making massive headway the last week.
* It no longer reinstalls the addon when it first discovers it
* You can disable the auto detection feature entirely, even before it runs once.
* It no longer offers to match things that are not exact matches
We also have more planned to help ensure accurate and truthfull matchings.
Without TOC scanning, there is simply no way that the client can know that the "Panda" I have installed is or is not the "Panda" that's hosted on Curse. In this case I have no idea what the Curse "Panda" does, but it's not the addon by Tekkub.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd yes -- it did ask me to confirm several addons -- several of which did not include the correct addon in the list. But it's the ones that did not get asked about that killed me. This was all yesterday.
Many people complained that the client would even spam them for multiple choices, so we had to disable it all togathar. :(
Do know however that we do understand your opinions on this.
My thoughts are to add some identifiers to the change log file, similar to how we did on the old wowace, that'd allow us to know for sure where the file came from.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorMD5 hash?
Well, here are my thoughts on this:
Matching only needs to occur the first time you run the client, and it needs to figure out how to handle all preexisting addons.
At this point, there wouldn't necessarily be any identifiers for the client to use. There certainly wouldn't be anything in the changelog file if the addon had been downloaded from another site.
For people who use more than a dozen addons, going through the thousands of available addons to match each addon by hand just sounds like an unnecessarily tedious requirement.
Once an addon is known to the client, there shouldn't really ever be a need for the client to re-match it to a Curse source.
The WoWAce community wants this (and that includes me :p ) but the Cuser users do not want that.
Maybe WAU should be re-designed to pull from the new WoWAce and/or CurseForge for the daring (like me) who prefers beta and bleeding edge addons, and for the rest, the Curse Client so they get the release quality addons?
Anyway, just a solution to the "can't please everybody", coz, as it appears, you are trying to convince two totally different and oppossing communities to use one client. If it goes down that path, one community must die lest the client becomes just a dream, it'll forever stay in SVN/CVS/GIT/Alpha/Beta etc.
And obviously, the Curse Community is given priority and more favor here, since the WoWAce community is now kinda "saved" by them. If they pull the plug, then we're dead, and I believe many WoWAce'ers are praying for some miracle that some rich guy or company out there will sponsor WoWAce so we can go back to the usual way ;)
Now of course, please don't be mistaken, "most" of us perfectly understood why things must be this way. All we can do is offer ideas and possible solutions.
With that said, I guess, back to manual downloading :p
PS
Could you add a "subsciption page" where all the projects we subscribed to shows up. I think I posted it as a ticket in CurseForge :p It will be very helpful.
Thanks a bunch. All I can offer right now, is prayers
It's just going to take time guys. I apologize that there is still so much to do. But rest assured, we ARE making progress.
But don't go beyond to "protect" (for the lack of word) the WoWAce Community, you are working for Curse and we are getting their support for free (or cheap for those who will get the premium). Been there, done that, have to give in sooner or later.....
And dealing with standalone lib, it would be solved if the software can scan our addon folder for identical folder and then delete them.
Sorry, but as much as I'm grateful for all the work you did in the past, I'm also very angry for the step BEHIND you're doing now.
- Premium account ? WTF is that, the door to pay to update addons that are done for FREE ?
- Externals: That was the FIRST thing to do. It's not an advanced setup. It's the way we can avoid old mods screwing new with outdated libraries.
- WoW addons on Curse are damn outdated. "syndicated by curse" means children-safe stuff, but also unacceptable delays. Btw, I've seen so many crap on curse that I hardly believe they can syndicate anything for real. Anyway, childrens doesn't use addons anyway.
- Curse addon is overbloated, MacOS version is still nowhere close to be a public beta (is there a public beta? No), and last but not least Curse updater is SLOW as molassa. Old JWoWUpdater was lightning fast.
Sorry, this is my 3rd post here and there (on curse and here too) saying the same, old stuff. I'm really disappointed, expecially with the patch knocking at our doors. Exactly when we needed rock-solid addon updating.
Sorry, but I'm totally disappointed.
Trying to match is going to always be problematic. A much simpler approach is to take advantage of the "Favorites" feature already present. Tying the client to Favorites removes all ambiguity.
Once that happens you are free to put the matching in a menu choice called: "Find existing addons..." which would locate addons not in the favorites list (and also not marked for ignoring) and allow the user to add them to their favorites list.
It's so blindingly simple, that we've all missed it.
No its paying for the bandwith that updating them uses.
No, it is an advanced option. The majority of WAU's 500k+ userbase doesn't use it.
I think you'll find this being rapidly fixed.
Mac is in public beta, and I've not really noticed any speed issues. Any specific issues ?
We are working to fix issues man. Trust me when I say that we want the absolute best product possible.
favorites is an option. we're definately wanting to fix the problem overall though.
I think we've been making massive headway the last week.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorIt sounded to me like he was referring to the old Curse client. I tried it last year for approximately 2 hours.