Aug 18th 2009 8:38AM I kept forgetting to use Inner Fire on my priest. I'd cast it occasionally, it would drop, I wouldn't notice. Since it's a major armor boost and my priest is shadow, I do get hit from time to time and that can make a huge difference. I fixed it by loading the addon PriestFriend, which among other things reminds me when Inner Fire has dropped.
May 5th 2009 8:30AM Having been a GM in Everquest, I would have immediately recognized this item for what it was. As soon as I heard about this case, I knew that he'd had a GM/developer item given to him by mistake. I had similar items of gear myself on my GM avatar, all of which had very specific rules regarding its use. An item like that wasn't meant to clear major instances (in fact, EQ GMs had strict internal rules about never "interacting" with any NPCs unnecessarily, and I suspect WoW GMs have similar strictures) -- they are meant to do things like eliminate a bugged mob so it would respawn properly. This was commonly done for zones where mobs routinely got stuck under the world or inside geography; there were mobs well known for this behavior and until the developers could fix it, it was the only way to deal with it.
Even the name screams "GM item". Many had goofy names like that, and many were named after developers or producers.
It was almost certainly not an intentional return. Likely what happened is that the person responsible for returning the items input the wrong item ID, wasn't paying attention and didn't double check. Like, for example, Item 1711 is a Scroll of Stamina II and 1777 is Brocade Shoulders. Tired, distracted, or sticky keyboard -- it could happen.
If the player had taken the item, walked into an instance, and tried it out just to see if it worked, that would have been fine, IMHO, and probably totally expected given natural human curiosity. But keeping it and doing runs for a WEEK is clearly taking advantage of a situation. The person knew he was having items restored and this item clearly did not belong to him prior to this.
Feb 16th 2009 10:03AM Yes, I finished, but I know many, many people who did not. This event was too short and the candy quest in particular was obviously far too random. I do not like achievements based on how many times you can log in and how lucky you are when you do.