I think two things are important to note here:
- the question is not closed - only one person has voted with that close reason
- you can vote to "leave open".
This is the system working the way it is supposed to work. Someone sees a problem, uses a custom close reason, and votes to close. Only if others in the community agree with that close reason will that close reason be applied to the question.
Did you vote to "leave open"?
In a sense, this meta question is being asked "too soon"... and should only be asked if the community has already closed the question.
As an aside, the custom comment would not normally be appropriate for a close reason, I agree, but in this case (and partially because this question is brought up on meta, and because our "top answerer" in the past 30 days (and 2nd all-time) is the person who voted to close, I have looked more carefully at the question....
I believe the close reason reflects what is a somewhat accurate interpretation of what we consider to be off-topic for this site:
Do I want the code to be good code? (i.e. not code-golfing, obfuscation, or similar)
in this case, the opening sentence for the question is:
I tried to make this clone of brick_breaker on my own in one day.
Is that "wanting the code to be good code"?
I downloaded the code, I pulled the "rar" file of resources. The code works, mostly. Enough for me to say it passed a "sniff test", but I can also say that the review is not being asked for in the spirit of this site. We hope for people to produce their best work, which we then review, not for people to throw stuff together in a hurry and ask us to be the "gatekeepers" of sanity.