The key word in "debug my code" is my.
If the code being asked about is short, generic, and something which a lot of people are likely to have written in that form, then it's not a "debug my code" question.
Similarly, if the code you're asking about was written by someone else and is available to lots of people who might also have problems with it (for ...
You didn't list any particular questions as examples (the one question you link to never received a close vote), so I'm going to list some recent "too localized"-closed questions and discuss them. Here is a list of every question closed as "too localized" during the last 48 hours or so (as of when I posted this answer):
Rectangle collision is not working ...
This question has come up around our big sister Stack Overflow.
I like Kevin Bourrillion's guidelines:
How do I? -- StackOverflow!
I got this error, why? -- StackOverflow!
I got this error and I'm sure it's a bug -- file an issue!
I have an idea/request -- file an issue!
Why do you? -- the mailing list!
When will ...
"This question does not show any research effort; it is unclear, or not useful."
That's what the downvote tooltip says, and I say that's just fine for dealing with these. People don't like getting 5 downvotes; it makes them feel bad. So they'll either fix the question and learn how to do it right, or leave the site. Either way seems ok with me.
When all of these apply ...
When a code sample is given and the Asker is expecting the code to be "fixed".
When the solution to fixing the code is not useful to many others.
When the context of the code is "specialised" or specific to some particular context / scenario that others may not typically be met with programming.
Questions that meet some of these ...
Observation: Today, code-dump questions are being closed as "Too broad" where previously we were closing them as "Too localised". As I type this, there are four code-dump questions in the review queue. Each of these have attracted several "Too broad" votes, and no other votes.
I guess the mental logic behind voting code-dump as too broad goes something ...
Here are my suggested off topic reasons.:
Getting Started (though technically the "too broad" reason would apply, this one would be a much clearer way to close)
Which tech to use
Pure-programming question with nothing Gamedev-specific; should be migrated to SO.
plz debug mai codez
Here's a first-pass at the wording for these reasons (attempting to be ...
I would like to keep something in the spirit of the original too localized, because sometimes it was true.
"This question is unlikely to be helpful to any future users. It covers tiny typo errors, simple misuse of libraries, or custom code that will never be reused."
While some finds a question unworthy to even read through and votes to cast it to the seventh hell, others write really good answers for them that actually helps others.
No, that's not how it works.
The purpose of every Stack Exchange site is to help build a useable, searchable knowledge base. The fact that a question has "really good answers" is ...
I could've sworn there was a selection for "too localized" in the close options; maybe that was removed at some point, because I don't see it now.
Anyway I see "debug my code" questions as a specific variant of "too localized" questions: debugging your code helps you but not anybody else. Stated differently, if answering your question amounts to hunting ...
Well for one, you don't specify your platform. Pixel density (or probably more accurately described as "texel density") on a modern iPhone game vs. a PC game can be quite varied. It can also vary depending on what your desired min spec platform is or the kind of game you're making or the kind of tech you're using.
Texel density if you're using something ...
I agree, people are sometimes a little too gung-ho with that close vote.
Some questions I don't understand why people vote to close. Especially if there isn't really any explanation given or even down votes (question down votes are free these days so it's not like you'd lose rep).
Yes, at the end of the day, most questions are going to involve someone's "...
Is there a policy to discourage architectural questions in general?
No, we have the text "engine architecture" in the "What topics can I ask about here?" section on the 'on-topic' help page. There is also a healthy architecture tag.
Is there an existing policy to discourage best practices questions in general?
Yes. There was a discussion here on meta, ...
The questions are actually pretty different in my opinion.
The Unreal question is about using the interface provided by Unreal to modify the available components. In this case, it's a fairly large component, being the engine itself. This is a standard workflow task that everyone will come across when installing the engine.
The Unity question is asking how ...
As it's been stated here or in one of the links you posted, donwvotes should encourage bad questions posters to either delete or modify the question.
These questions don't technically fit in any 'close' categories, but as DMGregory suggested in this situation, a close vote with a 'custom' reason could take care of it. At this point, it's in the hands of ...
I see no practical benefit from a "no clear problem statement" close reason. We already cover these issues across two separate close reasons, and as such, a third would be redundant. Furthermore, I see conflicting issues in the mentioned examples; clear issues in why they should not really be closed for the mentioned reason, and clear issues in why they ...
Do we need a “no clear problem statement” close reason?
I don't think we do.
I think the
unclear what you're asking
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.
The new off topic mechanism is in place, and we only have space for 3 custom close reasons.
The top close reasons seem to be the following, so this is what I would propose:
"Which tech should I use to X" (off topic because it'll usually just be a list of answers. More detail here: Are "What should I use to do x?" questions really on-topic and ...
I think this happens to mostly 2 classes of questions.
1) The longwinded "do it for me" type questions, where they post [pages] of code and kinda shrug their shoulders and ask "So what's wrong with it?" Or, they post just a smidgen of code, then ask something which nobody could know without browsing the whole codebase. (The latter question type comes from ...
When I asked about getting a close option for free resource questions, I was informed that we get 3 custom close options and maybe a fourth under special circumstances.
I don't feel the benefit of gaining that option outweighs the loss of removing one of our other custom close options ("general programming should be on SO," "how to get started," and "...
The question is asking for legal advice.
We're not lawyers and this is not a legal advice site. Meta post
The question is asking if product X has feature Y, or if Y is doable with it.
It's a "what technology to use" in disguise, it doesn't age well, etc. Meta post
The question is asking what technology should be used to do X.
They're not very useful for ...