When comparing Moai SDK vs Flixel, the Slant community recommends Flixel for most people. In the question“What are the best 2D game engines?” Flixel is ranked 17th while Moai SDK is ranked 19th. The most important reason people chose Flixel is:
Ports are available for Objective C, C# (XNA), HaXe and [Monkey X](https://github.com/devolonter/flixel-monkey).
Ranked in these QuestionsQuestion Ranking
Because it uses Lua + C++.
Pro Gives you total control
You can use your own custom shaders and extend the language with C++. MOAI doesn't give you everything, instead it gives you the tools you need to develop any game you want.
Pro Full source code is available
So it is extendable with C++
Pro Easy-to-use particle engine
Uses a limited subset of Lua
Pro Uses Lua, with LuaJIT where possible
Pro Is used by many pro developers
Moai SDK is used by popular developers including Double Fine for their mobile game, Middle Manager of Justice, and for their Kickstarter hit, Broken Age(formerly, Double Fine Adventure.) It was also used to create the popular mobile game Bubble Ball 2.
This proves that this engine can be used to make fully-featured and fun games.
Pro API interfaces
Has options for development like Hanappe and Rapanui, providing a different way to interact with the engine.
Pro Helpful community
The Moai SDK Forum is active and users will go to great extents to answer queries, post code snippets, beta test, and even purchase and give feedback on each others' games.
Pro Helpful and detailed documentation
Although the Moai SDK is very advanced and uses complicated features, the documentation wiki thoroughly and clearly explains how to use these features, such as the Moai Cloud(a service that provides web services for your game), and multiple ways to build from source.
Pro Many ports available
Ports are available for Objective C, C# (XNA), HaXe and Monkey X.
Pro Built-in pathfinding and following
Pathfinding just means figuring out how to (or if you can) get from A to B. FlxTilemap has a function FlxTilemap.findPath() which returns a FlxPath object, which is just a collection of "nodes", or FlxPoint objects.
Pro Camera system for split screen
Create effects like "split screen" views, or "picture in picture" style displays, or even mini-maps with FlxCamera. Each camera is an independent display object, with its own zoom, color tint, rotation, and scaling values.
Pro Record and play back replays
Replays are essentially a list of what keyboard keys were pressed, and what mouse inputs were given, during a specific time frame. Because Flixel is largely deterministic, you can use that information to recreate a gameplay session that someone else recorded, as long as you have the same SWF.
Pro Basic features provide a solid foundation
- Display thousands of moving objects
- Basic collisions between objects
- Group objects together for simplicity
- Easily generate and emit particles
- Create game levels using tilemaps
- Text display, save games, scrolling
- Mouse & keyboard input
- Math & color utilities
Pro Flixel Power Tools extend the functionality
Flixel Power Tools provide a set of classes and APIs that provide more functionality.
Pro Used to create Canabalt, game that started endless runner genre
Con Not for beginning developers
The Moai SDK has very advanced features which allow it to create powerful games. A drawback from this is that it is not very suitable for beginners.
Con Not necessarily tested or stable
Con Scarce documentation
Since it is a minimalist framework there is not that much documentation, but if you are used to reading API references and source code you are good to go!
Con Development has ceased
The last update was over a year ago. Users should not expect things to still work on future OS versions unless they're ready to fix them yourself.
Con Development has stopped
Seems like development for Flixel has stopped. The last commit on all of the branches of it's Github repository are from 2011.