I'm tired of seeing terrible Minecraft crash log questions. I'm tired of closing them. I'm tired of posting comments asking for a shred of useful material. Tired of seeing the same errors repeatedly.
But nevermind being tired, there's coffee for that!
What's really damning, in my eyes, is that we're terrible at answering these questions, as a community. The Q&A format doesn't really suit them: we close them and then either
- go back and forth in the comments, trying to troubleshoot the problem until the problem is solved, and then someone an answer just to maintain the Q&A form, or
- we ignore the terrible question.
Number 1 indicates that, maybe, these are actually off topic. (Number 2 is just growing apathy.) We're quality for lots of things, but this doesn't appear to be one of them. Generally, if a question requires lots of back-and-forth to diagnose the problem, it's a forum question, not a Stack question.
Worse, is that growing apathy. Our mandate is to curate good questions that make experts want to be here to write good answers. Entertaining questions that are evidently increasing the apathy of Minecraft experts, might undermining that mandate. It's certainly making me tired, speaking as one of the two userstwo users with the minecraft tag gold badge.
This has been discussed before, but if anything the problem is subjectively worse now rather than better. There are only really two kinds of Minecraft questions that come in these days: terrible crash questions and command block questions. That's not really a pretty picture.
Should Minecraft crash questions be thrown out with the trash: yes or no?
And if "no"... we need a plan, stat, to make them less rubbish, or we really should be saying "yes."
