Addons in 3.0.2
Sunday, October 19th, 2008Patch 3.0.2 has played havoc with our WoW addons as I’m sure we’ve all found out in the past few days. The easiest first response to this is to turn them all off. This is quite a good first step as it happens. The next steps are then updating the addons to latest versions and then turning each addon back on in turn to check that it doesn’t introduce problems.
Updating Addons
How you choose to update your addons probably depends on how many you’re using. If you’re using a small number, the easiest thing is simply to download the latest versions from your addon site of choice (I’m currently using Curse Gaming), or from their home site in the case of very popular addons like CT-Mod, Auctioneer and DeadlyBossMods. You can then unzip these to the WoW Interface\Addons folder, making sure they replace the old versions.
If you have a large number of addons, investigating an update program such as WUU (see my previous managing addons guide for details), is probably easier to get all the many addons up to date.
Also note that some addons have taken the 3.0.2 patch as an opportunity to move to a completely new version, for example Bartender - you now need to download Bartender4, rather than the old Bartender3.
Enabling addons and problem finding
Once you’re up to date, the best thing is to switch each addon in turn to check that it works ok. A couple more addons really help here, the first - Addon Control Panel (ACP) - allows you to switch addons on & off in-game and to reload your user interface, without having to keep logging in and out. After this installing something to catch any errors such as Swatter (comes bundled with Auctioneer) or Buggrabber is great to help you see any problems that are happening. I found buggrabber a little unintuitive - you have to type /buggrabber 1 to see the first error, /buggrabber 2 to see the second error etc. Installing BugSack and Broker2FuBar allows you to see the errors from FuBar (if you have that one installed), but can be a bit of an undertaking and has some incompatibilities, so I’d recommend sticking to the text commands unless you’re feeling confident.
For a complete guide to debugging your interface see this great post from Altitis.