DuskMarine wrote: »
ZOS_GinaBruno wrote: »We've been working on a fix for this since it was discovered. At this time, the fix is going through QA and if it passes, we'll get it into the next incremental. It's not that we weren't prioritizing the issue (this is a big deal and we want it fixed as much as you all do), it was just complicated and took some time.