Return to Answer

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the What's a "minimum complete verifiable example" (MCVE) and how do I provide it? meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the What's a "minimum complete verifiable example" (MCVE) and how do I provide it? meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the http://meta.gamedev.stackexchange.com/questions/2201/whats-a-minimum-complete-verifiable-example-mcve-and-how-do-i-provide-it meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the What's a "minimum complete verifiable example" (MCVE) and how do I provide it? meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the http://meta.gamedev.stackexchange.com/questions/2201/whats-a-minimum-complete-verifiable-example-mcve-and-how-do-i-provide-it meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.

I think we should change the reason to include wording requiring a minimal example that would reproduce the problem. I've created the http://meta.gamedev.stackexchange.com/questions/2201/whats-a-minimum-complete-verifiable-example-mcve-and-how-do-i-provide-it meta post, cribbed from the StackOverflow help pages (an idea I stole from Vi and Vim), which we can use to request users provide such an example. I propose we update the close reason text as follows:

Questions about debugging a problem must provide a minimal, complete, verifiable example of the issue so that readers can diagnose it without needing to guess, read all of your code, or engage in extensive back-and-forth dialog. For more information, see this meta thread.