When comparing HaxePunk vs Flixel, the Slant community recommends Flixel for most people. In the question“What are the best 2D game engines?” Flixel is ranked 20th while HaxePunk is ranked 22nd. 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).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Joystick and multi-touch support
Useful for mobile games and soon consoles (OpenFL has a console port in the works).
Pro Crossplatform testing/releasing
HaxePunk uses OpenFL which means you can compile to just about every device. A lot of the rendering code has been optimized so if you use HaxePunk’s graphic classes you are pretty much ready to deploy on any target.
Pro Generic entity system
A generic Entity system that only uses what you “attach” to it. If you need collision masks they are available but if an entity doesn’t need to collide with anything then simply don’t add a mask. Same goes for graphics.
Pro Written in Haxe instead of AS3
This comes with blazing fast compile times, proper static typing, multiple output targets, and a powerful macro system.
Pro Multiple collision masks
HaxePunk has added several collision masks beyond what FlashPunk had including a grid with slope values, circles, and polygons. This is in addition to FlashPunk’s tile grid and hitbox.
Pro Tweens
Tweens are available just like they are in FlashPunk. If you need to interpolate values for sounds, movement, etc… it’s probably already available as a tween. There is also a VarTween that lets you interpolate any value you want.
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
Cons
Con Messy / fragmented documentation
Not a lot of documentation is available.
Con Small comunity
It’s a small but growing community.
Con It is now obsolete
With Adobe Flash dead, Flixel is now unworkable.
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.