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.     

New Broken Isle CRZ is ruining the game.

blizz -> wysłany:
Hey everyone,

Thanks for all of your feedback on this. We've identified an issue that is causing some unintentional cross-realm coalescing to take place across many Legion zones (including Order Halls).

We are currently working on a fix that should resolve this issue, and I'll update this thread when I hear more.

Thanks for your patience!
blizz -> wysłany:
09/07/2016 11:34 AMPosted by Valangrr
09/07/2016 11:28 AMPosted by Ornyx
Hey everyone,

Thanks for all of your feedback on this. We've identified an issue that is causing some unintentional cross-realm coalescing to take place across many Legion zones (including Order Halls).

We are currently working on a fix that should resolve this issue, and I'll update this thread when I hear more.

Thanks for your patience!


Day and a half and counting with no fix, only just now getting them started on a fix.. Always good to see. :\

It does take some time to notice the issue (ie. this thread, etc), investigate the issue, figure out what caused it, create a fix, test the fix, and then implement it.

Again, we appreciate everyone's patience.
blizz -> wysłany:
<span class="truncated">...</span>
It does take some time to notice the issue (ie. this thread, etc), investigate the issue, figure out what caused it, create a fix, test the fix, and then implement it.

Again, we appreciate everyone's patience.


So what you're saying is there was no one monitoring the threads yesterday, yet you posted on the forums yesterday and easily could have seen and probably did see this thread but chose to not post.

We do not always post in every thread, no. I do not have immediate insight when I see a thread on what every developer will think about the issue.

But I do read everything and forward things along, but when topics are as hot as this one was yesterday, touching it without definite answers can create more problems.

This can lead to people having expectations of fixes being implemented as they desire, when we may choose to do something different - all this only by a post saying something not-so-reassuring like "we are looking into this."

Sometimes it is better to make sure we have a resolution to an issue before we share information on the topic, albeit this doesn't always apply and definitely is not always the case, as many here know.

In this process:

It does take some time to notice the issue (ie. this thread, etc), investigate the issue, figure out what caused it, create a fix, test the fix, and then implement it.

We are likely to inform players when the topic is heated once we reach the "create a fix" stage, to be sure we can actually address it.