Some bug I assume??

[greenoaks]

And somebody should fix the underlying problem. This update is clearly not appreciated by the TO's, why else would the natural response be that it must be some kind of bug?

It's already been stated somewhere else that they are working on a fix for this.

I'm hoping it will come soon.

working, they were made aware this would be a problem 1 month prior to implementing this

[chapcrap]

And somebody should fix the underlying problem. This update is clearly not appreciated by the TO's, why else would the natural response be that it must be some kind of bug?

It's already been stated somewhere else that they are working on a fix for this.

I'm hoping it will come soon.

working, they were made aware this would be a problem 1 month prior to implementing this

I don't disagree with you.

[Night Strike]

So everyone's clear, none of the TDs can do anything about this, so continually posting about it won't help. I've already been told by rds that it should be fixed by the end of the week but hopefully sooner. He's pestering the coder to get it fixed, and if the deadline passes, I'll bug him again for a fix. The TDs were not involved in submitting or consulting on the update that caused the problem, so we were just as in the dark about it going to happen as you all were.

[greenoaks]

So everyone's clear, none of the TDs can do anything about this, so continually posting about it won't help. I've already been told by rds that it should be fixed by the end of the week but hopefully sooner. He's pestering the coder to get it fixed, and if the deadline passes, I'll bug him again for a fix. The TDs were not involved in submitting or consulting on the update that caused the problem, so we were just as in the dark about it going to happen as you all were.

i wasn't aware anyone thought you guys had anything to do with this.

why weren't you asked to give input/feedback?

[Night Strike]

So everyone's clear, none of the TDs can do anything about this, so continually posting about it won't help. I've already been told by rds that it should be fixed by the end of the week but hopefully sooner. He's pestering the coder to get it fixed, and if the deadline passes, I'll bug him again for a fix. The TDs were not involved in submitting or consulting on the update that caused the problem, so we were just as in the dark about it going to happen as you all were.

i wasn't aware anyone thought you guys had anything to do with this.

why weren't you asked to give input/feedback?

I'm guessing they were just worried about making public games easier to find and didn't think there could be a bad result for tournament organizers and others.