Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Phaser vs GameMaker Studio 2, the Slant community recommends Phaser for most people. In the question“What are the best game engines for point & click adventure games?” Phaser is ranked 17th while GameMaker Studio 2 is ranked 37th. The most important reason people chose Phaser is:
Phaser keeps things simple and as such is easy to use by beginners.
Specs
Question Ranking
Pros
Pro Beginner-friendly
Phaser keeps things simple and as such is easy to use by beginners.
Pro 1000s of examples
Thousands of example are on the Phaser website, which show everything you could want to do with Phaser.
Pro Supports WebGL with canvas fallback
If WebGL is unavailable, Phaser automatically switches to HTML5 canvas.
Pro Targets mobile browsers
Built specifically for mobile web browsers.
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
Cons
Con Missing accessibility features
While not a big issue, it may be a dealbreaker for some.
Con Poor code structure
There's little in terms of cohesiveness in classes, methods or patterns.
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.
Con Unstable
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
