Hey -
I checked in this morning with the team, and we do not have an official ETA.
For some context on how this process works, particular in this case,
-
We receive the reports that it's not working.
-
Reproduce the issue on our end and create a ticket.
-
Developers (resources vary based on what needs to be fixed - for this, it's more of a designer/engineer aspect) start investigating the issue and look for the root cause. This could be an issue in the script, an issue with code, or various other scenarios. It can take longer for some issues than others when tracking down a root cause.
-
We find the root cause. (Hooray!) Now, we begin the task of fixing the issue, which again, time can vary, depending on what's going on.
-
Developer has a fix. QA verifies the fix is working on an internal platform. QA also verifies that this fix won't break anything else - so for Thresh, we're checking that we aren't overwriting any files, we aren't breaking something else in the process, things like that.
-
If the fix works, we move it to an external environment, something like PBE where it's considered a full build (something players would play on - as live of an environment we can get without it actually going to live itself). We test in several locations to ensure the fix isn't failing once it's in a full build. (Issues can work on an internal platform, but goof up once built out. We do this with all bugs we fix, actually!)
-
If the fix fails, we're looking to repeat some of the previous steps, which is why getting a fix for something can take longer than most would expect.
Again, we do apologize for the inconvenience here - we know it sucks not being able to play the content you've been waiting for, or have already purchased.
On our side, we want to make sure the fix that we push to live (via small patch / hot fix, whatever you'd like to call it), works, so that we can turn him on and get everyone back on the Rift, supporting in style.
I hope this post at least informs you a bit more about the process of how this has been going down, and to give a bit more clarity, rather than remaining silent on the issue.
I realize this isn't the answer you're looking for 'cause I don't have an ETA for you (and again, I'm super sorry about that), but I'm happy to keep a healthy conversation going around this and posting any additional information I'm able to provide.