So JWoWUpdater is basically toast and using the Curse website to find mods isn't exactly user friendly. Is there a terse listing of links pointing to only ACE-based addons on Curse somewhere?
You're not going to like this, but try deleting all your add-ons (after backing them up) and reinstalling them manually through the Curse Client. This is easy and straightforward, and will ensure it matches up the add-ons you expect. Take this time to also check each add-on to see if the author has updated it for 3.0, because if they haven't, no amount of updater magic will save it. For major WoW version upgrades, this should be everyone's mode of operation anyway.
To be fair to the curse client I attempted this approach. When I first loaded up the client it recognized probably 90% of my addons, which is great by most standards. The problem came when I allowed it to update the addons- suddenly functioning addons with proper deps installed were not functioning because addons that updated were loading, but with a different name/version/something, and Wow.exe was not recognizing the deps.
I figured hey, maybe if I wipe the slate clean and install EVERY mod from scratch and wipe out all the savedvariables the curse client will work like a champ. Wrong. For examples do clean installs of Pitbull, Atlasloot, various fubar plugins, and InFlight. Even from a clean install, these packages aren't functioning with themselves because of something as simple as dependency checking in the wow client.
The sad thing is I only ran WAU once every few months rather than compulsively every time I started WoW. I know Thott used the cosmos updater as a vehicle to upload data so he didn't mind the bandwidth usage, but I never believed in constantly updating since it could easily ruin a nightly play session without warning.
Surely the dev community suggested changes to the development cycle of wowace addons to have code push/version changes bundled into further apart cycles rather than having a fresh version available every time a dev committed code to the trunk. Surely even a nightly snapshot release could have solved a lot of the bandwidth issues? I'm assuming that compression was done before transmission and the wau client handle extracting compressed file, since most of the addons are just plain text?
I guess it's all moot now that the leap has been taken, but honestly the timing was awful. But that was the point, wasn't it? Most users of WAU like myself didn't know this was coming, so our only real option on patch day is this newfangled curse client that still needs issues ironed out, and developers aren't used to yet. Downloading mods individually from web pages has an even more ungodly amount of overhead and wasted time. Curse is usually inaccessible on patch days anyways as history has shown repeatedly over the last who knows how many years. Wgets are even less bandwidth smart than update clients since the file is downloaded regardless of update status :-/
Ironically when I set the WAU to download a mod after it had been decommissioned, it started consuming a fair amount of bandwidth doing auto-retry nonstop. Hopefully that's not going to be an issue for the bottom line operating budget.
This site and forum is for developers/power users, not for the average user - if you are "just" an average user, you should go to Curse/WoWInterface/WoWUI.
I have 2 Problem with this. First I don't think this is old news and most of you developers / power users want it to be true just recently. Second, whatever it is intended to be doesn't matter as long it is isn't used that way. If you want a change, well you can change but that doesn't mean everyone and everything around you will change as well. Your are going to / are pissing a lot of people off.
Btw. This kind of statement should be on the frontpage. Nothing more. Just this statement to clarify who is not welcome here anymore!
Everything else is just halfassed. You don't achieve changes by pretending...
So I love how my recently updated mods via WAU such as Quartz were determined "old" and "updated" with one from Curse dated for MAY. Nice job on the updater :rolleyes:
I have 2 WoW instlalations for different reasons. They both have very different UIs with different mods and such. With the Curse Client (2.0.0.14) if you switch the WoW installation directory and it doesn't refresh the addon list. When you do switch it and try to update your addons it'll install all the ones from the first selected install to the second.
Well, I'm going to try to avoid going over old ground - suffice to say that I'm a long term power-user of Ace addons and quite disenchanted with the change. It's currently a long way from a change for the better from my perspective. I only hope that it doesn't take too long before it at least breaks even with what we have lost.
I'm a Mac user, and had 285 Ace modules installed prior to today, using WUU's SmartUpdate feature to both stay current and minimise bandwidth. I previously had a very high opinion of Ace, despite the perpetual bleeding edge nature of it. I've refrained from commenting so far, as I wanted to see how things were going to play out, but now (on patch day), I find myself in a less than satisfactory position.
At present, the Mac CC 2.0.0.15 really doesn't feel any better than clunky and mediocre. I'm sorry to say that about it, but that's how I feel about it, and I think honesty is far more important than diplomacy in this case. It does nothing to convince me that I should become a paying customer of Curse. That's a bad thing for the community, as I do understand bandwidth costs and the need to try to raise some revenue. First impressions last, and it takes a long time to correct a bad first impression.
Anyway, those are my general thoughts on the change and the current state of things. Here are some specific problems with and suggestions for CC 2.0.0.15 on Mac, as it stands today:
I've started with an empty addons folder for 3.0, as the task of addressing all of the 550 addon modules in my old 2.4 folder was too huge to complete quickly, with essentially no usable assistance from CC (my old install was disembedded / no-exts). Starting from a clean slate was also necessary to eliminate addons which are unlikely to be updated any time soon (such as most of Cosmos :-( ).
The status box text is so small as to be nearly unreadable, and has an alien Windows type minimise button that doesn't gell well with the MacOS desktop. The text size is the main issue, and it's a problem on both my 13", 1280x800 MacBook; and my 24", 1920x1200 iMac.
Starting with an empty Interface/Addons folder in the default location (/Applications/World of Warcraft/Interface/Addons), it didn't install in the correct place - my first installation attempt landed in the main WoW folder.
When fiddling with the "Set WoW Directory" option to try to fix the installation path, it erroneously complained that there was no WoW.exe on the system (it's a Mac, we don't have .exe files).
The lack of version number display in both the "Find an Addon" and "World of Warcraft" tabs is very annoying (it needs to be in the lists, it's not viable to click on each addon to see it when you have hundreds of addons). Similarly, the lack of indication of whether a particular addon is release, beta, or alpha is a bit of a problem.
The TOC interface version number should also be (optionally) displayed in the lists - it can be very useful in determining addons that are possibly stale and in need of attention.
There doesn't seem to be a way to concisely view the available and installed versions (both by status and version number). Over the years, I've frequently had to revert to an older version of an addon when the latest turned out to be bad (including the latest "release" version on Curse in some cases). We need a pull-down list of all available versions, filtered by the global release type preference and per-addon preference.
Disembedded / no-exts / load on demand. This is an essential feature for power users. I appreciate that we may need to wait for 3.0.3 before this is fully viable on the WoW end of things. It minimises download bandwidth, and, more importantly, minimises load time. With hundreds of individual modules, it's a show stopper for this to be missing - the game times out before all the modules can load.
CurseProfiler. At the very least, this should be given the appearance of opt-in, with a popup window announcing its installation, and preferrably requiring users to click (a default) "Yes". I already submit data to both Thottbot and Wowhead, so I'm not completely against such things. What is missing here is the feeling of positive opt-in, and a sales pitch for why I should want to opt-in (the benefit for Thottbot and Wowhead is immediately obvious). This addon is going to be permanently disabled on my systems until it's sold to me as a good thing.
An optional text log file (Unix style with date/timestamps would be ideal) would be extremely useful for tracking what has changed and when. In the event of problems, being able to see something like "Oct 15 12:22:43 update: MegaAdd v1234 (2008/04/01, release) -> MegaAdd v1390 (2008/10/12, beta)" would be extremely useful. This log should grow over time and never be cleared without positive confirmation from the user, building a medium/long-term history of what has been installed/updated/uninstalled.
The lists need to be sortable by clicking on the column headings.
The "Find an Addon" tab needs a way to filter the available addons to only Ace addons, and then allow text search within that sub-set. Ideally, it also needs a one-line (60-80 characters) description of each addon.
Is there a way to update no-externals using the curse updater? I use so many addons that share libraries, when libraries are included inside each addon folder my load times are slooooooooooooooooow. Thanks.
Is there a way to update no-externals using the curse updater? I use so many addons that share libraries, when libraries are included inside each addon folder my load times are slooooooooooooooooow. Thanks.
Is there a way to update no-externals using the curse updater? I use so many addons that share libraries, when libraries are included inside each addon folder my load times are slooooooooooooooooow. Thanks.
Blizzard broke the no-ext mode for addons - it's recommended to running everything with embedded libraries.
Feature Request
Could we please get an option for some sort of "backup" feature within CU, that will move or zip "old" addons before replacing them with the "updated" versions? That way, when CU invariably screws up and overwrites your addons with the wrong version, you'll have something to fall back to?
At this point, I'm sticking with manual updating from the websites, until CU gets made to something that actually works properly (I know, I know... it's beta).
Feature Request
Could we please get an option for some sort of "backup" feature within CU, that will move or zip "old" addons before replacing them with the "updated" versions?
It would seem more logical to determine whether a mod needs updating based on actual version numbers than release date. If someone releases a mod that has problems today, and immediately comes out with a fix, the client won't see that an update is available. The client would have then failed at its job.
Feature Request
Could we please get an option for some sort of "backup" feature within CU, that will move or zip "old" addons before replacing them with the "updated" versions? That way, when CU invariably screws up and overwrites your addons with the wrong version, you'll have something to fall back to?
At this point, I'm sticking with manual updating from the websites, until CU gets made to something that actually works properly (I know, I know... it's beta).
R.I.P. WAU.
I just end up copy/pasting a backup of my interface, WTF, and Log folders to another directory before I do any updating, or at the least, once a week or so. then I've not only got the backups of the addons, but the saved variables the different versions need to work correctly. It works, it's clean and it goes MUCH faster than having a client do it for me would.
I just end up copy/pasting a backup of my interface, WTF, and Log folders to another directory before I do any updating, or at the least, once a week or so. then I've not only got the backups of the addons, but the saved variables the different versions need to work correctly. It works, it's clean and it goes MUCH faster than having a client do it for me would.
A good program (free too!) for this is SyncToy. Microsoft release, can find it from a quick Google or the microsoft.com page. Takes a minute to set up, then it makes it so you can back up your Interface/WTF folders with 2 button clicks and no headache. Been using it for months, works flawlessly.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
To be fair to the curse client I attempted this approach. When I first loaded up the client it recognized probably 90% of my addons, which is great by most standards. The problem came when I allowed it to update the addons- suddenly functioning addons with proper deps installed were not functioning because addons that updated were loading, but with a different name/version/something, and Wow.exe was not recognizing the deps.
I figured hey, maybe if I wipe the slate clean and install EVERY mod from scratch and wipe out all the savedvariables the curse client will work like a champ. Wrong. For examples do clean installs of Pitbull, Atlasloot, various fubar plugins, and InFlight. Even from a clean install, these packages aren't functioning with themselves because of something as simple as dependency checking in the wow client.
The sad thing is I only ran WAU once every few months rather than compulsively every time I started WoW. I know Thott used the cosmos updater as a vehicle to upload data so he didn't mind the bandwidth usage, but I never believed in constantly updating since it could easily ruin a nightly play session without warning.
Surely the dev community suggested changes to the development cycle of wowace addons to have code push/version changes bundled into further apart cycles rather than having a fresh version available every time a dev committed code to the trunk. Surely even a nightly snapshot release could have solved a lot of the bandwidth issues? I'm assuming that compression was done before transmission and the wau client handle extracting compressed file, since most of the addons are just plain text?
I guess it's all moot now that the leap has been taken, but honestly the timing was awful. But that was the point, wasn't it? Most users of WAU like myself didn't know this was coming, so our only real option on patch day is this newfangled curse client that still needs issues ironed out, and developers aren't used to yet. Downloading mods individually from web pages has an even more ungodly amount of overhead and wasted time. Curse is usually inaccessible on patch days anyways as history has shown repeatedly over the last who knows how many years. Wgets are even less bandwidth smart than update clients since the file is downloaded regardless of update status :-/
Ironically when I set the WAU to download a mod after it had been decommissioned, it started consuming a fair amount of bandwidth doing auto-retry nonstop. Hopefully that's not going to be an issue for the bottom line operating budget.
I have 2 Problem with this. First I don't think this is old news and most of you developers / power users want it to be true just recently. Second, whatever it is intended to be doesn't matter as long it is isn't used that way. If you want a change, well you can change but that doesn't mean everyone and everything around you will change as well. Your are going to / are pissing a lot of people off.
Btw. This kind of statement should be on the frontpage. Nothing more. Just this statement to clarify who is not welcome here anymore!
Everything else is just halfassed. You don't achieve changes by pretending...
Errorhandling, please...
(There was only /Interface, not /Interface/AddOns/)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm a Mac user, and had 285 Ace modules installed prior to today, using WUU's SmartUpdate feature to both stay current and minimise bandwidth. I previously had a very high opinion of Ace, despite the perpetual bleeding edge nature of it. I've refrained from commenting so far, as I wanted to see how things were going to play out, but now (on patch day), I find myself in a less than satisfactory position.
At present, the Mac CC 2.0.0.15 really doesn't feel any better than clunky and mediocre. I'm sorry to say that about it, but that's how I feel about it, and I think honesty is far more important than diplomacy in this case. It does nothing to convince me that I should become a paying customer of Curse. That's a bad thing for the community, as I do understand bandwidth costs and the need to try to raise some revenue. First impressions last, and it takes a long time to correct a bad first impression.
Anyway, those are my general thoughts on the change and the current state of things. Here are some specific problems with and suggestions for CC 2.0.0.15 on Mac, as it stands today:
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'll use the new fashionable nice reply.
No, but soon as in :
http://www.wowwiki.com/Soon
Blizzard broke the no-ext mode for addons - it's recommended to running everything with embedded libraries.
It does all the "processing new addons" and so on, but i dosent list them.
Could we please get an option for some sort of "backup" feature within CU, that will move or zip "old" addons before replacing them with the "updated" versions? That way, when CU invariably screws up and overwrites your addons with the wrong version, you'll have something to fall back to?
At this point, I'm sticking with manual updating from the websites, until CU gets made to something that actually works properly (I know, I know... it's beta).
R.I.P. WAU.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI second this request.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI just end up copy/pasting a backup of my interface, WTF, and Log folders to another directory before I do any updating, or at the least, once a week or so. then I've not only got the backups of the addons, but the saved variables the different versions need to work correctly. It works, it's clean and it goes MUCH faster than having a client do it for me would.
A good program (free too!) for this is SyncToy. Microsoft release, can find it from a quick Google or the microsoft.com page. Takes a minute to set up, then it makes it so you can back up your Interface/WTF folders with 2 button clicks and no headache. Been using it for months, works flawlessly.