When comparing Godot vs Monkey X Pro, the Slant community recommends Godot for most people. In the question“What are the best 2D game engines for Android?” Godot is ranked 1st while Monkey X Pro is ranked 4th. 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 Native code support
Developers can make native calls directly from Monkey code. This allows access to any native functionality and platform-specific features.
Pro Uses a great, easy to learn language
Monkey X uses a custom programming language (called Monkey) for all its scripting needs. Monkey is rather easy to learn, it's object-oriented which will help most programmers with understanding it. It's also statically typed and uses a garbage collector, helping to avoid manual memory management.
Pro Very rapid prototyping
Monkey compiles to HTML 5 so it is very easy to make a small change and quickly preview it in a web browser.
Pro Not running in its own VM
Unlike other multi-platform engines (Unity3D, Corona, etc), Monkey-X games do not run explicitly in their own virtual machines. Your code is translated into the native languages of each target platform, and then compiled as a native executable. For some platforms "native" is still a VM, but there is no overhead compared to other apps on that platform.
Pro Out of the box support for Admob
Add Advertisements to your app with just some lines of code.
Pro Built-in modules for quickly building games
Monkey X has a selection of great built-in modules.
- Data and Filesystems
- Text and Strings
- Online Services
Write your code once for multiple platforms, including iOS, Android, Windows Phone, HTML5, Flash, Windows, OS X, Linux, and many more.
Develop using Windows, OS X, or Linux.
Pro Easy to learn
With it's Object orientation and clean syntax its a brilliant language to learn if you have never done any programming before and yet still has all the power it needs to make full games and apps.
Pro Lots of great examples
Monkey X includes over 50 examples ranging from complete sample games to demos of single features.
Pro Many community modules available
Pro Partly open-source
The entirety of the base-language itself is open source. Commercial modules such as Mojo for non-free platforms cost a one-time fee. Though Mojo is not free for all targets, the targets for these platforms are, meaning it is possible to implement other frameworks for these targets.
The Desktop (GLFW and C++ based) and HTML5 implementations of Mojo are currently free and open source.
The language's development is completely public, and is managed via GitHub.
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 The documentation is not very thorough
The documentation contains a reasonably detailed language overview, and a somewhat-generated list of the included modules, classes, and methods. Module descriptions are rather lax, but usually present. Method descriptions tend to be short, and a majority of them contain no usage snippets; most parameters have very minimal descriptions. And there are no community collaboration features to help improve it, besides GitHub.
Con You'll have to learn a new programming language
Even though this is not a problem if you're new to programming (since you'll have to learn a language anyway), having to learn a new language develop games is a lot of friction for people that already know how to program in other languages.
Con No real asset store
Untangling how to keep assets in the ".data" requires attention and a filenaming convention.