Thank you for being willing to ask this question. I think there are probably quite a few people who feel similarly, but haven't been willing to ask how to change.
First things first: don't insult people. There are a lot of really hard-working people on this site who work to make it an amazing resource for learning how to program and for fixing programming problems. If you insult people or say things that make them feel bad, they probably aren't going to want to help you.
Second, this site has a really high bar, and it can be really difficult to gain respect here. The moderators spend a lot of time digging through questions and trying to improve the site. Thus, questions that aren't up to standard can get downvoted pretty quickly, and it can be discouraging to have that happen many times. Even people like me who have been on the site a while mess up and post a thing or two that don't meet standards.
Just because your question is downvoted doesn't mean that it isn't valid. It just means that it's not in a good enough form that people here can really help you effectively.
So now to your real question: how can you change?
The biggest thing I've found to be helpful to this site is to ask a single question that can be answered objectively. The format I usually follow is
Give a brief overview of your problem
Pose your question
Explain what you've done to solve the problem (include links to other things
you've looked at if possible)
Pose your question again
Step (1) helps people to understand where you're coming from.
Step (2) helps people know what they should be looking for in the rest of your question.
Step (3) shows people that you aren't just using them as an instant resource; that you've done research and come here because you can't find your answer anywhere else and you think that people in this community might be able and willing to help you. If you provide links, those links can also help people who view your question to find solutions to similar problems, even if their problem isn't the exact same as yours.
Step (4) Clarifies what you want and tells people exactly how you'd like help. It needs to be a single question that addresses your core concern. (Sometimes it can be two questions, but they both need to address the exact some concern, just in different ways. For example: Why is <insert problem> happening? What can I do to fix it? Two questions. One core concern.)
I find that the hardest thing to do on this site is to come up with that one question. I thought that @Shog9 pointed out a great example of yours that I think a lot of people struggle with when they come to this site.
This question has too many questions. When I read this question, I find that I could answer What are char variables? (You've heard of them, but do you know what they are?) Or I could answer Do char variables have involvement in testing user input? Or I could answer Is using ActionListener to detect user input necessary? Etc. If you keep your post to one core issue, people are far more likely to be able to help you here because they'll understand what you want.
In the other question @Shog9 mentioned, you do this fairly well. It would be better if you had ended with something extremely clear, such as How can I get the plane to render in the correct position? (instead of So what is going on?).
Overall, the trick is to ask your questions in such a way that the people here are able to help you effectively and to do research so that people here feel valuable when answering questions instead of feeling like they're just doing your research for you.
Hopefully this helps you and many others feel more welcome here on Stack Overflow. It can be a hard place to start, but once you understand how to phrase your thoughts so people here can help, it can be a wonderful place to learn and exchange ideas. I wish you the best of luck.
