GameMaker: Studio vs Engine 001 Game Maker

Language does not support actual objects, structs, real data types, functions, overloading, even argument naming. Developers generally have to code around the lack of these features in very tricky ways.

The GUI must be hard-coded, leaving a lot of tricky calculations and jumping through hoops to accommodate different devices and displays; it's probably the least developed and hardest thing about GMS2 compared to comparable engines

In late 2012/early 2013, YoYo Games released a version of their new Studio IDE for cross-platform development that would import games and destroy all of the image type resources for some legitimate purchasers of the software by superimposing a pirate symbol on top of the image. This was due to a fault in their digital rights management software implementation which they use as a method of combating pirated copies of the software. Though the false positives bug is reported to be fixed, the DRM is still in place and may affect placeholder graphics, etc. YoYoGames publicly stated they would remove the DRM at a later point in time, but that other less-invasive DRM techniques would remain.

You need to buy extra modules to be able to export to platforms like Android, iOS, HTML5 and others.

There are no built-in refactoring tools. For example, you can rename a resource, but GM:S will not automatically change the mentions of it across the code to the new name. Furthermore, because all file formats are text-based, basic refactoring could be achieved by simply doing "find & replace in all files" -- which is a feature offered by pretty much every external code editor nowadays -- but no such feature here. Hitting Ctrl-F will pull up a rather odd Find/Replace box but selecting a word before hitting Ctrl-F will not autofill the Find field for you like it will in most tools. Even that you have to cut and paste yourself.

The cost for this tool is hindering for indie developers who have little money to work with.

In the past, the developer failed to update the software for iOS and Android when game-breaking updates were made to those platforms.

The change from 1.x to 2.x was cosmetic, the engine and language stayed the same. The roadmap for future development is also cosmetic and includes updating the sprite editor, adding an audio editor, and adding a "mini map" for the IDE.

No marquee select, no layers, can be glitchy, no grouping, etc.

Doesn't support embedding videos in a game.

There are several options with more flexibility, better learning resources, and a lower price point.

Because it uses GML, a very non-standard custom language, new users do not learn a transferrable language and become locked in.

Documentation and resources largely focus on proprietary scripting language, which is necessary for achieving full potential of the software due to poor drag and drop integration.

Support entirely focused on new iteration depriving even basic functionality of this version with any purchase that hasn't already been activated. It is still possible, thought not intuitive, to download this version on the trail screen for GM S 2. But no purchased (wildly expensive) module can be added any longer.

While the editor of course has features for intending code such as auto indent and smart tabs that can be turned on or off, these features work in unusual ways and, overall, the editor is not very adaptable to various typing styles. Also, Home always takes you to position 0 and never to the beginning of the text no matter how many times you hit it. Thus, if you hit Home and then Enter a new line, with auto indent on, it will always mess up the indentation on the line following the new line leaving you to fudge around to fix it manually. If you prefer tabs over spaces, forget it. Finally, if you leave the GameMaker app and try to click back into the code editor, the code editor will not fully get the focus sometimes leaving you with the ability to type but not tab. It usually takes two clicks to fully focus the code editor from outside the GM app.

They are not beautiful - for example, Undertale.

As opposed to other engines, which are open source or owned by game companies, GameMaker is developed by YoYoGames, which is owned by Playtech, a gambling software company.

As it doesn't have enough tutorials, and they don't wanna make more, so they just add some new services about one on one help which that cost 40$ for an hour.

The editor is Windows only, no OSX or Linux versions are planned.

The 3D capabilities of the engine are a bit limited (for today standards), and some of the times you'll need to work around to create something.

Even those few tutorials don't teach you the very basics, and first you must learn the basics somewhere else (the submitted pros are by professional guys).

Just ask them about games made with this engine and you will see that even if you find some good games, those are mostly simple/small ones.

If you want to use more than a few actors/light/events, or you're trying to get a pretty look, you will get a significant drop in frame rates. This is especially true if you want to implement a moving light (something like a flashlight).

If you encounter a bug or problem and report that as bug report, it will take about 1 week to get any answer, and if they solve that, the fixed version will just come up with next update for engine which that isn't be soon and no specific time, so maybe you have to wait for one month.

Sometimes you have to do a time-consuming workaround to just do a simple function.

There are significant drops in frame rate; some bugs that can even ruin your game (also, looks like just run on firefox).

Are you a mobile developer? If so it's good to know that it has export for ios/Android but no support for IAP or Ads.