When comparing ENIGMA Development Environment vs AndEngine, the Slant community recommends ENIGMA Development Environment for most people. In the question“What are the best 2D game engines?” ENIGMA Development Environment is ranked 60th while AndEngine is ranked 102nd. The most important reason people chose ENIGMA Development Environment is:
Almost full support for GML, The ability to create and access C++ types, templates, and functions, compile DLLs and other C/C++ scripts
Ranked in these QuestionsQuestion Ranking
Pros
Pro Raw C++ power and GML accessibility
Almost full support for GML,
The ability to create and access C++ types, templates, and functions, compile DLLs and other C/C++ scripts
Pro Cross platform
Support for Windows, Mac and Linux.
Pro Compatible with GameMaker
Enigma can support over 90% of gamemaker's GML language
Pro Friendly user interface
besides the powerful combination between GML and C++, beginners can also use drag and dropping.
Pro Free and Open Source
Pro Faster than GameMaker
Written in C++, many features have been demonstrated running much faster than interpreted equivalents in GameMaker (up to 10-20 times faster than GM 8.1).
Pro Under active development
Changes are made daily to add new functions/fixing bugs.
Pro Helpful error messages
A full stack trace with available cores and memory information as well as operating system and Java version including file names and number is generated whenever an exception is encountered, with a handy link to submit the issue to GitHub.
Pro Functionality can be extended
AndEngine has extensions that can add additional functionality to the engine.
Cons
Con A few bugs & glitches
Because Enigma is under very rapid development, with new functions added almost daily, some bugs and unexaplainable glitches can happen, though they also gets patched quickly.
Con No code refactoring
Like any C++ based programs, the ability to refactor is limited. However, the new Ide for engima will support a few refactoring cababilities
Con Abandoned
No work on the engine has been done since 2013.
Con Doesn't support current SDK
Only works on older SDK that isn't even supported anymore by google or Android Studio.
Con Poorly documented
Documentation is severely lacking.