WoWCenter.pl
wikass zabił Mythrax the Unraveler (Normal Uldir) po raz 2.     
kuturin zdobył 7th Legionnaire's Cuffs.     
Nikandra spełnił kryterium Loot 200,000 gold osiągnięcia Got My Mind On My Money.     
Tooly zdobył Fairweather Helm.     
Muattin zdobył osiągnięcie The Dirty Five.     
Yoozku zdobył Parrotfeather Cloak.     
Mlody89 zdobył Royal Apothecary Drape.     
Weakness zabił Dazar, The First King (Mythic King's Rest) po raz 6.     
liq spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Osiol spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Wuntu zabił Zek'voz, Herald of N'zoth (Heroic Uldir) po raz 1.     
Olsa zabił Vectis (Heroic Uldir) po raz 6.     
Sarenus spełnił kryterium osiągnięcia Saving for a Rainy Day.     
kajtasus zdobył osiągnięcie Come Sail Away.     
ossir spełnił kryterium osiągnięcia Saving for a Rainy Day.     
mcpablo spełnił kryterium Alliance players slain. osiągnięcia Frontline Slayer.     
Emmm zabił Taloc (Heroic Uldir) po raz 17.     
AsaGorth spełnił kryterium Big-Mouth Clam osiągnięcia The Oceanographer.     

Bug with Sanguinary Veins and two rogues

blizz -> wysłany:
http://tinyurl.com/pfaxyle (Ravenholdt.net blog)

The tl;dr is that if you have two subtlety rogues, only one will ever benefit from sanguinary vein, which both increases rupture damage by 10% and all other damage by 20% for enemies affected by a rogue bleed. Whichever rogue applied a bleed most recently will get the effect, while the other will not benefit until they refresh their own bleed.
blizz -> wysłany:
We're working on a hotfix for this. I don't have an ETA yet on when it will be released, but we'll get it done.
blizz -> wysłany:
02/17/2015 01:23 PMPosted by Kane
It still raises the issue that Fierydemise pointed out at the end of the post - unless you go screaming on the forums, or raise a big "hey! hey! bug!" this stuff doesn't appear to be even looked at. The fact it got such a speedy response and incoming hotfix lends credence to it.


To speak to this, if it was indeed reported using the in-game feature, I'm not sure how it slipped through the cracks. I don't handle the in-game bug reports myself so I can't speak directly to how it could have happened, but it's definitely a fail on our part if we got reports on a bug like this and managed to miss them somehow.

We're extremely grateful to people like Fierydemise for pointing stuff like this out, but you're correct that it shouldn't be necessary. In the vast majority of cases, it isn't. In fact, I'm not 100% sure that the Ravenholdt post was what got this bug fixed (it seems likely, but I haven't asked the developer who's working on the fix where they heard about the bug because, well, it seems like actually working on the fix would be a better use of their time).

But we identify and fix a ton of bugs due to player reports -- this one just slipped through the cracks somehow. That sucks and is obviously our fault, but it's definitely the exception and not the rule.
blizz -> wysłany:
Hotfix has just been applied. It might take a few minutes to completely roll out everywhere, but should be active shortly if it's not already.