When comparing HaxePunk vs Adventure Game Studio, the Slant community recommends HaxePunk for most people. In the question“What are the best 2D game engines?” HaxePunk is ranked 22nd while Adventure Game Studio is ranked 23rd. The most important reason people chose HaxePunk is:
Useful for mobile games and soon consoles (OpenFL has a console port in the works).
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 Easy to learn tool
Good for newbie game creators. Can be used for prototyping: on several occasions was used to make a demo/experimental version before creating a final commercial product on different engine.
Pro Completely free and open source
AGS is licensed under Artistic License 2.0 and is completely free for use for creating both freeware and commercial games.
Pro Relatively well documented
Besides the manual there are multiple text and video tutorials and code samples written by community.
Pro Used for a number of high-profile commercial releases
Adventure Game Studio has been used to develop games such as "Resonance", "Blackwell" series, "Gemini Rue", "Primordia".
Pro Lots of assets available
An extensive library of game templates and script modules accumulated over years. You can construct a simple game in hours (if you know what you are doing).
Pro Friendly community
An old, big and active community which would support newcomers not only in learning basics of the engine, but can help with every aspect of game making (including art, voice acting, moral support, etc).
Cons
Con Messy / fragmented documentation
Not a lot of documentation is available.

Con Small comunity
It’s a small but growing community.
Con Natively supports only 2D
2D only native support, 3D could be supported with plugins though.
Con Uses dated tech
Engine is based on the old technologies, which impose number of limitations and may cause problems on latest systems (level of annoyance varies depending on your priorities).
Con Graphics renderer is a bit dated
Graphics renderer is not well optimized for high-resolution games and complex effects.
Con No visual editor for scripts
You have to actually write all scripts yourself.
Con Development is slow
Further development of the engine is currently slow, done by only few people in their free time.
Con AGS Script isn't as full-featured as other scripting languages
Its own scripting language has lower syntax capabilities compared to modern script languages.
Con Assets cover almost exclusively adventure/quest genre
The features, script functions and game templates are very biased towards adventure/quest genre. The non-adventure games were made in AGS (2D shooters, platformers, turn-based strategies), but their development usually requires to write everything from scratch.
Con Workflow is closely coupled with the editor
Workflow is very tied to the editor and custom file formats, which can cause problems for bigger, more professional projects (interfering with source control, parallel development, automated builds, etc)
