Skip to main content
Tweeted twitter.com/StackRPG/status/1371430996214702087
edited tags
Link
V2Blast Mod
  • 50.3k
  • 1
  • 24
  • 51
added 9 characters in body
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others.

There is no reason to close that question. None.

Thanks to the help of NautArch and Doppelgreener, we can see that the closuresclosure votes come after the newest deleted answer was posted. ?

In an attempt to prevent further erroneous close votes, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up:
Per the linked timeline, the question popped into the review queue thanks to a new answer of unimpressive quality that has received at least one down vote. That's not a bad response, but closing that particular question is a bad response. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years isare good, on topic, and useful.

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others.

There is no reason to close that question. None.

Thanks to the help of NautArch and Doppelgreener, we can see that the closures come after the newest deleted answer was posted. ?

In an attempt to prevent further erroneous close votes, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up:
Per the linked timeline, the question popped into the review queue thanks to a new answer of unimpressive quality that has received at least one down vote. That's not a bad response, but closing that particular question is a bad response. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years is good, on topic, and useful.

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others.

There is no reason to close that question. None.

Thanks to the help of NautArch and Doppelgreener, we can see that the closure votes come after the newest deleted answer was posted. ?

In an attempt to prevent further erroneous close votes, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up:
Per the linked timeline, the question popped into the review queue thanks to a new answer of unimpressive quality that has received at least one down vote. That's not a bad response, but closing that particular question is a bad response. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years are good, on topic, and useful.

added 238 characters in body
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others. There

There is no reason to close that question. None.

Thanks to the help of NautArch and Doppelgreener, we can see that the closures come after the newest deleted answer was posted. ?

In an attempt to prevent further vandalismerroneous close votes, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up:
Per the linked timeline, the question seems to have popped into the review queue thanks to a new answer of unimpressive qualityof unimpressive quality that has received at least one down vote. That's That's not a bad response, but closing that particular question isis a bad response. The arrival of a bad answer is not a good reason to close that question. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years is good, on topic, and useful.

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others. There is no reason to close that question. None.

In an attempt to prevent further vandalism, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up: the question seems to have popped into the review queue thanks to a new answer of unimpressive quality that has received at least one down vote. That's not a bad response, but closing that particular question is a bad response. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years is good, on topic, and useful.

I am seeing a trend that is well illustrated by this question, where our reviewers seem to be forgetting about our meta discussion a while back about the word Should.

There is no need to close that very useful question about what the best info is on a DM screen. I am pretty sure that either the term should informed the reaction to it, or that an erroneous "that's a tool-rec question" assessment was made. The use of a DM screen is a 40+ year old habit in our hobby, not just in D&D, and the person's problem to solve is "what is the best info to have there" and the accepted answer clarifies that nicely. So do a few of the others.

There is no reason to close that question. None.

Thanks to the help of NautArch and Doppelgreener, we can see that the closures come after the newest deleted answer was posted. ?

In an attempt to prevent further erroneous close votes, I felt obliged to remove the term "should" via an edit to forestall further wrongful review responses. I am calling on all reviewers to take a little more care in their efforts.

And, please, everyone, read and Review the Meta that @Someone_Evil posted about the word Should a while back.

Note on the question that got me to speak up:
Per the linked timeline, the question popped into the review queue thanks to a new answer of unimpressive quality that has received at least one down vote. That's not a bad response, but closing that particular question is a bad response. The arrival of a bad answer is not a good reason to close that question. The question and the answers that have sat there for Over Five Years is good, on topic, and useful.

Became Hot Meta Post
edited title
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75
Loading
added 460 characters in body
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75
Loading
deleted 16 characters in body
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75
Loading
added 138 characters in body
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75
Loading
Source Link
KorvinStarmast
  • 144.3k
  • 1
  • 37
  • 75
Loading