Contact
GodotLearning is written and maintained by Mete Yengil. One inbox, read by Mete, handles everything: corrections, guide requests, reader games, privacy questions, and partnership notes.
contact@framedarc.comWhat to expect
Every message is read by a person. Corrections and broken-link reports are handled first, usually within a few business days, and the fixed page gets an updated modified date. Guide requests are collected and used to plan what we write next, so you may not get an individual reply for those, but the topic will not be lost.
Please do not send project secrets, API keys, or private client material. If you need to share a reproduction, a minimal Godot project on GitHub or a pasted script is enough.
Editorial standards
Mete Yengil maintains GodotLearning and handles content corrections. AI tools may assist with drafting, code, and illustrations. Each article’s review note states the Godot version, date, and scope of its documentation review. “Docs reviewed” does not mean the examples were run in the engine.
Selected GDScript examples have passed headless checks in Godot 4.7.2. Their revision notes describe the checks and what remains untested, including visible rendering and exports. A parse check only confirms that a script compiles in its supplied setup. Follow each example’s scene and input instructions; blocks labeled as fragments need surrounding project code.
Corrections update the article’s revision note and modified date while preserving its publication date. Documentation-review dates stay separate from editing and runtime checks. Source links let you check the engine guidance yourself. The About page explains our editorial responsibility and review labels.
No page on this site is sponsored, and coverage, recommendations, and links are not for sale. Advertising may help cover the site’s costs when available. Ads must stay separate from tutorial steps and have no influence on what a guide recommends.
Messages sent through the form on this page are handled by Netlify and used only to reply to you. They are not added to a mailing list, sold, or passed to an advertiser. The newsletter is a separate signup you have to opt into yourself, and the privacy policy covers which analytics and advertising cookies the site sets and how to refuse them.
Reporting a correction
If something here is wrong, saying so is the most useful message you can send. A correction is quickest to act on with four things: the page URL, the sentence or code block in question, the Godot version you are running, and what actually happened when you tried it. A minimal project on GitHub helps for anything involving more than one script, but a pasted snippet is usually enough.
Confirmed errors are fixed on the page itself rather than answered in a comment or buried in an erratum, and the fix ships with an updated modified date so a returning reader can tell the page moved. If a report turns out to be a difference in Godot versions rather than a mistake, the page gets a note saying which version does what.
Corrections
A snippet that no longer runs on Godot 4.7, a wrong node name, a broken link. Include the page URL and what you expected.
Guide requests
A migration pain point or Godot workflow you want explained. The more specific the project context, the better the guide.
Games you built
Shipped or prototyped something with Godot? Send a link and one line about how you built it. Reader games are featured on the site once a few have come in.
Privacy requests
Questions about analytics, advertising cookies, or a form submission you sent us. See the privacy policy for what we store.
Partnerships and press
Educational collaborations, links from courses or studios, and interview requests about migrating to Godot.
Send a message
Use the form or email contact@framedarc.com directly. The form is handled by Netlify and only used to reply to you.
Other places
- About GodotLearning: who runs the site and how guides are checked.
- Privacy policy: analytics, advertising cookies, and forms.
- Terms of use: how you may reuse tutorials and code samples.
- FAQ: common questions about learning Godot answered without email.
For engine bugs and general Godot help, the Godot Forum and GitHub issue tracker reach the engine maintainers directly; we are an independent learning site and cannot fix the engine itself.