HaxePunk vs Leadwerks Game Engine

Useful for mobile games and soon consoles (OpenFL has a console port in the works).

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.

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.

This comes with blazing fast compile times, proper static typing, multiple output targets, and a powerful macro system.

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.

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.

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.