Game Maker Studio 2.0 was asking for way too much money for not enough features I was looking for (namely 3D development, the Direct3D functions in GMS haven’t been cutting edge for around 10-15 years.), so someone suggested I go to Unity. TBH, I really liked GameMaker, and used it since 7.0 all the way up to Game Maker Studio 1.4.
Many of these things may have better solutions since the software has matured. Passing events between objects can also be a bit tricky. GML can potentially be limiting within the event framework Game Maker sets up. I'm glad I chose it as the engine to release my first game, I think it probably saved me a good deal of frustration, but I'll be moving on to Unity after I finish this project. I'm not gonna say it's the best engine on the market, but it might be the best option for some users' needs.
Also, a lot of the built in tools are ONLY good for prototyping - I have a hard time believing the sprite editor is getting a lot of serious, professional use as it's pretty limited. There are a handful of functions that feel underdeveloped for a game engine (the top ten scores function, for instance).
I was disappointed to discover that other engines have better API support, especially for HTML5. The frustrations that I've experienced "further down the line" with GMS2 are bad but not disqualifying.
The documentation and community support were also a big plus for me, /r/gamemaker and their Discord are great resources. GMS2 is beginner friendly and capable of very fast prototyping while also being robust enough to deploy a finished project. Check out our Discord! Suggestions and feedback Message the Moderators r/Games: A place for informative and interesting gaming content and discussions. r/gamedevclassifieds: A game development classified section to help you find talent, or to help the talent find you. r/indiegaming: The place for all news and developments in the Indie gaming community. r/themakingofgames: For all 'behind the scenes' content of your favorite games. r/devblogs: The latest blog posts from your favorite game development bloggers. r/GameSociety: reddit's "book club" for games. r/ludology: For the serious discussion and analysis of games played on a computer, board, field or any other interactive media.
r/tabletopgamedesign: All things related to designing tabletop RPGs, wargames, board, and card games. r/gamedev: All things related to game development, programming, math, art, music, collaboration. If your post isn't related to game rule crafting, consider posting in one of the following subreddits: Please report any submissions or comments violating these rules using the report button. Show-off posts are only allowed as game design case studies (Tell us how/ why you developed an interesting game design concept in your game)ģ) DO NOT link to an article or video without providing a short summary. All submissions must be related to Game Design.Ģ) DO NOT post self-promotion, sales, low-effort posts, memes, jokes, etc. "how do I fix this problem in Unity?" or "how do I get a job in the game industry?" Try /r/gamedev instead. Posting rulesġ) DO NOT post about general Game Development, e.g. If you're new to /r/GameDesign, please read the GameDesign wiki for useful resources and an FAQ. Game Designers of all experience levels are welcome! Posts about visual art, sound design and level design are only allowed if they are also related to game design. Posts about programming, making assets, picking engines etc… will be removed and should go in /r/gamedev instead. This is NOT a place for discussing how games are produced. If you're confused about what game designers do, "The Door Problem" by Liz England is a short article worth reading. It's about the theory and crafting of mechanics and rulesets.
Game Design is a subset of Game Development that concerns itself with WHY games are made the way they are.