When comparing SFML vs Adventure Game Studio, the Slant community recommends Adventure Game Studio for most people. In the question“What are the best 2D game engines?” Adventure Game Studio is ranked 23rd while SFML is ranked 35th. The most important reason people chose Adventure Game Studio is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very efficient and usable
Pro Zlib/PNG license
In short, SFML is free for any use (commercial or personal, proprietary or open-source). You can use SFML in your project without any restriction. You can even omit to mention that you use SFML -- although it would be appreciated.
Pro Can be combined with OpenGL
If you hate something about the way SFML handles graphics, you can just combine it with OpenGL. It's completely smooth and works as expected, without any additional dependencies.
Pro Active community and wiki
You can ask questions on their own personal forum which is full of users, and their wiki is constantly being maintained. They even have an IRC.
Pro Works on every platform
SFML 2.2 brought forth Android & iOS functionality, and SFML games work on Linux, Mac and Windows out of the box, since SFML is written with OpenGL.

Pro Great documentation
SFML is very well documented, even with short examples of use for many functions and modules. Furthermore, there are books like 'SFML essentials' and 'SFML for game development' which teach you how to use this library to its fullest.
Pro Good for OpenGL
If you are thinking about using OpenGL, look no further, you can open a window, and handle events in less than 15 lines, and it provides input, time, and even networking, plus alot more. It has become my favorite c++ library :D
Pro Great library
SFML is a collection of modular, well designed libraries you can implement an engine or game on top of. The API provides tons of good documentation and is very straightforward to use. You can get a game up and running with SFML quite quickly and with minimal effort.
Pro Clean code
An SFML project's code-base is usually clean and easy to read. All public SFML classes are under the namespace "sf" so it is easy to tell which code is yours and which belongs to SFML (of course you can stop this by typing using namespace sf;
).
Pro Available in many languages
There's support for many languages besides C++, current supported languages are: C, .NET, Crystal, D, Euphoria, Go, Java, Julia, Nim, OCaml, Pascal, Python, Ruby and Rust, and this list is constantly growing.
Pro Beginner-friendly
SFML is extremely beginner friendly and even provides pre-built libraries for your IDE of choice on Windows. Besides the fact that it's extremely well documented, they also have a set of tutorials that walk you through every module.
Pro Modern C++11 implementation
SFML is one of the few good C++ frameworks out there to actually make full use of the language. It's extremely well optimized and it plays well with anything you throw at it.
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 Relatively slow
Compared to SDL2, GLFW, it is slow.
Con No GUI editor or IDE
Does not include any IDE or media editor. It's purely source code.
Con May take longer to learn and understand
Con Messy sprite management
Sprites retain all of the operations applied to them, whether that be a new position or a rotation. This makes sprite management somewhat annoying.
Con Not specifically a 2D game engine
It isn't really an engine, more of a collection of modular, well designed libraries you can implement an engine or game on top of.
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)
