All Things Patrick - Working Hard to be Lazy!

I got sucked into WoW and something I found was that WoW has a directory for AddOns!

I couldn't find something for a particular quest and started googling for it. As usual, someone was nice enough to list coordinates for the quest. It wasn't until later that I discovered these coordinates are percentages from the top left corner of the map, but even so it's nice to have something that will display these.

Apparently there are lots & lots of add-ons for WoW. One that a lot of people use seems to be QuestHelper. One of the pages for 1 of the quests I was doing pointed me towards Curse.com. Curse.com has a nifty downloader/installer/updater utility that works great on windows... Unfortunately I'm on linux - but I got it working!

Installation of the Curse Client under wine went smoothly. Everything seemed to work great and after running it it even sits in the system tray! Now, when I find an addon on curse.com that I want to install I should be able to just click the install via curse client button and be done with it.

Unfortunately I keep getting this error from firefox stating that it has no idea what to do with the psyn:// URI. After googling for all the wrong things I finally decided to google for firefox protocol association... After more poking around I came across this post FireFox: Associate IRC link. I don't really need something for the IRC protocol, but using this info I can piece together what I need to get the Curse Client working.

Or at least that's what I thought... I tried varying amounts of backslashes & quoting, but I couldn't get it to work. Looking at the post again I knew I could get a shell script to work, so I put this shell script together...

#!/bin/bash
/usr/bin/wine C:\\games\\curse\\CurseClient.exe -url $@

I named it ~/bin/wow-curse-module-install.sh. Now all I had to do was:

• Go to about:config in firefox
• Right click -> New -> String
• Set the name to network.protocol-handler.app.psyn
• Set the value to /home/username/bin/wow-curse-module-install.sh

I then proceeded to go through and install several different addons. Some of the addons had issues where they didn't install all of the files - including the cgProfiler for the Curse Client (I'm guessing something to do with case sensitivity on the file system or the way in which the Curse Client extracts the files).

Even after downloading the addon and extracting all of the files myself I was still having issues with various things. I ended up making all lowercase soft links that point to the proper case directories (i.e. an interface softlink that points to the Interface directory and addons that points to AddOns). I ran WoW again and most of the problems seemed to completely disappear. I still get an error on rare occasion, but usually not at a critical point in game.

After mentioning how cool QuestHelper was in guild chat, several others had to try it. After several were fumbling around with trying to get it to work I suggested they simply watch the youtube video showing how to get QuestHelper to work. It goes through downloading it from curse, unzipping the zip file, installing it, setting up WoW to use it, and showing how it works in game.

I currently have the following AddOns in WoW (some I'm still trying to figure out how to use) -

• Auctioneer
• Cartographer Complete (requires Lib: Ace2, Lib: Babble 2, LibGratuity 3, & LibRock)
• cgProfiler (profiler for Curse.com's client to keep track of AddOns)
• Fishing Buddy
• Lib: Ace2 (just click Show All & do a search for Ace2)
• Lib: Babble-2.2 (just click Show All & do a search for Babble-2)
• LibGratuity-3.0 (just click Show All & do a search for LibGratuity-3)
• LibRock-1.0 (just click Show All & do a search for LibRock-1)
• QuestHelper

There's also a Stubby & Swatter AddOns that I think came with either the Curse Client or the Cartographer Complete. Swatter is nice as it captures errors and only seems to display them once. I disabled Swatter when I was trying to test some things and every single time I moused over a creature an error popped up (I think the profiler was missing a file) which got annoying in a battle against multiple mobs as clicking the button to get rid of the message simply popped up another error window.