ImpactJS vs HaxePunk

ImpactJS has an active user community that busily produces tremendous resources including videos, books, tutorials, walkthroughs and more. There are also comprehensive class documentation available.

Impact provides 2 types of collision detection; static and dynamic collisions. Both of which are easily integrated into game development.

Many plugins are available, including one called Impact++ which adds features like pathfinding and dynamic lighting.

Built-in map editor with support for tiling, collision layers, and actors.

Works with Box2d physics library, comes with all worthwhile elements for actors built in.

Extending the reach of a game developed with ImpactJS is easy due to the cross-platform nature the framework. There are Considerations around performance, resolution and audio, however all can be appropriately addressed when in development. Works in the browser via Canvas, even on mobile. Easily translatable into a packaged app.

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.