When comparing Superpowers vs GameMaker Studio 2, the Slant community recommends GameMaker Studio 2 for most people. In the question“What are the best 2D game engines?” GameMaker Studio 2 is ranked 67th while Superpowers is ranked 71st.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Collaborative
You can spin up a server and work with other people at the same time.
Pro Supports both 2D and 3D
This isn't a 3D with 2D on the side type of engine. The scene-editor supports both 3D and 2D views, allowing ease of use no matter what type of game your making.
Pro Plugin based
The community can develop and release their own plugins to add additional features making game development easier. All of these plugins can be easily downloaded in the app.
Pro Lots of handy built-in editors
It's got a scene-editor, cubic-model creator, text-editor, 2D image / animation importer, and a very useful tile-map editor.
Pro Easy to use programming language
Games can be published to the web with good performance, and the game-framework utilizes TypeScript to make programming games a little bit nicer.
Pro Quick prototyping
Pro Good user interface
Pro Well-optimized engine
Pro Has a trial version (but limited functions, can't export)
Pro Many unofficial tutorials
Most GMS1 tutorials are fine for GMS2
Pro Highly customizable IDE
Although users must work within the IDE and editor, GMS2 has many options to customize the look and feel
Pro Good documentation
Pro Huge, generous community
Cons
Con Not frequently updated
Although it's got very nice features as is, and the team does respond to issues at a pretty good rate, the engine itself takes a little while to get updates. It's a 3-4 person team, and they need to work jobs on the side in order to bring in income.
Even though the updates come out a little slower than other engines, the team is still very much committed to the project and still support it well.
Con Not the best scripting language out there
GML is just weird; if you want to learn programming, it is not the best because it teaches bad habits and has many odd shortcuts and shortcomings that won't transfer to a real language
Con HTML5 export is buggy, doesn't "just work"
Con Quite expensive
Windows ($100) + HTML5 ($140) + Mobile ($400) + UWP ($400) is $1,050, plus $800 anually for each console export separately. But doesn't do anything any of the free engines can't do, and the stability and tech support aren't great.
Con Unstable
Users frequently report crashes and hangs, particularly when working with assets, and the software uses a complicated underlying meta-file structure that may become corrupted and cannot be rebuilt
Con Limited support for OOP
Con Small development team
The core programming team is only 5-10 people, with about 30 employees total, so bug fixes can take a long time to be addressed, and there aren't many official tutorials