Mainloop25 said: One of those baffling questions that have been asked many times, and never got a good response to.
shteev said: I imagine Brigby will show up in a bit and ask us if we can help collate some data so we can fix the problem
Volrak said: shteev said: I imagine Brigby will show up in a bit and ask us if we can help collate some data so we can fix the problem D3 reaching out is a positive thing, and the existence of some other negative thing (bugs), combined with the lack of existence of a further positive thing (good QA practices) doesn't change that.
Ohboy said: Yes, that's true and all, but you're forgetting one thing. We don't use logic here. No seriously, I've actually been told by a mod that pointing out logical fallacies is an offence.
Matthew said: Ohboy said: Yes, that's true and all, but you're forgetting one thing. We don't use logic here. No seriously, I've actually been told by a mod that pointing out logical fallacies is an offence. You can't be serious...
Brigby said: Actually when it comes to the card Cast Out, there is a fix in 2.2 that will prevent it from erroneously casting when you select "Not Now."I know it's not exactly the same scenario as @Phillmoore's original post, but it's similar and relevant enough that I figured I'd mention it
Ohboy said: Brigby said: Actually when it comes to the card Cast Out, there is a fix in 2.2 that will prevent it from erroneously casting when you select "Not Now."I know it's not exactly the same scenario as @Phillmoore's original post, but it's similar and relevant enough that I figured I'd mention it And now I want to know lilianna's oath got changed too. It's the consistency that matters. This just makes things more unpredictable.
Brigby said: Actually when it comes to the card Cast Out, there is a fix in 2.2 that will prevent it from erroneously casting when you select "Not Now."
bken1234 said: I don't think that should be the case with a support - they should auto cast.