- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Game Coding Complete Paperback – Jun 11 2003
Special Offers and Product Promotions
Customers Who Bought This Item Also Bought
To get the free app, enter your e-mail address or mobile phone number.
About the Author
Mike McShaffry, a.k.a. aMr. Mike,a started programming games as soon as he could tap a keyboard. After graduating from the University of Houston, he worked for Warren Spector and Richard Garriott, a.k.a. aLord British,a at Origin Systems on Martian Dreams, Ultima VII:The Black Gate, Ultima VIII: Pagan, Ultima IX: Ascension, and Ultima Online. Seven years later he formed his first company, Tornado Alley. Mike later accepted a position at Glass Eye Entertainment, working for his friend Monty Kerr, where he produced Microsoft Casino. Ten months later, Monty asked Mike and his newly assembled team to start their own company called Compulsive Development, which would work exclusively with Microsoft on casual casino and card games. Mike served as the Head of Studio, and together with the rest of the Compulsive folks, produced three more casual titles for Microsoft until August 2002. Compulsive was acquired by Glass Eye Entertainment to continue work on Glass Eyeas growing online casual games business. Mike was later recruited to start an Austin studio for Maryland-based Breakaway Games. Mike is currently self-employed, helping teams build a positive, creative and energetic environment so they can do what they do best - make great games.
Inside This Book(Learn More)
Most people that want jobs in the computer game industry have some interesting and completely wrong opinions about what it's like working on games. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Top Customer Reviews
I've bought many game programming books over the years, and two authors stand out... Mike McShaffry and Andre LaMothe. This book is incredibly valuable as a reference and as a guide. Quite honestly, I wonder who paid the guy who wrote the "Spotlight Review" to dis it so badly, or who he paid to get his opinion in the spotlight.
But here's a test you can take for yourself... go to [...] and see how Mike McShaffry is *still* helping folks who've read his book, (or anyone who post on the site for that matter). He's still giving *free* advice on his book's forum, when most other authors won't even respond to an email.
In response to those who objected to the author's "coding opinions":
Yes, the guy has an opinon - he's entitled to. What do you expect from a book? "well, this is probably wrong, and I don't really know what I'm talking about, but the publisher paid me a lot of money so I have to say something." Give me a freaking break! OF COURSE the book is full of opinions - that's what books are!
Just one caveat - it doesn't teach you C++. It assumes some experience, meaning you can take the coding advice and apply it to suit your own style. It does assume a basic level of professional ability in other words.
IMHO this book is geared toward those who want to make a professional career in making games, but have no idea how, while at the same time teaching concrete principles of game programming to those like me who are currently hobby coders. Many times had I tried and failed to start developing a game, but I am now building my game intelligently and efficiently, knowing exactly what I need to do to get things done. I have to say it is all because of this book.
This is also one of the few books that has managed to grip my attention for as long as it did because of the clever way that Mike writes. His writing style is such that it is easy to read because of its almost informal nature. The text thankfully lacks rigid structure, and welcomed breaks in the lessons of "how and why" are made up of "I remember the day" stories that are both amusing and filled with helpful hints on what NOT to do OR how the approached a problem and fixed it :) (Which is the point BTW)
The code in the book is sparse, and it initially bugged me, but I came to realize that it really is not about giving the reader chunks of code. This is not a step by step guide on how to make a game, but a collection of ideas on how to cleverly write and manage your game.Read more ›
Unfortunately Mr. McShaffry fell into the same pitfall most other "here's THE right way to write code" authors fall into: he just has too many opinions and not enough facts. He touches on a lot of subjects which are programming religions, and there is no objective right or wrong for much of what he discusses. I feel some of the problem lies in the fact that McShaffry has worked on two types of games: the Ultima series and a playing card game. If you work on one codebase for years, you're going to think your solutions are perfect. As a person who has worked on numerous different types of games and engines I can tell you that there is no magic solution for writing the perfect engine. The engine is always very heavily tailored to the game desired. This is why you hear about the Quake engine, or some other third-party technology, being licensed and then gutted with major portions rewritten. So most of McShaffry's game-specific ideas need to be taken with a grain of salt. An example: smart pointers sure are safe, but if you're working on the PS2 you probably can't spare the memory or execution time for all that tracking.
I also disagree with his opening statements about variable and function naming. This is a constant headache for development teams, particularly game dev teams whose programmers are mostly self-taught.Read more ›
For example, he tells how automated build scripts are vital and how milestone builds and multiple projects are useful. But all this of course applies equally well to any code project with several programmers involved. The chapters on debugging/testing are also quite general in scope, and useful in explaining that this is a discipline, in and of itself.
The book specialises to code examples in C++ for the various Microsoft OSs. In no small part because most desktops are running these operating systems, and if you are in a commercial effort, you go where most of your customers are. The choice of C++ is good and realistic. For games with a quick response time, compiled code is usually faster than interpreted. But then why not C, you might ask? Because C is procedural and scales badly when the source code gets over 100 000 lines. C++ is a much better choice.
The coverage of 3D graphics is only the bare minimum, as the author points out. For any application using 3D, you need at least another book, dedicated purely to the algorithms in that field, to be used in tandem with this book.
Most recent customer reviews
The author tries to hard to cover the basics of making games. It sort of reminds me a class study guide, i.e., everything lumped together in a highly condensed manner.Published on June 5 2004 by Taddese Zicke
The title of this book suggests two things to me. The first is that it provides a complete guide to game coding. Read morePublished on Feb. 17 2004 by Dave Astle
I just wanted to weigh in with my thoughts on this book. I really enjoyed it, no I loved it.
I have an addiction that involves buying every darn programming book released on... Read more
Although the author, in his comment below, points out that correctly-running code is available at his web site, he neglects to note that this code will only work with Visual Studio... Read morePublished on Dec 29 2003
For a complete book it is heavily lacking in many areas... if you want something more complete check out the Introduction to 3D Game Programming with DirectX 9. Read morePublished on Dec 7 2003 by JJ4America
As someone who just has about 3 years of programming experience and is finishing up high school this year, I found this book to very helpful. Read morePublished on Dec 4 2003 by MRom
This is an excellent book. The author clearly is an expert on the subject who has spent years developing mainstream commercial games (eg Ultima series). Read morePublished on Oct. 6 2003 by Codehead
I have studied a lot of the "standard" game coding books recently. This is the first game book I have read that I was sorry when I got to the end because there wasn't any... Read morePublished on Sept. 10 2003 by myob
Look for similar items by category
- Books > Computers & Technology > Graphic Design
- Books > Computers & Technology > Programming > Game Programming
- Books > Computers & Technology > Programming > Graphics & Multimedia
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Deals in Books
- Books > Humour & Entertainment > Puzzles & Games > Video Games & Strategy Guides
- Books > Textbooks > Computer Science & Information Systems > Graphics & Visualization
- Books > Textbooks > Computer Science & Information Systems > Programming Languages