Morning again everybody,
Work continues on this. Nothing major to share other than answers to some questions and comments that have been popping up recently.
Some people in the thread have asked if people are in office on weekend are working on this. We do have QA trying to prep a fix for this ASAP but because of the amount of work needed and the fact that it needs a new game build, it likely won’t be ready this weekend. I don’t have anything else of importance to share at the moment other than the fact that this is a top priority for us.
Some have been asking about refunds as well. While we are working hard on this, we also understand if you’re unsatisfied based on this bug preventing you from playing. You can request a refund here.
There’s also some comments regarding something I mentioned previously, quoting myself. “There’s currently another major issue taking priority over this.” I wanted to take some time to own that mistake in phrasing. Ultimately I didn’t mean to express that your issue wasn’t important to us as much as set appropriate expectations, but I understand that I could have communicated that better. When that was mentioned there were mass server issues that we needed to fix up before most of our developers could focus on other tasks. Even while that was true, we had some engineers free who were gathering information from the thread and looking into things. So, sorry if that made anybody feel that this was being treated as unimportant.
Hopefully this provides a bit more clarification. In the mean time, here’s the relevant information from the most recent CM post regarding the issue on Friday.