When comparing Godot vs Esenthel, the Slant community recommends Godot for most people. In the question“What are the best 3D game engines?” Godot is ranked 1st while Esenthel is ranked 16th. 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 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 Fully dedicated 2D engine, no hacks
Godot has a mature 2D engine with many features used by modern 2D games.
Pro Built-in physics
Add physics to 2D and 3D scenes, through rigid and static bodies, characters, raycasts, vehicles and more.
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.
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 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 User friendly UI for all your team
Non-programmers (musicians, artists, etc) can join the development easily.
Pro The list of supported languages is growing
Officially, Godot supported languages for now will be GDScript, C#(Mono), VisualScript and C++.
Pro Instancing and node concept makes sense
The node and the instancing concept work very well and helps developers to structure content efficiently.
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 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 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 Can Be Installed On Steam
You can easily install Godot via the Steam store.
Pro Quicker development by using the integrated code editor
Esenthel has a built-in code editor which drastically simplifies the programming process.
Programming with Esenthel is based on C++, however, when using the code editor there's no need to make separate .cpp or .h files. Code can be written once and the editor will be separating definitions and declarations automatically in the background allowing for quicker development.
Pro Can be easily extended
Built in pure C++ so it is easy to use and extend however needed.
Pro Available on Steam
Pro Can be used for collaborative development
Esenthel comes with tools allowing for multiple developers to work on one project at the same time in collaborative mode. Every change made is instantly visible by other team members.
Pro Engine issues are resolved quickly
The author is very device minded and able to handle any problem quickly and effectively and he has a good track record of listening to requests.
Pro Access to full source code
Having easy access to the full source makes it possible for any skilled developer to add features that a project requires.
Pro Attractive licensing
Free to try, with license as cheap as 9.50$/month (with yearly subscription), 11.40$/month (monthly subscription) or full source code license 228$/year.
Pro Incredibly stable
The engine is rock solid and stable which, considering its extensive feature set, is a huge plus for game developers
Pro Helpful and responsive forum
Pro Good support for Android and iOS
Android and iOS support is pretty stable and easy to develop on. It's possible to, for example, develop the entire game on Windows or Mac and then easily compile for Android and iOS.
Pro Can import a wide variety of formats
- 3D - FBX, DAE, OBJ, 3DS, B3D, MS3D, BVH, ASE, PSK/PSA
- 2D - BMP, PNG, JPG, TGA, DDS, TIF, WEBP, PSD, ICO
- Videos - VP9, Theora
- Sounds - OGG, WAV, MP3 (once decoding patents expire)
Pro Constant development and progress
New features or update to features are provided monthly.
Pro Supports in-app purchases
IAP support for both mobile and desktop devices.
Pro Supports multiple compression libraries
LZMA, LZHAM, LZ4, ZLIB, Snappy, RLE
Pro Oculus Rift native support
Oculus Rift API integrated into the engine platform.
Pro Supports modern graphics and sound APIs
- Graphics - DirectX 9/10/11, OpenGL, OpenGL ES, WebGL
- Sound - DirectSound, OpenAL, OpenSL
Pro Rock solid
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 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. Though it has gotten better starting from version 3.0.
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 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 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 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 NoAdmob or other AdNetwork support
Godot has no native support for implementing advertisements into your game.
Con Hard for a Unity user
Coming from a Unity background, Godot engine is hard.
Con Slow roadmap implementation
Bugs are fixed promptly, but the developer maintains a growing 'roadmap' of features with no indication to users of time frame and priority of feature implementation.
Con One-man developer
Although the complete engine is maintained by a single, highly-skilled individual, he can be limited to what he is able to see or perceive, and sometimes he doesn't recognize broken or incomplete features until he sees it firsthand and sometimes doesn't recognize valid reports from his users. But when he does recognize the gap in the engine's feature-set, he is quick to make adjustments and updates.
Con Lack of in-depth tutorials
There are plenty of beginner coding tutorials which serve as a basic introduction for a new user to get up to speed, but once having passed that stage there is a real lack of free more advanced tutorials/examples/code snippets demonstrating the finer details of the vast and varied API functions.
Con Lack of editing tools
Con Web support practically non-existing