Search for the answer
Before asking a question, check Godot Docs and use the Forum Search functionality to make sure your question hasn’t been answered or there isn’t an ongoing discussion on that topic already.
If you don’t know where to start, try here: Getting started, Your first 2D game, Your first 3D game.
Create a good post
Click on each point to expand.
1. Write a good topic title
Give the topic a descriptive title that captures the problem accurately - it’s the first thing people will see of your help topic. Use specific keywords that describe the problem in the most concise way and avoid redundant words, like “help” and “please”.
“Problem with CharacterBody2D. PLEASE HELP!” is a bad title.
“CharacterBody2D doesn’t trigger collision during move_and_slide()” is better.
2. Use the template
Use the Help topic template - fill in the Godot version you’re using, any plugin versions, describe your problem thoroughly, include all relevant code snippets (properly formatted - see the next point), scene tree screenshots, video of incorrect behavior if applicable, etc. The more relevant information you provide, the better answer can be provided.
3. Format your code
Post all relevant code snippets and format it properly, do not post screenshots of code.
There are a few different ways to format code:
- Wrap it in triple backticks (```) above and below the code to create a
code block. Adding “gd” for GDScript or “cs” for C# after the top set will nicely color your code and make it easier to read. - Press the Preformatted Text button
</>in the toolbar. - Press Ctrl + E on your keyboard.
This:
```gd
func _ready() -> void:
print("hello world")
```
Turns into this:
func _ready() -> void:
print("hello world")
Describe your problem
Explain the problem you’re having in details, using the 7 questions below to guide you.
Click on each point to expand.
1. What problem are you having?
Tell us the problem you are trying to solve. Try to avoid the XY Problem by thoroughly describing the actual problem and your desired outcome, without asking about your attempted solution.
2. What did you expect to happen?
It may not be obvious to your readers what you think should happen, so tell us. Don’t assume that the reader has played the same games as you or watched the same tutorials. Don’t expect anyone to watch a 30 minute tutorial video to see where you went wrong. When a video is integral to the problem, make sure to specify which exact part of the video is relevant, e.g. “from 1m20s to 2m30s”.
3. How and when did the problem arise?
Was this working before? On an earlier version of Godot? Or before you made a change? Did you update your video drivers recently or make other changes to your computer?
4. What steps have you taken to fix the problem?
Tell us what you’ve done to try to fix the problem to avoid receiving an obvious answer that you have already tried and didn’t work. Showing that you have spent time trying to solve the problem is more likely to get you more thoughtful responses in return.
5. What error messages have you gotten?
You can copy messages from the editor directly and paste them into your post. That gives us information to help you - even if it seems unimportant or nonsense to you. Do not use screenshots. They are harder to read and make it harder to do more research about the error.
6. What does your Editor look like?
Add screenshots of your Scene Tree, Inspector and/or the whole Editor if you think it might be relevant. If you are new to the forum, you can make replies to your own post to add additional screenshots after the first. Do not try and recreate your Scene Tree in text. There are things we can see by the icon or color of an icon, warnings and other things that you may not notice but can help us solve your problem.
7. How does your post look?
Before posting, re-read your question to make sure it’s clear and presentable - then hit Create Topic, lean back, and wait for help to arrive. If you later notice something that can be improved, you can edit your topic.