I think there are legitimate times to offer code. It's usually when it becomes apparent that the questioner is really trying to understand something. If there's a friendly back and forth of the questioner asking and the answerer giving contextual ideas or pseudo-code examples and the questioner still doesn't get it, then a blow-by-blow piece of code with good comments is awesome. Believe me -- it's awesome. (I remember being a newbie noob. Now I'm an old, intermediate noob, and it's still awesome when that happens.) I think it's pretty easy to tell when someone genuinely wants to learn. No one is forcing anyone to offer cut&paste solutions. Those that are dishing copypasta will eventually get tired of doing it when they see their efforts are futile. Why spend so much time and energy on someone who refuses to learn when you have your own programming on your own project to do? (This isn't any kind of solution, just me thinking out loud.) Personally, I don't see it as big of a problem as it's being made out to be, but I don't dismiss it as a non-concern either. I agree it should be addressed, as it has always been addressed by the community, at least from what I can remember. I've seen this happen in surges over the years, waxing and waning. The forum has had an influx of new programmers in the last several months, many of these newcomers with zero experience. They read the GameMaker gimmick line of, (paraphrased) "Make games quick and easy, no programming necessary!" They mess around with it and are either confounded and dismiss it altogether (we never hear from these people), or are instantly hooked, but either too young to "get it" or too "non-programmer" to follow the logic. So they have questions. Some of those questions are of the most basic. If you can't be fussed to answer them, then don't. Let it lie. Let someone else answer it. I really don't think there are that many in here trying to use GameMaker that don't want to learn it. Don't let a few bad apples spoil the whole barrel. The GMC had a wealth of answers for newbie beginners asking amazingly basic questions, but it's all archived and not very searchable now (what didn't get misplaced/lost). So now, the GMC has to start over answering all those newbie questions again, including that most amazingly basic of basic. This was talked about before the new forums were made. Many dismissed it as ever being a potential problem, but we may be seeing it rearing it's head now. My suggestion to people answering questions is similar to Bobs, by checking things off in a kind of order. If the first bit of advise doesn't work, try the next one down the line: 1. Offer an answer, but please explain it. For example, don't just write "Use collision_line" as your entire reply. Explain what to do with collision_line, how to implement it. 2. Share a link to the relative page in the help doc, and perhaps help explain what the help doc is probably failing to explain. Believe me, that help doc can be pretty convoluted sometimes with it's explanations. 3. If the conversation has gone this far, by now you should have a good grasp of whether the questioner is for real and wanting to learn, or just wants to eat the ice cream directly from the carton. This is when you decide to either help further by offering some code, or abandon the thread. A polite "I'm sorry, I'm unable to help you" is nice, but even that is not necessary. Just jump ship. Sometimes it takes a conversation to get a new programmer to a light bulb moment. That's what makes this a community. Conversation. If the questioner is unruly and ungrateful and demands copypasta, report it. (I believe this is what the OP was originally addressing - demanding copypasta.) What else can you do? Reply with a snide remark? "Gee, I wish I could get people to write all the code for my project and not have to learn anything." "Learn to read, like, help docs and stuff." "Next time, try some google sauce with your copypasta." These types of replies, though (possibly) humorous, will only cause more trouble. Corny tagline: I was a noob once. Still am. I'll forever be a noob, as there is always more to learn.