When comparing Stencyl vs Genome2D, the Slant community recommends Stencyl for most people. In the question“What are the best 2D game engines?” Stencyl is ranked 6th while Genome2D is ranked 53rd. The most important reason people chose Stencyl is:
Visual scripting in Stencyl is based on the [MIT Scratch](http://scratch.mit.edu/) project, which was designed to teach programming. Script elements fit together like puzzle pieces, ensuring that data and function types cannot be mismatched.
Ranked in these QuestionsQuestion Ranking
Pro No coding required, great drag & drop interface
Visual scripting in Stencyl is based on the MIT Scratch project, which was designed to teach programming. Script elements fit together like puzzle pieces, ensuring that data and function types cannot be mismatched.
Publish iOS, Android, Flash, Windows and Mac games without code.
Pro Haxe scripting available for advanced users
Power users can also write code in Haxe (similar to Actionscript 3) to create their own custom classes and extend the engine.
Pro The original concept for Ghost Song was created using Stencyl
The original concept for Ghost Song was created using Stencyl 3.x
Pro Great performance on every platform
Stencyl exports your games to native code so they have great performance on every platform.
Pro Lightning fast
It's the fastest gpu-based framework out there for flash. It's beautifully optimised. It has very low rendering latency, low level OpenGL calls that other tech simply cannot do (ie Unity) due to Stage3D, and thus can render a lot more data quicker
Pro Cross-platform mobile, desktop and web
Supports Windows, Mac OS X, Linux, iOS, Android, Web and native Flash.
And with the HTML5 export, it also potentially supports development for the Wii U :)
Haxe is a strictly typed programming language that saves development time but still compiles high performance executables, and can build for tons of different platforms (flash, c++, html5, java, c#, etc.)
Pro Access to direct draw features
Has access to direct draw features so you can make you own rendering structures (scene graphs etc).
Pro Automatic dynamic batching
Automatically batch geometries with dynamic batching techniques (by using constant buffers).
Pro Component based architecture
It needs much to improve for mobile games, it was left in the era of Flash games. In Android you can not even put the native keyboard, you can not access things like native camera, GPS or native text input.
Con Only available via subscription
There should be an option to buy it outright, especially considering it is written by a one man team....this is not exactly an Adobe level enterprise with shareholders, so there is no excuse!
Con Slow release cycle
Con Not a powerful engine
Should be used for basic games only.
Con Tile system is somewhat inflexible
Con Lacks documentation
The API documentation is minimal, there's not many tutorials and the ones that are there are very small and only cover the basics. If you want to learn how to properly use it, you have to ask the community or read the source code and figure it out.