Not sure if this is a real bug, but something I noticed when a guildie inspected me. The tool-tip displaying meta gem requirements appears gray/inactive when inspecting someone with one equipped. Basically, what's happening is the meta gem on the person you are inspecting is checking against *your* gems, not his.

When a guildie told me "your meta doesn't work", I showed him I had the requirements. Oh well, not game breaking but the problem exists.

There was a while (not sure if this has been fixed) where sets were broken the same way. Took me a minute to figure it out the first time I saw it.

This always happens if you have a 5cp rupture up and try to refresh it. I imgaine it also happens when you try to refresh any where the damage would be difference.

Kind of annoying somtimes

Small change. I noticed someone getting "drunk" in the AH, and it said:

Soandso is getting tipsy from [Rumsey Rum Black Laber] or whatever. Basically it seems to announce what your getting drunk from.

It really suprises me that bugs as large as:

- The metagem inspect thing (predictable, has happened and been fixed before)
- Arcane shot dispelling all buffs
- Not rolling in BT boss hotfixes into this build (also a previous problem they've had)

Get through. I work in Tech and understand the restrictions of QA. But Blizz must (should!) have a fairly huge team checking a fairly huge range of stuff. I'd understand if many minor bugs got through, but the major ones always baffle me. Especially ones that clearly fall on the side of "must fix ASAP" vs "internally known, but shouldn't delay patch launch"

Actually, it doesn't ALWAYS happen. It happens when you applied a rupture with more attack power than you have when trying to overwrite that rupture. Since rupture is affected by AP, if you had mongoose procs, or unleashed rage, when applying the first rupture, but didn't have the same or greater buffs when trying to overwrite it, you have to wait for the more powerful rupture to drop.

This happened before 2.3. If you ruptured while Mongoose was up, or during a Windfury proc, then you couldn't overwrite it with another.

Our entire raid had a complete game freeze on supremus - twice, a freeze where you have to force the game to close and reconnect.. only happens on supremus and to everyone in raid.

Not my experience. Prospected 25 stacks earlier tonight and it was the same as ever with regard to looting.

This is probably going to sound stupid, but you do have the right auto-loot settings enabled? I do and it most definitely auto-looted correctly. I prospected about 40 stacks last night as gem prices are through the roof right now (as are many other things)

If you inspect a warrior or rogue, any talents they have that have multiple ranks will not show up as having been trained if they have a higher rank than the base rank of the talent. Appears to be an issue with the fact that for rogues and warriors, higher ranks of spells replace lower ranks.