On the MacOS version, running in automatic update mode, it's difficult to know when the client has completed its update run, or what it's currently doing. There needs to be some sort of positive confirmation that the update run is complete, so that we know it's ok to quit the client and start WoW. Is 2.0.0.15 still the latest MacOS version?
Having used it for a week, I'm still less than convinced it's something I'd be willing to pay for (even a small amount). Given the choice between paying for it or writing my own scripts to update from tagged versions in SVN, I currently reckon I'd opt to write my own scripts.
CurseClient 2.0.0.15 seems to have a fatal bug on MacOS. It's crashing shortly after launch and is currently unusable as a result. Here's the crash dump:
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.
0
On the MacOS version, running in automatic update mode, it's difficult to know when the client has completed its update run, or what it's currently doing. There needs to be some sort of positive confirmation that the update run is complete, so that we know it's ok to quit the client and start WoW. Is 2.0.0.15 still the latest MacOS version?
Having used it for a week, I'm still less than convinced it's something I'd be willing to pay for (even a small amount). Given the choice between paying for it or writing my own scripts to update from tagged versions in SVN, I currently reckon I'd opt to write my own scripts.
Lastly, any ETA on disembedded support?
0
0
0
continued in next post...
0
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: