When comparing Godot vs Unreal Engine 4, the Slant community recommends Godot for most people. In the question“What are the best 2D game engines?” Godot is ranked 3rd while Unreal Engine 4 is ranked 18th. The most important reason people chose Godot is:
Every property can be animated.
Ranked in these QuestionsQuestion Ranking
Pro Integrated animation editor
Every property can be animated.
Pro Fully dedicated 2D engine, no hacks
Godot has a mature 2D engine with many features used by modern 2D games.
Pro Can be deployed to multiple platforms
Deploy games to desktops (Windows/OS X/Linux), smartphones (iOS/Android/BlackBerry), and the web (HTML5 via Emscripten).
Pro Unified game editor interface
All the game development work is done inside one program: the engine editor. The scripting is done in the same program. No need for Eclipse or other front-end editors.
Pro Built-in physics
Add physics to 2D and 3D scenes, through rigid and static bodies, characters, raycasts, vehicles and more.
The executable is portable and less than 40 MB in size.
Pro Free and open source
Godot is licensed under MIT license. Anyone can grab the source from https://github.com/godotengine/godot, and compile the engine themselves.
Pro Under constant development
This engine barely released one year ago has more than 1000 forks on github and about 100 developers. Not only that just a bit of browsing trough issues you will quickly find out the dev community loves new esp free technology and does not shy away from completely rewriting parts of the engine. The audio engine is being completely rewritten to use threads and so forth.
Pro Instancing and node concept makes sense
The node and the instancing concept work very well and helps developers to structure content efficiently.
Pro Editor and runtime are fully cross-platform
You can run Godot on all 3 major operating systems (Windows/Mac/Linux) and build your game to all available platforms from each without any platform-specific work needed. All platforms including Linux are supported first class.
Pro Easy to learn scripting language
Godot has their own scripting language called GDScript. The scripting language is easy to learn with Python-like syntax, but it is not Python. It's very powerful, easy to learn, and it's free of unnecessary things because it was custom built for optimized integration with the Godot Engine.
It can be used to add custom behaviors to any object by extending it with scripting, using the built-in editor with syntax highlighting and code completion.
A built-in debugger with breakpoints and stepping can be used and graphs for possible bottlenecks can be checked.
Pro Fun to use
An important aspect that can't be grasped without using the engine for a few days. The Interface is evolving nicely and making games is just fun.
Pro The list of supported languages is growing
Officially, Godot supported languages for now will be GDScript, C#(Mono), VisualScript and C++.
Pro User friendly UI for all your team
Non-programmers (musicians, artists, etc) can join the development easily.
Pro Internationalization of the editor
You can change the language shown in menus. Godot translations: https://hosted.weblate.org/projects/godot-engine/godot/
Pro Drag & drop interface
Many parts of the editor allow you to drag & drop, which makes working with assets and scene trees a joy.
Pro Friendly towards Version Control Systems
The engine is build not only to support version control but to really use it. Scene files for example which usually get compiled into some sort of unreadable data stay in a text format - that way you can actually see your changes in a version control system like Git.
Pro Really good community
The community is great and really cares about the engine. It is easy to get help and to be part of Godot's future.
Pro Creating editor tools is a breeze
Godot Engine is itself a Godot game. By adding the "tool" keyword to the top of a script, you can design extensions for the editor itself INSIDE the editor. Integrating these editor scripts into a bundled plugin for sharing is extremely easy to do.
Pro Built-in documentation linked to the internal ScriptEditor
The editor has a fully searchable index of class API documentation for everything the engine offers (NOT just a web interface). You can easily open the documentation for any class by Ctrl-clicking the class's name in the in-engine text editor for scripts.
Pro Simple and readable codebase
The engine's source code is easy to read and understand with a self-documenting approach to code design. You don't have to wait months or years for other people to fix an engine bug that is important to your game. Often times, you can spend an hour or two of your own time to fix whatever problems you encounter yourself.
Pro Easily expanded scripting system
With 3.0's addition of NativeScript and PluginScript via GDNative, developers can easily define bindings for new scripting languages. In addition to the primarily supported C++, GDScript, VisualScript, and C# languages, the community has contributed D, Nim, and Python as well with more on the way.
Pro Scene Based editing
Godot gives you the ability to create scenes to make your life easier, with reusable objects and things you want to incorporate in your games. This makes the game making processvery streamlined and organized.
Pro Free development license, including source code
The engine, including full access to source code, is licensed to developers for 5% royalty on resulting revenue if it exceeds $3000 per quarter.
Pro Dynamic global illumination with voxel cone tracing decreases the computational power needed
Voxel cone tracing is a similar algorithm to ray tracing, but uses thick rays instead of pixel thin rays to be able vastly decrease the amount of computational power needed.
Pro A visual scripting system for non-coders enables quick prototyping
Blueprints are authoring tools designed for non programmers so designers and other team members can help tweak and prototype. UE4's Blueprint scripts resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish and games a lot faster to prototype.
Pro Developers have full control of the engine and source code
UE4 gives full access to the C++ source code allowing editing and upgrading anything in the system.
Pro Lots of resources to learn from
Epic provides multiple official video tutorials, lots of free example projects and content, an extensive wiki and regular streams showing how to use latest features.
Pro Powerful material/shader system
Allows a texture/material artist or VFX artist to create amazing effects from the ground up.
Pro Spectacular lighting visuals
Pro Active community
Forums have many active and friendly members that are quick to respond and help out. Even staff is very active on forums.
Pro Cross-platform editor and export
This engine exports for a big range of platforms including Linux. The editor can be run on Windows, MacOS, and Linux (Early Access).
Pro Fast compilation for quick iteration
Recompiling an entire game to test a small change takes up a lot of time. UE4 quickly compiles in seconds instead of minutes improving iteration time by an order of magnitude.
Pro Quick release-cycle
New feature releases can be commonly expected about once a month.
Pro Realistic graphics
Pro AAA Ready
This is ready to make the next AAA game.
Pro Professional feature set for all aspects of game development
Almost everything a game developer wants has a deep and sophisticated tool waiting for them in UE4. No external plugins are needed to make powerful materials, FX, terrain, cinematics, gameplay logic, AI, animation graphs, post process effects, lighting etc.
Pro Proven track record
Pro No coding experience needed
Con C++ Engine API not very friendly
The base C++ code from Godot is not documented, it's hard to set it up, to compile and hard to extend, it could use better programming standards.
Con Tileset management could be more efficient
The tileset creation and management is lacking common features found in more developed tileset managers. However, it features support for Tiled - the only downside being that it is an external program.
Con No built-in way to import atlases
Godot does not have an easy and automatic way to import atlases created by other tools. However, there are plugins that can be used to import atlases from other engines.
Con Very bad documentation
The documentation is poorly written, and has very few examples of real application and even fewer design guidelines about how to program a game in the engine.
Con 2DPhysics is weak compared to Box2d
Box2d has much more features.
Con Strange terminology at its base
Scenes can be made up of other scenes. That makes some sense. But even the smallest object (or prefab or asset) in a scene -- such as that spoon on the table or the marble on the floor -- is still called a scene... except when it's called a node. This is a bit odd for those coming from other engines. With all the great decisions behind the basic design of this engine, the choice of this term from all the potential other terms out there seems really out of place and only serves as a constant reminder that not everything about Godot is great.
Con No console targets
Given that you can target both desktops and consoles with the same code base in other engines, the lack of support for consoles in Godot is pretty hard to get past if targeting desktops for a game. But asking for an open-source engine to target consoles is probably too much to ask. But it would be interesting to see some legacy consoles targeted even if current ones cannot be.
Con NoAdmob or other AdNetwork support
Godot has no native support for implementing advertisements into your game.
Con Difficult to optimize
Godot has an OOP architecture. Everything is an object internally and data is spread among many classes, thus it's difficult to optimize (i.e. not cache friendly, difficuly to vectorize or paralellize, etc).
Read about "Data Oriented Design" for more info about the problems and solutions.
Con OSX app is a mess
Instead of one contained folder/file with an icon per normal it is a mess of files which is not at all suitable or distributable without further work after every compilation.
Con Hard for a Unity user
Coming from a Unity background, Godot engine is hard.
Con Very high build size
A blank project will build in to a minimum of 200 MB.
Compared to other engines, UE4 seems to perform various actions considerably slower. Actions like starting the engine, opening the editor, opening a project, rebuilding shaders, updating references, calculating lightmaps, saving projects, etc take long enough to get irritating and end up wasting precious development time.
Con No drawcall batching, performance is very bad on mobile
There's no dynamic batching support to minimize drawcalls. There's InstancedStaticmesh concept in UE4, but it's 3d only, functionally limited and requires hardware support which rules out most mobile devices.
Con Extremely long build times
Making a full rebuild, including engine can take a good 30minutes. If you plan to use Unreal professionally, you better get some licenses for Incredibuild as well.
Con Poor documentation
Most of the "documentation" for code is actually just automatically generated from the source. If you're interested in knowing how things are supposed to work, you must either go to their answers site or pay for UDN.
Often their examples won't even compile, since they were written for now outdated versions.
Con Steep learning curve
Especially when compared to its primary competitor, Unity.
Con Hard engine for beginners
This engine not easy for beginners
Con C++ - oriented development cycle: slow turn-around times
The Unreal Editor is the main place to do stuff (of course), so if someone wants to do a lot of C++ stuff, the compilation and linking turn-around times can be painful. Still they probably are quite fast in comparison to the provided featureset.. Still ,they are far from optimal.
Con Royalty based
5% of profits will go to Unreal after $3000 earned in a quarter.
Con They spend more time adding features than fixing existing ones
Con Poor quality assurance on their releases
After each release they almost immediately release a hotfix. And another one. And another one.
Con C# not natively supported
UE4 does not support C# natively, but this can be achieved through MonoUE, although it requires using the MonoUE fork instead of UE itself.
Con Extremely poorly designed
The code is a mess.
Everything is connected, a single Actor is 1500 bytes, because it contains a million things that Epic once needed in a game.
Inheritance for AActor: AActor > UObject > UObjectBaseUtility > UObjectBase
Con Tutorials do not go in-depth enough
The blueprint tutorial just teaches how to turn on a light when you press f.
Con No Terrain Editor included
Con Poor source control support
Merge tool is not working.
Con Difficult for mac users
If you're installing it on mac, you simply download epic games launcher and watch it download nothing endlessly.
Con Bad support
The epic games team only assists with billing and account issues, not bugs.
Con Terrible physics
Con Frequent crashes
Often the editor crashes interrupting your work.