When comparing Stencyl vs GameMaker Studio 2, the Slant community recommends Stencyl for most people. In the question“What are the best 2D game engines?” Stencyl is ranked 6th while GameMaker Studio 2 is ranked 85th. 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 Quick prototyping
Pro Good user interface
Pro Well-optimized engine
Pro Has a trial version (but limited functions, can't export)
Pro Many unofficial tutorials
Most GMS1 tutorials are fine for GMS2
Pro Highly customizable IDE
Although users must work within the IDE and editor, GMS2 has many options to customize the look and feel
Pro Good documentation
Pro Huge, generous community
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 Not the best scripting language out there
GML is just weird; if you want to learn programming, it is not the best because it teaches bad habits and has many odd shortcuts and shortcomings that won't transfer to a real language
Con HTML5 export is buggy, doesn't "just work"
Con Quite expensive
Windows ($100) + HTML5 ($140) + Mobile ($400) + UWP ($400) is $1,050, plus $800 anually for each console export separately. But doesn't do anything any of the free engines can't do, and the stability and tech support aren't great.
Users frequently report crashes and hangs, particularly when working with assets, and the software uses a complicated underlying meta-file structure that may become corrupted and cannot be rebuilt
Con Limited support for OOP
Con Small development team
The core programming team is only 5-10 people, with about 30 employees total, so bug fixes can take a long time to be addressed, and there aren't many official tutorials