Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Phaser vs Flax Engine, 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 Flax Engine is ranked 54th. 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 Free
Can be used for free until you hit a rather high revenue cap, at which point you have to pay royalties.
Pro Powerful C# scripting
C# scripting is really well made, comparable to Unity, but without any of the legacy cruft.
Pro Multiplatform
Supports most platforms, including Windows, Linux, Android, Nintendo Switch, ...
Pro Modern rendering backend
Has a very modern, performant and beautiful rendering backend.
Pro C++ support
The entire core is written in C++ and it supports writing game code in C++. The interoperability between C# and C++ is also nothing to scoff at.
Pro Supports multiple IDEs
Works with any text editor and comes with proper support for Visual Studio, VSCode and Jetbrains Rider.
Pro Excellent documentation
The documentation is well written, up to date and accepts improvements from the community.
Pro Great and extensible editor
The editor is both powerful and simple. My favourite part is how easy it is to extend the editor with custom magic.
Pro Source code available
The entire source of the engine is available on Github, though not under an open source license.
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 New software
As is standard with new software, not all of the bugs have been ironed out yet.
Con Few plugins
Unlike more mature engines, there isn't a vibrant ecosystem of plugins yet.
Con Not open source
While the source code is available, it's not quite open source
Con Not latest C# version
It uses Mono and is still on some variant of C# 7.
Con No OpenGL support
It only supports modern APIs, namely Vulkan and DirectX. This means that it won't run on very old machines.
