I asked 4 LLMs which Game Engine they’re most familiar with:
Out of curiousity, which of those are you most familiar with, if you would have to create a game client with it? Godot, Unity, Defold, Unreal?
and this is what I received as a response.
Codex 5.3
For creating a game client, Iām most familiar with Unity.
Roughly, my practical support depth is: Unity > Godot > Unreal > Defold.
Gemini 3.1 Pro
1. Unity (Most “Familiar”)
Unity has been a dominant force in indie and mobile game development for over a decade. Because of its massive market share, the internet is absolutely flooded with Unity C# scripts, Stack Overflow threads, and troubleshooting guides.
My strengths here: I can generate C# boilerplate, write complex custom editors, debug tricky Monobehaviour lifecycles, and explain its component-based architecture very fluently.
2. Unreal Engine
Unreal is a close second in terms of raw data volume. It has a massive, highly professional community and decades of history.
My strengths here: I am highly proficient in writing Unreal C++, generating header files, and explaining the architecture of the Gameplay Ability System (GAS).
The AI caveat: A huge part of Unreal is Blueprints (visual scripting). While I can easily tell you how to wire up a Blueprint node by node, I can’t generate the visual graphs directly, which slightly changes how we would collaborate.
3. Godot
My familiarity with Godot is extremely high and rapidly growing. Because it is open-source, the community is incredibly active in sharing code and discussing engine architecture publicly.
My strengths here: Godot’s scene-and-node system translates beautifully into text, making it very easy for us to discuss scene trees. I am highly capable with both GDScript and C#, and I can easily help you structure a game client from scratch using its signal-based architecture.
4. Defold
This is the one I have the least relative “exposure” to, simply because it occupies a more specific, niche space (primarily 2D, highly performant web/mobile games) compared to the big three.
My strengths here: I still know the engine well! I can help you write the Lua scripts, explain its message-passing system (msg.post), and structure your game objects. However, if we hit a highly obscure edge-case bug, there is simply less historical data on the internet for me to pull from compared to Unity.
GLM-5
Unity, followed closely by Godot. Unity has the most extensive publicly available documentation, tutorials, and code examples, which gives me the broadest knowledge base. Godot’s excellent open-source docs and Python-like GDScript make it a close second. Unreal is solid but more complex with C++/Blueprints. Defold I know least well due to its smaller ecosystem.
For a 2D game I’d lean Godot (lighter, MIT licensed). For 3D or larger scope, Unity (bigger ecosystem, more third-party tools).
Minimax M-2.7
Godot and Unity are my strongest of those four. Godot has clean open-source architecture I can reason about deeply, while Unity is widely documented with massive community resources. Defold is solid for 2D but I have less recent experience with it. Unreal is powerful but C++/Blueprints complexity makes it harder to reason about in detail from first principles.