Update to Cog of Doom

10/18/2010

Just wanted to share this. A very enterprising person posted this in the Bug Report Blizzard forums. Link

Deyneth made up scripts for 2 macros, the first of which you'd use whenever there might be a possibility of freezing the game. I'd recommend turning off the tooltips whenever going into a random dungeon, like when zoning into the Oculus, your mouse naturally lands right on the entrance portal, causing the freeze-up. Also, definitely do it when going for the Headless Horseman. The first script will still allow you to interact with objects, it just won't pop up a tool tip description when you hover over them.

And, when the danger has passed, like after you've killed the HH, use the second to turn tooltips back on.

I've taken the liberty of posting the scripts here as well. Copy & paste into macros for your toons, and you shouldn't have any problems. /cheers for Deyneth!

Turn Off Tooltips

/script GameTooltip.Temphide = function() GameTooltip:Hide() end; GameTooltip:SetScript("OnShow", GameTooltip.Temphide);

Turn On Tooltips

/script GameTooltip:SetScript("OnShow", GameTooltip.Show);

The Cog of Doom!!!!!! ...... Or, how a mouse-over throws a wrench in the works

10/18/2010

Hallow's End is upon us, and I was looking forward to getting my Loot on with the Headless Horseman, especially since I only managed to do the event once with Bloodshrike last year.

Instead, I've only managed to become like Ichabod Crane, dumped unceremoniously from the instance when I zone in. When you get in the graveyard, directly in front of you is a pumpkin, which you almost are invariably already mousing over. Unfortunately......there seems to be a bug in the 4.01 patch, which will frequently cause WoW to freeze up when mousing over or clicking on almost anything that shows a cog. Mage tables, flags, anything of that sort can cause problems.

I had thought that some of my addons were causing the problem, as I noticed Deadly Boss Mods message load, then WoW immediately froze up. But after poking around the forums, it looks like it's on Blizz to fix it.