Archive for the ‘tools’ Category

Hand of Reckoning Macro

As usual, we’re finding out that the barebones behaviour of yet another ability is pretty poor. In order to make the brand new ranged paladin taunt more efficient, here’s a macro you can use:

#showtooltip Hand of Reckoning
/cast [target=mouseover, harm][harm] Hand of Reckoning

Bind it to a key.

This enables you to either taunt your current target or simply hover with your mouse over another foe to taunt with a simple keypress.

A more advanced version if you focus one specific add, eg one which gets CCed (to avoid having a mage or priest sandwich after sheep or shackle runs out):

#showtooltip Hand of Reckoning
/cast [modifier:shift, target=focus, harm] Hand of Reckoning
/stopmacro [modifier:shift]
/cast [target=mouseover, harm][harm] Hand of Reckoning

If you’re holding down shift, it will taunt your focus, otherwise behave just as the other one.

On Similar Matters

From FuBar to LDB: Writing Your Own AddOn Loader

In terms of menubar utilities, it appears I’m just a sheep following the lead of the enlighted Mr. Kestrel. It was after one of his posts that I moved from Titan Pannel to FuBar, and it was again after reading his November post on LDB that I migrated from FuBar to LDB (currently using StatBlockCore myself).

One of the small things which have been irking me since the transition, though, is that a certain amount of FuBar plugins (like DurabilityFu) are Load on Demand, and since I no longer use FuBar, there’s no longer anything to demand that these are loaded.

This has been annoying me for a while now, and I finally decided to write my own AddOn loader.

Fortunately, it’s so easy even someone as ungifted for coding as myself can do it. I suspect I might run into issues at some point but for the time being, it works.

And this is how you do it.

First, go to your Interface\AddOns\ folder.

Create a new folder, name it eg. MyLoader

In this folder, we will create just one new text file, called MyLoader.toc

And we will add the following code:

## Interface: 30400
## Title: MyLoader
## Notes: A little self-made utility to load some load-on-demand addons.
## Version: 0.1
## DefaultState: enabled
## OptionalDeps: loadondemandaddonX, loadondemandaddonY, loadondemandaddonZ, (...)

Make sure that every AddOn you want to load with OptionalDeps are named exactly as their respective Folder names, save it, and voilà, your own AddOn loader is done.

Clunky, and you’ll have to update the ## OptionalDeps (and ## Interface) information manually if things change, but it does the trick and only requires a minute to make.
Why pick OptionalDeps (Optional Dependencies)? If you use required dependencies instead, the little loader we just wrote will not work if for whatever reason one of the addons you want to load is not enabled or not present.

On Similar Matters

Beacon of Light Macro

The risk when you’re running as a healing / tanking / DPS hybrid (paladin) with a DPS / tanking hybrid (DK) is that you’ll end up having to heal your buddy who’s tanking to ensure the core of an instance PUG is covered.

We wanted to do the amphitheatre of Anguish last night, and you guess where it ended, I finally bit the bullet and respecced Holy.

And while I will readily admit that the wrath healadin is better than the TBC healadin, despite the new toy (Beacon of Light) or the improved old toys (6 seconds Holy Shock, and no, I’m not really using it unless things get hairy, and long distance judgement of Light), it’s a lot less fun than Ret or the Death Knight.

That being said, I somehow managed to get us through Amphitheatre of Anguish, Gun’Drak and Violet Hold, clobbering together about 1070 spell power and 11k mana out of spare kit I had been assembling in prevision of this very situation, two AH purchases and a couple of well-timed drops in the above instances.

Fun situation: in VH, the run was 4DK + me. A tanking cloak drops off the Aroakka boss (if memory serves). A level 73 DK needs because he wants it for his tanking set. I need for the same reasons. And after I win the roll, he starts whining that I stole it since I’m holy spec.

Memo to the clueless whining noob with a misplaced sense of entitlement: the healer has the same right to need on off-spec gear as a DPS, and if you have an issue with that, you make sure you get really good with combat bandaging. Especially when said healer blew over 200g in respec and AH gear cost to drag your underleveled arse through the instance.

Beacon of Light is an interesting spell. Using it properly at the right time is probably a bit of a learning curve, but I’ve been tossing it on anyone taking a HP dive at the same time as Steptoe (the tank, duh) and it seemed to work OK.

That being said, it took me a moment to figure out how to macro it properly to speed things up, and here’s what I came up with:

#showtooltip Beacon of Light
/cast [target=mouseover, help][help][target=player] Beacon of Light

Binding the macro to a key then allows me to hower over an unit frame to cast, or select a target, or if nothing else is selected, cast it on myself at one single keypress.

That did the trick.

Later, I went outside and tried to kill something with my holy spec. And wept bitterly. Never gonna make 80 with holy spec. I hope the bloody dual spec feature doesn’t get delayed too much, it’s really becoming a must-have feature (and we haven’t even tried it out yet…).

On Similar Matters

Frost Death Knight Macro: Hungering Cold / Bandage macro

Here’s the Frost Death Knight’s equivalent to the pallie’s Bubble + Bandage macro:

#showtooltip
/cast Hungering Cold
/use [target=player] Heavy Frostweave Bandage

Useful when things start getting out of hand with an AoE pull.

On Similar Matters

SEO Basics for the WoW Blogger

Following Yashima’s mishap with one of the scumbag gold-selling splogs we all hate, it struck me that some WoW Bloggers may have little notions on how to improve their search engine visibility.

This post will be focused on self-hosted WordPress blogs, but some elements may be applicable to other platforms as well.

First, what is SEO, and why would your WoW blog want it?

SEO stands for Search Engine Optimization, a field of activity which covers an innumerable amount of methods to promote a website. These methods are in general roughly divided into so called white hat activities, considered fully legit by search engines, and black hat, which if caught will get your site blacklisted. While most search engines have different rules of what is black hat and what not, as a very rough rule of fist, anything which is devised to deceive a search engine or artificially inflate your search results is to be considered off-limits.

The purpose of starting to apply some SEO techniques is to boost your search engine traffic and ensure all the wonderful, smart, funny, witty, insightful posts you write are positioned properly.

A word of warning before we begin, though. No search engine has published how their indexing mechanisms work exactly, nor how they rate content internally.  As a consequence, the field of SEO theory has always been full of exploratory techniques which would turn out, later on, to be totally worthless. Fortunately, we’re going to focus on the basics and these are quite straightforward.

As to the question of whether it’s worth it, well, in the grand scheme of things Altitis is a very small blog. Before Wrath (and due to a low posting volume), my readership was in average below 150 visits a day. If you were to Google last Friday (when I started writing this post) and type “death knight macros” as the search term, though, I was sitting in 4th position with my post about the ghoul leap suppression. Ahead of scores of sites focused on macros, ahead of wowwiki, dedicated DK sites, and even the o-bards.

Since Wrath was released, my readership sits between 400 and 600 visits a day, without ever getting linked by the big names (EJ or WoWInsider). All of the additional visits come from search engines, mostly Google.

Worth it? Well, I don’t have advertisements on the site, but I still like the fact that my posts are being read, so I’d say yes, it’s definitely worth it for me.

Setting Up

First thing first. Before anything else, make sure your blog is actually allowing search engines. On WordPress, it’s under Settings -> Privacy. Blogger definitely has that setting as well, under Settings->Basic->Let Search Engines find your blog. Others? You tell me :)

Second, make sure your blog is known and recognized by Google. Blogger users have a slight advantage over others here as they will be included in some capacity even if they do nothing beyond changing the privacy settings. Nonetheless, start by visiting Google Webmaster Central and follow the Submit your content to Google procedure. Next, sign in to webmaster tools, and authenticate your site. Webmaster tools aren’t really good for a lot of things as much of the information is stale, inaccurate or way too plentiful to be of any practical use, but the diagnostics page can point out a couple of interesting elements to check and fix. Among these, keywords and meta descriptions.

For WordPress users, a good way to improve drastically the context of your posts – that is, providing some additional information to search engines to help them catalog your posts, or in other words, to give them some clues what your post is about, is to grab the plug-in All-in-One-SEO Pack.

The reason you want to use and configure this plugin is simple, it gives you a simple and handy way to edit meta keywords and descriptions for all your posts, which will appear as an additional set of fields in your edit post page. The settings are pretty self-explanatory, but basically you will want to fill in some generic recurring elements (like “world of warcraft” for the home keywords”) in there at the very least, for the general context of what you’re writing about.

In the post editor page, under the All in One SEO Pack menu you will have an opportunity to enter some specific keywords and a short description of what the page is about. Note that while not all search engines will use these, they are better filled in than left out. Descriptions should ideally have between 80 and 160 characters (more might get ignored, less are flagged as “short descs” by Google) and should be unique for each post.

Next, a very important element, the post slug, or permalinks – in short the url under which an individual post can be reached. Blogger users have little in terms of options here but in your Settings->Archive Settings make sure you have Enable Post Pages active. This is important so that the search engines index each post individually instead of just an ever-changing front-page where whatever search results fall off every 10 posts or so.

For WordPress users, you have many different choices in how to configure permalinks, under Settings->Permalinks. There are many schools of thought about permalinks, but one of the most basic one is to make sure these actually add to search visibility. That is, your permalink should be explicit and probably reflect your post title. The default setting in WordPress (both self-hosted and on WordPress.com) is to a simple numerical value. This is bad, as the numbers not only aren’t telling any story at all, but if for whatever reason you migrate your database the posts may get re-numbered, and all search results pointing to any specific posts will end up in a wrong place. You could further improve visibility by making the permalink text a rephrased version of your post title. For the rest, there are divergent opinions of what else should be part of the permalinks – just the post’s name, or the full date, just the month or just the year. The majority opinion seems to be the shorter the better (so no dates at all or just the year), but full dates are quite popular on some SEO trendsetters’ own blogs as well. As long as the permalinks are explicit, you’d probably have to work at Google to know which of the other options are best.

Last but not least, to improve the search engine’s knowledge of your blog’s content, you will want to generate a sitemap. The best way to do that is to use the Google XML Sitemap plugin. Once you create your sitemap, make sure to go back to Webmaster Central and link to the sitemap from here. As you will see in the plugin’s settings, you would be well advised at that stage to also follow through with the other search engines, use their own webmaster tools and make sure the sitemaps are registered there as well.

Duplicate Content? We don’t need no duplicate content!

In general and due to years of abuse by spammers and black hat SEOs, search engines will penalize duplicated content. The problem here is that WordPress in particular is very generous in the way people can access an individual post: by its permalink, by its category (../category/MyCategoryname/permalink)  and by its tags (../tag/MyTagName/permalink). A post in two categories will therefore appear in Google’s index at least thrice: by it’s own normal permalink, Category 1 and Category 2. This is bad because Google is said to penalize all results on the theory that it may actually be spam posted all over the web. If you use tags, you can add one additional individual result per tag, which will rapidly dilute the value of your post the more tags you’re using. Last but not least, WordPress 2.7 has added comment pagination, which means you may end up with your normal post’s permalink duplicated with permalink/comment-page-#/ by search engines. Not good.

The best way to fix that is twofold: For most search engines, noindex directives to categories and tag archives will be honoured. The simplest way to implement that is to use a plugin called Robots Meta, it’s configuration is still pretty straightforward. Google is however pretty bad at honouring noindex and nofollow directives, so for these guys, you’ll want to make sure the following is set in your robots.txt file (create this one at the root of your blog’s path, eg altitis.treehuggers.info):

User-agent: Googlebot
Disallow: /category/
Disallow: /tag/
Disallow: /comment-page

This will simply prevent Googlebot, the automated scanning engine, to access all links containing these three elements, and sort the issue.

We’re doing it with Style!

Last but not least, remember the good old html heading tags, <h1> to <h5>? Since the advent of CSS, they have often become underused, but in terms of search visibility, that’s probably a mistake. Headings are important as they give additional context, so do use them properly to provide a clear hierarchy to your content. Again, there are a couple of options available to you, but roughly, you should decide how you will build up your blog’s brand. Is each individual post the key element you want to promote? Make sure your post title is styled with <h1> tags. Is your blog’s name the brand you want to promote? Make your blog name a <h1> tag and your individual posts <h2> tags. Everything else should have a lower heading that these, your posts however should probably not be lower than <h2>.

Content is King

Beyond the above basic technical measures, there are almost as many tricks and methods as there are SEO specialists. Whether to investigate the field further for a hobby WoW blog is worth the time or not is up to each individual blogger, but you can easily get lost in the wealth of additional stuff to do (popular things include link-building and the realtively new but still not proven pagerank sculpting, for instance). That being said, the best way to have a good search visibility remains to simply write quality content matching the purpose of your blog. The better your posts, the more people will read it, comment on it or comment about it. In the end, a trackback from your blogging peers will remain a high-value testimonial to the quality, relevance, importance or wittiness of your writings, and no amount of additional SEO techniques can replace that.

On Similar Matters

Death Knight Macro: Rune Strike Wrapper

Here’s a cool macro template to get your rune strike into your opponent’s face:

#showtooltip Blood Strike
/cast [nomodifier] Rune Strike
/cast Blood Strike

Make one for each of your relevant runic abilities (not RP, only runes) and you’ll be sure to dump RS whenever the opportunity is up.

If you need to conserve RP for Dancing Rune Weapon or a Gargoyle, simply hold down any modifier key and the spell will be cast without RS. Oh, and make sure RS is first in your macro, the other abilities are on a cooldown, which would prevent RS from being cast on the same keypress otherwise.

On Similar Matters

HowTo: Debug your UI

Stranded in WoW 3.0.2 withtout working addons? Getting mad because you can’t exactly figure out what’s broken where?

Many things actually work, but in order to get it fixed, a methodical approach works best.

Here’s my method:

Tools

  • AddOn Control Panel (ACP), found here
  • If you’re using Gatherer or Auctioneer, Swatter which is part of the distribution, otherwise I recommend Rabbit’s excellent Buggrabber.

Method

  1. Disable all AddOns
  2. Make sure ACP and either Swatter or Buggrabber is active (if you have both, Swatter will politely yield to Buggrabber)
  3. If you’re using Swatter, after loading a toon, type /swat enable. Remember, if you have both, only Buggrabber will actually work
  4. Type /reloadui (it should now work) or /acp and click the reloadui button, you’re now in a clean slate state
  5. Now add your addons back through ACP step by step, and reload the UI between each step
  6. Swatter should start popping up by itself, if not, type /swat show to see the error list, and /swat autoshow once to have the window pop up on an error
  7. The errors due to any missing libraries are at the beginning of the error lists, the rest are usually errors borne out of the fact that said libraries aren’t there
  8. /buggrabber # will show you each error in turn. Swatter will need you to click through to reach the earliest errors.
  9. Now go download your missing dependencies, exit the game and restart to get them accounted for, then rince and repeat.
  10. Last but not least, with Swatter, make sure you type /swat clear before you reload, since it actually saves the entire error list. Buggrabber does not.

Note that Buggrabber also relies on a companion, bugsack, which gives a nice window display too. It doesn’t currently work for me, though, and barebones buggrabber does the trick as well.

It’s a long and painful process, but the only way to recover whatever you need asap without going completely insane.

I hope :)

On Similar Matters

A Plea to Ace & Curse: Bring Us NoLib AddOns ASAP

As many readers have been slowly realizing over the past 24 hours, the WoWAce community has gone through a massive change in the way they make addons available to the general public – ie. all of us end-users.

The reason given is simple, the Ace community’s success, combined with automatic updaters, have been vastly exceeding their servers’ capacity, to a point which became seriously threatening to their core mission: to provide AddOn developers with the adequate means to work, share, interact and develop code.

The AddOn distribution part of WoWAce has started to effectively imperil the AddOn creation part, something which would, in the long term, harm us, the end-users, a lot more than having to change our downloading ways.

In concrete terms, the WoWAce community will no longer host AddOns for wide distribution, but rely, instead, on Curse.com for that task.

This will impact us in the following manner:

  • If you were manually updating AddOns from files.wowace.com, switch over to curse.com or wowinterface.com (which is still operating at full speed)
  • If you were using WoWAce Updater, this tool has been discontinued. Your recommended choice is to download the curse client instead and start using it.
  • If you were using a different updater and it supports AddOn site changes, like WUU (which is what I’m using), you’ll have to start the sometimes gruesome (when you have 290 AddOns and libs in your portfolio, that is gruesome) task to reroute each of the Ace packages to a different site, adapting the site ID in the process. Note that Curse repositories in general use only lowercase names (contrary to what wowace had) and WoWInterface uses an ID number followed by a dash and the addon name (eg. 1234-myaddon). Also note that WoWI is currently in the low bandwidth mode and updating through the standard siteID is actually not possible.

No matter how, solutions are at hand to help you bring your AddOns up to 3.0.2 par. Granted, the Curse client is, at the time of this writing, quite lacking in features, bells and whistles, but it mostly works.

However, one of the core and fundamental benefits of using Ace AddOns AND getting them from WoWAce was the possibility to download the AddOns separate from the Libraries. The advantage isn’t just in file size, it’s also the best way to ensure you’re not suddenly having two AddOns having library version conflicts, like one loading an older instance of a library which doesn’t hold more recent or updated functions the other one would need.

This is therefore an appeal to the people in charge at WoWAce and Curse. You yourselves have extolled the virtues of nolib distributions, of disembedding the libraries from the individual packages. You have convinced us years ago because it made perfect sense, and you were right then. It still makes perfect sense today.

Please give us access to the bare packages without the libraries. Manually erasing 220 lib folders every update is just not viable.

Thank you kindly.

One of your enthusiastic end-users.

On Similar Matters

Official Wrath Talent Calculators Online

This post contents Wrath Beta SpoilersJust a quick heads-up, Blizzard has put official talent calculators for Wrath up for playing. Here’s the EU version, and here the US one. The latter has a nice landing page, too.

Alternatively (or if they are down / too slow for your taste / whatever), MMO Champion has added their own talent calculator as well. And there’s of course the one at wowhead, but you know my stance about linking to these guys by now.

Anyway, that’s most certainly enough toys to start theorycrafting level 80 builds, unless you’re part of the lucky beta testers :)

On Similar Matters

Blizzard Authenticator Warning: Only One Per Account

Just a quick heads-up here. I’ve now read on four separate sites that some people are ordering more than one Blizzard Authenticator for themselves, eg. if they play on a desktop computer and a laptop.

It doesn’t work that way, I’m afraid. You can use one single Authenticator for several accounts, but not the other way around. Multiboxing? One authenticator for all your boxes is enough. WoW, Scarcraft2 on battle.net and the future diablo 3 accounts can all be protected with the same Authenticator. But you can’t have two authenticators protect the same account twice.

From the Authenticator FAQ:

Can I apply my Blizzard Authenticator to more than one account?

Yes! You’re welcome to associate a single Blizzard Authenticator to as many accounts as you like. Please remember that you must have that Authenticator with you to log in to any of these accounts afterwards.

Can I keep one Blizzard Authenticator at home and another at work, and have both associated to the same account?

No. Each account can have only one Blizzard Authenticator linked to it at a time, so you would need to carry the Authenticator with you to log in from different computers.

Hope that clarifies it.

On Similar Matters

World of Warcraft™ and Blizzard Entertainment® are all trademarks or registered trademarks of Blizzard Entertainment in the United States and/or other countries. These terms and all related materials, logos, and images are copyright © Blizzard Entertainment. This site is in no way associated with Blizzard Entertainment®