Flixel vs Leadwerks Game Engine

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.

Leadwerks's flowgraphs resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish.

Has an acceptable 3D map editor that is easy to use.

For example, you take a model (e.g. torch), add a light source to it, add a particle generator (for fire) and save it as a prefab (one file). Then this prefab can be used to add many torches with fire and light.