Posted by Kaelten Oct 26, 2008 at 23:54 UTC
The State of the Client
I want to start out by stating that we're well aware of the issues. We're not deluded into thinking that the current state of the Curse Client is as good as it gets.
Up until this point I've been on the sidelines of the Client, however I'm pleased to say that I'm taking over the project and will be leading product development on the client.
I've spent a large portion of my time over the last several weeks reading forums and talking to people to get a better idea of what people want, need, and hate.
We've recently broken 500,000 Client installs. While that is a very exciting number for us to reach, it also shows us the level of responsibility we have to making sure that the client is the best possible.
The Big Issues
It is the primary purpose of this announcement to help communicate what's going to be changing in the near future. But first let me recap some of the things that are definite issues(in no particular order). This is also not necessarily an all inclusive list.
Now I want to tell you what we're going to be doing in order to improve things.
What we're going to do about it!
First we're giving the UI an overhaul. The overall goal here is to make sure that the interface is more intuitive, more usable, and that it gives better feedback about what it's doing. To that end we're taking the following steps:
In addition to the above colors we're going to be using sorting to help it make sense. All Yellows and Grays will be forced to the bottom of the listings. All Red and Purples(?) will be forced to the top for easy identification.
We're also going to be enhancing the activity log panel, making some adjustments to the change log viewers, redoing the listing controls to allow you more options, adding more messages back to the user, etc.
Like I mentioned before we're missing de facto features. And we'll be moving quickly to add them.
Several of these above features are considered to be advanced features and we will be labeling them as such.
Changed Behaviors & Methods
One of the larger problems we've faced is about it auto detecting the wrong addons and/or downgrading or otherwise installing things wrongly.
We're taking a few steps to fixing these problems.
Discovery and Detection of versions
First, we're changing our auto detection code. In the next major release we're switching away from toc name based matching to instead use unique version fingerprints. We will both be fingerprinting individual files and packages as a whole in order to know for sure what version you're using.
Because of the fact that this will allow us to know within a very high level of accuracy in identifying exactly what version of a addon you're using we'll be able to reliably recommend upgrades.
The question shifted at that point to knowing what to do when we don't recognize the files. So we're changing the behavior some. For unrecognized packages we'll be displaying a special Unrecognized status. From that point on we won't update the addon until either a) you tell the client to or b) we learn for sure what version that is.
This does have one potential issue, or in some cases a feature, for auto discovery. If you go in and edit an addon, add a file, remove a file, etc the fingerprint of the file will change and then the fingerprint of the whole package will change.
In the case of initial discovery we won't be able to auto detect what project the files belong to. If we do know what project the file belongs to it becomes an Unrecognized version and will no longer be updated until you tell the client to do so. Down side, if you have some zombie files in your directory from unclean upgrades you'll need to manually match the project or tell it to upgrade.
The current toc name based scanner will still be available for suggesting matches in the new Uninstalled Package Listings.
Changes to Defaults
We're changing a few default behaviors. We'll no longer be defaulting to fully automatic addons update as this seems to be counter to the majority of our users usage patterns. We'll be shifting the defaults throughout the client to match the default behaviors of our users.
These annoying repetitive popup questions will be streamlined out of the client. Anytime we find ourselves saying "well we could ask the user...." we're going to smack ourselves and find away to do it without that.
The Mac Version
Having a fully functional Client under Mac is very important to us. We know that it does not follow many of the standard conventions on macs at this time. We will be addressing as many of those as possible, however our first focus is on having a solid product with all the needed features. After we get there we will then focus on asethetics and the macesqueness of the client (is that a word?).
I'm very happy to be stepping up my participation with the Client. I hope that this massive wall of text I've posted has helped you realize just HOW serious we are about delivering the best possible updater.
We will be continuing the free premium preview until we've gotten most of the things in this announcement out the way. We hope to have everything in this missive out to you guys in just a few short weeks.
And as always, please give me as much feedback as possible. Any and all constructive feedback on the things outlined in this announcement is most certainly welcomed.
It's a lot of work to do. We're making daily progress. And I'll keep you posted.
Posted by ckknight Jun 26, 2009 at 20:14 UTC
Hey there, ckknight here.
I've been slaving over the keyboard for the past few days getting some cool features in that I hope a lot of you will appreciate:
Posted by Xtek Mar 05, 2010 at 00:27 UTC
This is a pretty urgent thing to report because it could damage or potentially completely ruin your video card if it's ignored. The latest NVIDIA drivers, 196.75-WHQL released on March 2nd, 2010 are causing issues with the video card fan control while playing Blizzard (and other) games. This is caused by the Automatic Fan Speed feature being broken in the latest drivers.
The games included are: World of Warcraft, StarCraft II Beta and Warcraft III. If you play any of these games (which I'm pretty sure you do if you're reading this website), you'll want to roll your drivers back to earlier versions until this is fixed, unless you want to replace a video card within the next few days.
To find out what version drivers you're using:
Quote from Datth:
Posted by Ackis Nov 17, 2010 at 18:38 UTC
Taken from the news report here
We're aware of an issue where random users will not be able to connect to either the Curse Client, Curse.com, and/or other Curse sites. This is a temporary problem that should go away by tomorrow, the 18th.
We do apologize for any inconveniences this has caused, but please do not submit client support tickets related to connection issues until after tomorrow, Thursday the 18th.
Thank you, The Curse Support Team
This does not seem to be affecting CurseForge, WowAce or SC2Mapster.
Stealing this from Merah:
You may need to clean your cache with: ipconfig /flushdns
If it does not help switch to Google's public DNS, they have new records.
>nslookup curse.com Server: google-public-dns-a.google.com Address: 220.127.116.11 Non-authoritative answer: Name: curse.com Address: 18.104.22.168 >nslookup www.curse.com Server: google-public-dns-a.google.com Address: 22.214.171.124 Non-authoritative answer: Name: www.curse.com Address: 126.96.36.199 dns1: 188.8.131.52 dns2: 184.108.40.206
Posted by Ackis Dec 04, 2011 at 09:19 UTC
Just wanted to give everyone a heads up that a new category has been added.
At this moment we don't have an icon for it, but it exists so you can go forth and use it! :D