I have been doing some amount of work on combat log analysis recently. There are certain things for which neither WWS nor WoL are suitable.

When Blizzard redid the combat logs in 2.4, they added GUID columns for each participant in the line (source and destination or, if you prefer, subject and object). The GUIDs can be used to uniquely identify a participant.

According to WoWWiki's page on UnitGUID(), you can determine the type of object using a bitmask. If you shift the GUID right 52-bits and do a boolean AND with 0x7:

• 0 is a player.
• 1 is a world object.
• 3 is an NPC.
• 4 is a pet.
• 5 is a vehicle.

(In US realms, the third digit from the left will show this. In EU realms, the higher bits seem to be used for something recently.)

So, given the following GUIDs:

• The entity with GUID 0x0200000000322CF9 is a player. (My mage on Stormrage.)
• The entity with GUID 0xF130008061003BD7 is an NPC. (Thorim)
• The entity with GUID 0xF13000752E004257 is also an NPC. ("Desecrated Ground V")
• The entity with GUID 0xF14007BC02000063 is a pet. (An imp.)
• The entity with GUID 0xF150008208030C23 is a vehicle. (Yogg-Saron)

Yes, Yogg-Saron is a vehicle. Other mobs which appear as vehicles include the Constrictor Tentacles, Ignis, and Archavon the Stone Watcher. All of these mobs have effects that physically hinder or affect a character in some fashion. This suggests that these are designated as vehicles as a side effect of the internal mechanic for these effects.

There is something hilarious about Yogg-Saron as a vehicle though.

I've been bad about updating the site recently. Unfortunately, a lack of "important" insights and time has kept me from doing much. Perhaps I will get someone else to write.

Anyway, what I've been doing:

• Raiding. A lot.

  Raiding five days per week does decrease the amount of time available. We did get Yogg-Saron down two weeks ago in the 10-man raids so at least that's something.

• Working on Rawr.

  What started out as contributing patches for Rawr's DPSDK model has turned into a position as an official developer. My focus is still fixing small bugs in the DPSDK model.

With 3.2 coming soon, I hope to do more posts. However, my track record on this is somewhat poor so we'll see how that goes.

The Avarice Alliance downed Sartharion with all three drakes up in both 10-man and 25-man on Saturday, 21 March 2009. This keeps Avarice among the top raiding entities on Stormrage (although still a little slow, we should be better in Ulduar).

ReadyCheckFix is now ready for public use.

ReadyCheckFix fixes a bug added by Blizzard in 3.0.2 that prevents the ready check sound from playing for all checks.

To learn more, go to the project page.

CharmCommand is now ready for public use.

CharmCommand provides commands for assigning raid symbols, also called "lucky charms." These are suitable for use in macros or from the edit box/command line.

To learn more, go to the project page.

Despite what I said in the previous entry, I've opted not to pursue upgrading to Drupal 6. The main reason for not doing this is because the Project module for Drupal is not ready for use with 6 yet. I chose to use Project to manage WoW addon projects I've been working on. (More on those later.)

I replaced the warcraft_armory module with the warcraft_itemstats module. It accomplishes the same basic goal without having to import items from the Armory into Drupal. This tendency caused the database to grow to be over a gigabyte in size when dumped. Now, the database dump is a much more reasonable 66 megabytes.

This completes most of the infrastructure work I have been planning on doing. Now since Wrath of the Lich King has been released, I may have a lot to post about in the near future... or very little at all.

I've upgraded Drupal to 5.12. I plan to upgrade to 6 in the near future.

Going to version 6 will require some significant changes: The module I'm using to handle item imports from the armory is not being maintained. While this shouldn't require having to redo some entries, I will have to rewrite this module myself. Either I will replace it with a lengthy, behind-the-scenes import from the Armory like the current module or I will implement it on top of itemstats. Either way, it's going to be interesting.

3.0.x has also seen me seriously picking up addon development and I want to get proper pages set up here for that too. It's just a matter of time...

I really need to get back in the habit of doing updates.

Anyway: S4 gear for PvE for mages doesn't seem to really be that great an idea. Last I checked in Rawr, the S4 pieces all tended to lose out to gear acquirable in early T5 if not earlier.

The neck is a different case. The Guardian's Pendant of Subjugation is a very nice piece. When gemmed with one of the new epic haste tems, it comes out superior to Loop of Cursed Bones from Zul'jin, which is a pretty nice neck piece. (When I finish updating the item list, I'll be able to show the difference better.)

So while I was not working on Phaedra's List (work has been pretty busy for the last few weeks and I've gotten no work done), the fact that Rawr, a druid modeling project now has a module for mages too was brought up on the EJ mage theorycrafting thread. And it turns out that it does most of what I'd wanted to achieve with Phaedra's List. So I guess I'm putting the project on hiatus, especially since I still don't have time at the moment.

This is not to say I won't come back and work on it... I think that there's a definite niche for the tool but I don't have the time to work on it right now. And a proper implementation of the gear parser (quartermaster) would definitely allow for a backend for something like Lootzor... and it could be kept up to date too! (This being an outstanding issue with Lootzor...)

It turns out that the tooltips had not been completely parsed correctly.

When originally doing the testing on rishu, I ran into an issue that the Test::Unit::XML gem wasn't working correctly. It would accept two radically different XML paragraphs with doctype headers and say that they were equal.

After some amount of digging, I found this bug on the REXML tracker. I made the (one-line) change provided and suddenly Test::Unit::XML started working again.

The ruby install on winry provided with a newer version of REXML than what was on rishu. However, it still did not incorporate the fix in the bug report. Unfortunately, I used winry to validate the item tooltip XML since it was faster.

After adding the fix to REXL, the validation script is dying because there are still unimplemented tags. Yay for more work.