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.     

“Battle.net” Update

blizz -> wysłany:

We’re going to be transitioning away from using the Battle.net name for our gaming service and the functionality connected to it. Battle.net technology will continue to serve as the central nervous system for Blizzard games—nothing is changing in that regard. We'll just be referring to our various products and services using the Blizzard name instead. You've already seen this recently with things like "Blizzard Streaming" and "Blizzard Voice," and more changes are on the way.

When we created Battle.net, the idea of including a tailored online-gaming service together with your game was more of a novel concept, so we put a lot of focus on explaining what the service was and how it worked, including giving it a distinct name. Over time, though, we’ve seen that there’s been occasional confusion and inefficiencies related to having two separate identities under which everything falls—Blizzard and Battle.net. Given that built-in multiplayer support is a well-understood concept and more of a normal expectation these days, there isn’t as much of a need to maintain a separate identity for what is essentially our networking technology.

We just wanted to make sure everyone was aware as we moved forward with this change over the next several months; we’ll provide any relevant updates as the transition progresses.