Lack of help in simple requests

Yes it is hard to write working code with max 10 letters.

No, not everyone needs to learn PHP.

Most of the time that is because the question is not clear, the person didn't provide any code etc.... When someone want to make a plugin he/she should also put some effort in it. Most if not all of the questions can be answered by looking at the PocketMine-MP source.

It's not hard to look at the PocketMine-MP source code, why don't people do that? The source code is the best place to look for code examples.

BTW: https://forums.pmmp.io/threads/readme.16/ Nobody reads the readme!

 

Moving to Facepalm section doesn't mean your thread is ignored, censored or banned. Usually, such questions are moved to Facepalm section similar to "Closed" questions on StackOverflow:

Spoiler: StackOverflow question closing interface

Particularly, those threads are usually:

• Duplicate. Moving to Facepalm simply means future readers won't want to read it as a helpful thread. It's not locked. Helpful forum members should post a link to the thread that it duplicates. Sometimes the asker doesn't know it's a duplicate because some errors happen all the time but all the description would be very specific, and it's difficult to search them. However, it's not going to be useful for future readers since it's a duplicate, and we want to keep the Development forum index to list only high-quality or useful threads. For duplicates, which would be useless to anyone else once solved, they are moved to the Facepalm section so that nobody will try to dig them out once all the participating parties consider it as resolved.
• Too broad. "How to make a proxy?" "How to make a CTF plugin?" "How to make antihacks?" "How to write a plugin?" Such questions are too broad. Yes, it's possible to answer your question, but it's too much. How to make a proxy? You create a UDP socket, accept client packets, parse the RakNet packets, handle the login, determine the destination server, setup a bridge between the proxy and the destination, wrap the packets through the bridge, and let the destination unwrap the packets and handle them as a new connection, passing other client data like IP address. How do you actually do these? By the time I finished explaining it, I've already finished the proxy server software. A detailed, high-quality answer is simply too long, and I even doubt if the asker would read it.
• Too specific. Actually off-topic. In good cases, you have a minor typo somewhere, and you would even yourself after you find out the cause of the error, so why can't others? You are still allowed to reply to that thread, just that we don't like seeing such questions again because we don't want more people to you (It's not useful to anyone else!). In bad cases, you simply don't understand what code you are writing and you paste the error and let others fix it for you without understanding what gets fixed. If all that you are doing is to mix and match different code snippets, why don't we write the whole working plugin before sending it to you? We want to help, but we aren't paid, and we want to avoid boring work. Opening the tap, letting the water run over the dishes and letting them dry is a fun thing to do the first time, but who wants to wash dishes for their whole life? Fixing uglily-mixed-together code all the time is more tiring than washing dishes indeed -- at least, you won't see the dishes you washed getting dirty again immediately.
  • I'm mainly referring to syntax errors and trivial errors. It's simply so boring to look at them all day.
    
• Too vague. You aren't asking us how to do something; you are asking to do something. It's unclear what exactly you are asking -- your question depends on your context a lot, and if you don't provide them, you aren't asking a development question but requesting a plugin. For example, "How to let player leave a team"? Well, how did the player join the team in the first place? Most likely you copied the join-team code, but it totally depends how you store the teams, so nobody can help you at all.

In general, most Facepalm threads are caused by the author not understanding the code he provided because he just copied them. You may know how to "return false;", but do you even understand what they mean? Do you know what "return" means, why you need to return something or who receives the returned value, and why it is "false"? You may know you can create command handlers in other classes, but do you even know what "extends Command" or "extends PluginCommand" or "implements CommandExecutor" mean? You may know that you can move all event listeners to another class, but do you know what a class means? If you have tried to understand, refactor and rewrite something that you are trying to copy, 99% [citation needed, might have been 100%] threads in the Facepalm section should not have been posted.

PHP:

return true;

Oops, exactly 10 letters (not characters/bytes!)

I hope so. Did you try to find it at all? Or did you find it at the wrong direction? If it's at the wrong direction, maybe you should rephrase your question and ask how you can find out the error instead of how this error can be fixed.

And they usually aren't in the Facepalm section.

citation needed.

I take this as a typo. I assume you meant "10 lines".
Yes, very hard. Providing no context, we have to remake your context. Providing your whole plugin, we have to understand your plugin's structure (code quality problem again -- if your plugin is just a big piece of code snippets from the forums gathered together, there's no structure to understand at all).
This is not a code writing service. We provide knowledge, not code (otherwise go to the Requests section). Code is a good medium to elaborate your points, but not always. After seeing many people just copy the code, we realize that providing code only leads to distraction rather than comprehension.

 

Yep, you need a line of exit(127); somewhere.

 

Indeed. So many people just write the code and let people copy them, without even trying to explain or to guide people writing it. They're degrading themselves as code-writing robots.