Flixel vs Blacksmith 2D

Ports are available for Objective C, C# (XNA), HaXe and Monkey X.

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.

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.

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.

• 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

Flixel Power Tools provide a set of classes and APIs that provide more functionality.

Automatically detects changes and updates bitmap cache. Allows to gain even more performance on heavy scenes and runs smoothly on old devices.

All engine code is written in ES6, fully GCC typed, allowing to eliminate all dead code from your app.

Dirty flag tracks scene changes and avoids unnecessary calculations and context calls. If no changes were made to the scene since last frame, no rendering will be done. Battery efficient.

According to the tests on the Github page, the performance is better than in Phaser!

The source code is well commented and easy to understand.

Super small build size through dead code elimination. The best for playable ads and Facebook Instant Games.