Hermes

General

Q: I found a bug. What do I do?

Please submit a ticket. While the core of Hermes is fairly simple, some of the features (such as the UI, and the Spell Monitor) are quite complex. Bugs are a part of life but I usually take care of them quickly when reported.

Q: I only want to see when someone uses a spell. I don't care who has it available. Does Hermes do this?

Yes. There are two ways to do this:

  1. For containers using the GridBars view, you can check the "Only show bar when spell is on cooldown" option found under the Behavior section of the View Settings.
  2. Change your containers view to use CooldownBars. This view only ever shows spells that are on cooldown.

Spell Tracking

Q: Does Hermes track Warlock Soulstones?

Yes. The spell you'll want to use is Soulstone Resurrection (spell id 20707).

Q: Does Hermes track Shaman Reincarnation?

Yes. The spell you'll want to use is Reincarnation (spell id 20608).

Q: Does Hermes take Glyphs into account?

There are two answers to this question. For users running Hermes, glyphs are 100% accounted for. For users not running Hermes (which thus rely on the Spell Monitor) glyphs are not (and cannot be) accounted for. This is a limitation in the Blizzard API. Please see the Spell Monitor section below for a workaround however.

Q: I added a new spell but Hermes isn't working. What's wrong?

Most spell "names" have numerous matching "id's". When this happens, it's impossible for Hermes to know which id is correct, it just picks the first one it finds. Whenever possible, enter the ID for a spell instead of it's NAME. This will solve 95% of the issues reported.

If you entered the spell by name, then check that the spell id Hermes used is correct. This is best done by hovering over the enable checkbox for the spell in the configuration window (it'll show you the spell id there). Use http:www.wowhead.com/ to compare with the value Hermes chose.

Optionally, if someone else in your raid is tracking that spell correctly, you can ask them to hover over the ability in their Hermes container as the id is shown in the tooltip.

Q: Can Hermes track Mirror of Broken Images ?

Yes. Hermes can track any equipped or usable item such as trinkets and potions. These are configured on the Items tab. Note however that item cooldown tracking only works with other Hermes users (Spell Monitor does not support this). For items that are equippable (like a trinket), Hermes will make sure that the item is equipped and check it's cooldown. For items that are not equippable (like potions) Hermes will make sure there is at least one in their inventory and check it's cooldown. If not equipped or not in their inventory, Hermes will consider that person to not have the ability.

Note: If the trinket or other item generates a SPELL_AURA_APPLIED event, then Spell Monitor is capable of tracking it via the spell id of the buff.

The Alliance version of Mirror of Broken Images has an item id of 62471 (Horde is 62466) Using the trinket (Alliance or Horde) gives a buff called Image of Immortality with a spell id of 92222.

Spell Monitor

Q: How accurate are Spell Monitor cooldowns versus those from other Hermes users?

Spell Monitor relies on the combat log. Therefore any cooldowns used by non Hermes users while not in combat log range (or while you were logged out) will not be detected. As far as accuracy is concerned, that's mostly in your hands. You'll need to configure the requirements and adjustments of each spell as necessary to suit your needs.

For players running Hermes, the spellbook is used to determine cooldown values. This means that cooldowns from other Hermes users will always be 100% accurate (whether logged out or not) without any additional work on your part.

There's a huge advantage to everyone running Hermes in that it'll work 100% out of the box.

Q: Does Spell Monitor account for glyphs?

No, but there is a workaround. If you know that a certain player always has a glyph equipped, you can create a "Player Name" adjustment for that spell and person. For example, Glyph of Lay on Hands reduces the cooldown by 3 minutes. Create a Player Name adjustment for Lay on Hands using the name of your Holy Paladin and -180 for the Coolldown Offset (note the minus sign).

Alternatively, if all of the Holy Paladins in your raid have this glyph you can just set the Base Cooldown to account for it right there.

Q: Can I prevent Spell Monitor from including certain players?

Yes, you can create a "Player Names" requirement. This acts like a white list. If created, only the names in this list will be tracked.

Q: Why does it take so long for non Hermes users to show up?

For accuracy reasons, Spell Monitor needs the talents of players before it can track their cooldowns. Talents aren't available until you're in inspect range. Blizzard also throttles how often a player's talents can be queried. When you add all of this up, it can take up to 30 seconds for Hermes to extract the talents of the players in your raid (assuming they're in range of course). Once extracted that first time, it's not an issue.

Q: I noticed that Hermes "remembers" cooldowns of non Hermes users even after I reload my UI. How is that possible?

Hermes uses a simple algorithm that compares the difference between your system uptime to the server time. As long as the delta between these two values is the same (within 3 seconds), and the cooldown did not expire while you were logged out, the previously detected cooldown value is reliable. Rebooting your computer will change your system uptime, thus invalidating the status of any prior cooldowns. Hermes handles this appropriately.

This feature is very valuable for lengthy cooldowns (Reincarnation, Lay on Hands, etc.). Short cooldowns are likely to expire while logged out, making this feature less useful for them.

Performance

Q: How much communication traffic does Hermes generate?

The short answer is, not that much.

It's significantly better than similar addons I've tested. I've spent great effort in optimizing the message protocol. In fact, I spent a week designing the protocol before writing a single line of code. I haven't changed the protocol since the very first release of Hermes. That's how stable it is.

Most of the optimization is invisible to you, but one place where it's not is when you see the "Hermes: queuing requests for 10 seconds..." message: By queuing up all the spell requests from other players, Hermes will send one message to the raid with all of the requested cooldown information instead of an individual message for each request as it comes in (of which many will be requests for the same spell).

An example of an invisible optimization is that if only one player is tracking an ability of yours, then Hermes will Whisper that player with updates instead of sending an update to the entire raid (resulting in 1 message received instead of 25).

In short, Hermes knows what players are tracking what spells (if any), and it takes advantage of this.

Q: Is Hermes CPU intensive?

Hermes performs well. Here are some comparisons for you:

CPU utilization:

  1. 12.2% - Recount
  2. 10.4% - Pitbull
  3. 7.4% - Grid
  4. 7.0% - Bartender4
  5. 4.3% - Power Auras Classic
  6. 1.7% - Mik's Scrolling Battle Text
  7. 1.5% - Tidy Plates
  8. 1.5% - Hermes

Performance varies based on how many abilities you're tracking, whether you're using Bars Style or Buttons Style, etc. For the numbers above, I was monitoring 15 abilities, 10 using Bars Style, and Spell Monitor enabled.

Disclaimer: The above values were taken with v2.2. Significant features were added since which will surely have an impact. I will update this page when I have more data available.

Q: How much memory does Hermes use?

Hermes uses a fair amount of memory. Anywhere between 1 and 2 MB is typical. A lot of this is from the cached talent information used by Spell Monitor. Another decent chunk comes from all the spells that get loaded (along with the name and icon for each spell). But this caching is also what improves CPU performance. And CPU is what matters.

The dynamic nature of the configuration windows (I'm pushing AceConfigDialog to it's limits) do in fact consume a sizable amount of memory. Especially if you are constantly switching around doing various tasks. However, the memory *WILL* eventually get garbage collected so there's no reason to worry.

You must login to post a comment. Don't have an account? Register to get one!

Facts

Date created
May 28, 2011
Last updated
Jul 03, 2011

Author