When comparing Moai SDK vs Urho3D, the Slant community recommends Moai SDK for most people. In the question“What are the best 2D game engines?” Moai SDK is ranked 18th while Urho3D is ranked 59th. The most important reason people chose Moai SDK is:
Because it uses Lua + C++.
Ranked in these QuestionsQuestion Ranking
Because it uses Lua + C++.
Pro Gives you total control
You can use your own custom shaders and extend the language with C++. MOAI doesn't give you everything, instead it gives you the tools you need to develop any game you want.
Pro Full source code is available
So it is extendable with C++
Pro Easy-to-use particle engine
Uses a limited subset of Lua
Pro Uses Lua, with LuaJIT where possible
Pro Is used by many pro developers
Moai SDK is used by popular developers including Double Fine for their mobile game, Middle Manager of Justice, and for their Kickstarter hit, Broken Age(formerly, Double Fine Adventure.) It was also used to create the popular mobile game Bubble Ball 2.
This proves that this engine can be used to make fully-featured and fun games.
Pro API interfaces
Has options for development like Hanappe and Rapanui, providing a different way to interact with the engine.
Pro Helpful community
The Moai SDK Forum is active and users will go to great extents to answer queries, post code snippets, beta test, and even purchase and give feedback on each others' games.
Pro Helpful and detailed documentation
Although the Moai SDK is very advanced and uses complicated features, the documentation wiki thoroughly and clearly explains how to use these features, such as the Moai Cloud(a service that provides web services for your game), and multiple ways to build from source.
Pro Free and fully open source
The entire engine is open source and makes use of other open source libraries. Source code is licensed under MIT and available on GitHub.
Pro Includes a lot of samples
There are a lot of sample projects included with the engine for both C++ and Angelscript. They are mostly very simple applications built to demonstrate the engines capabilities and features.
Pro Fat-free codebase
Only use what you need.
Pro Very high code quality
Urho3D is written in a modular and super-clean way, so that it can be integrated into the other parts of your game seamlessly.
Pro Good documentation
The documentation for Urho3D can be split in two parts: auto-generated from class references and documentation written to cover the various aspects, features and systems of the engine. The written documentation is pretty good. It covers most of the aspects of the engine in clear and understandable English.
Pro In constant active development
Bugs are usually fixed that same day. Core devs are very active on forums. New features are always being worked on. HTML5, DirectX11, and OpenGL3.1 support have recently been added (as of 4/15/15).
Pro Small turnaround times while developing
Builds are quite fast, aids in rapid development.
Pro Does not require an editor to get going
Pro Good 3D level editor
Pro Unofficial Oculus Rift support
Information on enabling OR support can be found here.
There are no lights limits per mesh.
Pro Flexible rendering pipeline
You can configure rendering pipeline.
Pro I Love It!
It's Recommended, So I Want To Make You Happy!
Con Not for beginning developers
The Moai SDK has very advanced features which allow it to create powerful games. A drawback from this is that it is not very suitable for beginners.
Con Not necessarily tested or stable
Con Scarce documentation
Since it is a minimalist framework there is not that much documentation, but if you are used to reading API references and source code you are good to go!
Con Development has ceased
The last update was over a year ago. Users should not expect things to still work on future OS versions unless they're ready to fix them yourself.
Con The UI can be hard on the eyes
Urho3D's UI could cause eye strain.
Con May be a bit hard to get started
To install Urho3D you need to get the archive from GitHub (be careful to download the master branch) and extract it. After that, you need to compile the engine with CMake. If all the dependencies are installed, then it should be a straightforward process, otherwise you will need to track down and install all the missing dependencies.
For people who don't have much experience with CMake this whole process may seem a bit like magic. For people who do have experience with CMake, the whole installation will be relatively easy.