Game Development with GameMaker Studio 2: Make Your Own Games with GameMaker Language

I bought this book to help my son learn Gamemaker. I've been programming for years, which is just as well as I've been able to make sense of this text for him. But for a book which is aimed at beginners this is absolutely dreadful - there are so many errors in the text that you'll struggle to make sense of it.Just a couple of examples so you can see what I mean. On p.109, the code calls a function 'all_cards_matched()', and in the text following it correctly says that this function hasn't yet been written. However, in this explanation, it refers to the function as 'all_cards_paired().' On p.91, there is a simple FSM (Finite State Machine) diagram, referring to four states: wait; check; victory; and loss. Yet on p.94, the code creating an enumerator refers to these states as paused, playing, won, lost. Then in the code on p.96, it checks to see if the state is set to 'wait' - not one of the states in the enumerator.There are numerous other errors, and the text is poorly written too. It's a shame, because there are the bones of a useful book here - but it desperately need an edit and rewrite. As it is, it is basically unusable unless you already know how to code, in which case you'll be able to work out what's wrong. But this isn't really aimed at people who can already code, is it?!

Bien qu'en anglais et datant de quelques années, ce livre m'est indispensable pour progresser avec GameMaker.

Having written hundreds of pages of work instructions over four decades, this book (at least the Kindle edition) feels like a good effort that was rushed to press without any serious editing. Critical instructions and missing lines of code are common enough to bring a novice to tears. I have years of coding experience in other languages so I was able to download the source code from GitHub and figure things out.My opinion of any step-by-step approach is that the more questions a reader has to ask, the poorer the job of laying out and explaining the steps.The author does do a nice job of laying out and explaining tbe steps but falls awfully short in presenting working code in some places. Again, my own opinion, but the author, editor and other test subjects, especially testers unfamiliar with the project, should be following the steps and writing the code. If this had been done, or done properly, then the glaring code errors and missing explanations would likely have not made it into the released version of the book.Also, although the author does explain what lines and chunks of code are doing, the code itself is not commented.It's not specifically mentioned in the book (at least not that I saw) but some basic familiarity with GameMaker Studio 2's working environment is kind of critical. Readers hopefully will have watched the video tutorials provided by YoYo Games so that they are not totally lost.As the title says, the book is focused on Game Development. It not a book about how to program with GML. The author does provide explanations about the GML being used but GML programming is not the focus.I suppose 1 star might seem pretty harsh, but the errors/omissions mentioned above make the desired result impossible to attain rely on the text alone.

if u want to learn gamemaker studio, don't even buy this book, it teach so-called game design, not really about programming, so what u can learn from this book is very limited basic and it offer no help for your programming skill. beside, u can find pretty all those content of the book in youtube for free, so don't waste ur money on this book, unless u make the same mistake as i did, thought having a book will be more organized and easier to learn, but turns out watching video and learn it from some website provide free resource is way better way to learning GMS 2

Terrible, terrible book. It's filled with code errors--- the code in the book will generally NOT RUN unless you make changes based on the code in the GitHub repo. Absolutely painful trudging through this book.