HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
godotengine
godot
C++2014–2026
godotengine / godot

godot

Godot Engine – Multi-platform 2D and 3D game engine

100Distinct people
116Mentions
1Explicit recommenders
120.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Godot Engine – Multi-platform 2D and 3D game engine

GitHub

Where it is used

  • Material Maker — Material Maker uses Godot to build its open-source application for creating materials and textures. It is a shipped app showcased by the Godot project. Source
  • Cassette Beasts — Cassette Beasts uses the Godot Engine as the game’s engine. The developers describe choosing and settling on Godot for the project. Source

What people are saying

I've been building a game part-time in Godot[0] and I contribute to the code on occasion. For the most part it has been a pleasant experience[1]. It currently does not have the…

cart_cart used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:59:22 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year116 dated mentions

Observed mentions: 2014-02-10 05:36:11 UTC to 2026-07-23 17:08:42 UTC.

051015202014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 1 submissions, 13 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 18 mentions; 2 submissions, 16 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC404
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC615
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC321
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1019
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC14014
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC14113
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC18216
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12210
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC14311
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC11110

What Hacker News says

14 sources
Seems like Godot already does what Blender Apps does much better: - Godot is great at importing Blender models/scenes. - Blender is GPL, Godot is MIT. - Godot produces much lighter .exe files. Blender Apps are at least 200MB. - Godot has web export, too. Godot still has stability issues that can affect larger projects (presently over 7000 open issues on Github[1]) but for smaller demos and art things Godot usually is pretty solid. [1] https://github.com/godotengine/godot/issues
In Blender Apps
I am really looking forward to Godot 4. GDScript improved a lot. I'm mostly excited about callables (function pointers), easier signal handling in combination with await (former yields) and an improved tweening system. The scripting environment inside of the editor with inbuilt documentation, code completion and debugger is really an achievement. The only thing I miss are static typing and refactoring tools. You can use type hints, but you need to fall back to dynamic typing at some places for example because there are no generic collections. Therefore I'm quite excited about the dotnet6 branch being merged into main a few days ago [1]. This is a huge step and will probably make some unity developers consider Godot for their next game. Also there's GDExtension, the successor of GDNative, which will make it easier to integrate C++ code [2]
Read the rest
. I could never imagine myself using Visual Scripting, because you can express yourself so much easier in Code. [1] https://github.com/godotengine/godot/pull/64089 [2] https://godotengine.org/article/introducing-gd-extensions
In Godot 4.0 will discontinue visual scripting
> ...you are requested to delete The Machinery source code and binaries. This is pretty weird. Then again, in regards to the engine itself dying, I feel like this is inevitable for many of the projects out there. For example, there was the Xenko engine which was later renamed to Stride: https://www.stride3d.net/ It's actually a nice project, has lots of great features and feels like it should be a more open alternative to Unity, whilst being similarly easy to use. However, compare the attention it is getting in comparison to something like Godot: - https://github.com/stride3d/stride - https://github.com/godotengine/godot On OpenCollective, Stride has an estimated annual budget of around 12k USD, whereas Godot gets around 15k USD per month on Patreon. Stride has a bit under 100 contributors, Godot has almost 2000. Godot gets hype on v
Read the rest
arious game development subreddits regularly, yet Stride gets no such love. Ergo, it's probably pretty easy to draw a trajectory of what the next 10 years might bring for either, with one probably getting more features and development and becoming a mainstay of the indie scene, when compared to the other. But the great thing is that if whatever engine you use has an open license, you cannot have it be taken away from you (as long as you have all of the actual executables and don't depend on external services).
In End of the Machinery Game Engine
After quickly falling in love with Godot and several months of serious use I'm having to give up on it due to Godot's lack of funding to fix its more than 6000 open issues on Github: https://github.com/godotengine/godot/issues Every single time a Godot bug bites me I find that a bunch of other devs reported the issue more than a year ago but no one has had time/money to fix the issue. For example, I was just bitten by #45628 opened Feb 1, 2021: https://github.com/godotengine/godot/issues/45628 When implementing controller support for a top-down Zelda-like game, it's normal to allow either the d-pad or left analog stick to control direction. But if you enable both at the same time in Godot then d-pad inputs cause your character to "freeze". Eventually Godot will stabilize and be to game engines what Blender currently is to 3D modeler
Read the rest
s. If I had time to learn the Godot C++ code I would volunteer to help but I want to actually make video games instead of working on an engine.
In Godot 4.0 development enters feature freeze ahead of the first beta
Yep. Similar numbers of assets, similar sizes of assets, etc. Things that would cause Unity to keel over and die were virtually instantaneous in Godot. I had a project with something like 10k game objects in Godot with no major issues. Actually, there was one issue where saving was taking like 5 seconds in Godot instead of being instantaneous. I reported it and it was solved in the next point version. https://github.com/godotengine/godot/pull/49570
In It’s time to make that indie C# game in Godot
For the curious, this seems to be the issue: https://github.com/godotengine/godot/issues/32383 The thread is a bit messy, but it was eventually fixed in 3.4 it seems. It's a serious engine problem, and I can understand getting frustrated/put off by it if you have a bad personal experience (and in general I find deleting nodes in Godot to be surprisingly footgun-ish) but from my PoV it did eventually get solved, so that speaks to something. If not in a timely fashion (but given that I've let bug reports on some of my open source projects, including pull requests, dangle for 5/6 years, I'm inclined to be forgiving ).
In Unity is laying off hundreds of employees

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.