This article originally appeared in Dev.Mag Issue 29, released in February 2009
If one had to compile a list of the top ten reasons for envying former Dev.Mag editor-in-chief Rodain “Nandrew” Joubert, coming a close second to his fabulous hair would be his tendency to constantly roll out absolutely fantastic and innovative games. Whodunnit…Think Quickly is no exception to this rule.
This article originally appeared in Dev.Mag Issue 29, released in February 2009.
Last month we covered some of the very basic ways of testing whether object A hits object B. But, while the techniques we covered could quite likely take you very far, you’ll inevitably encounter a time when they simply aren’t enough. So this month we’ll go a little further.
This article originally appeared in Dev.Mag Issue 29, released in February 2009.
This article originally appeared in Dev.Mag Issue 29, released in February 2009.
Game Development. The words have a way of sending a flurry of mathematical equations and complex code lines swirling through one’s head; after all, it’s exactly that which drives a game forward, isn’t it? – having your logical pathways set out so that when objects interact with one another they do what is expected. We get so hammered down on programming and gameplay that it’s easy to forget, particularly at the introductory level of game development, that there’s much more to a game than simply getting the code to compile without any errors. Continue reading
This article originally appeared in Dev.Mag Issue 29, released in February 2009.
I must confess. I hardly ever comment my code. It’s the sort of thing that everybody lectures about, saying that it’s important for clarity, ease of use and even national security in the event of nuclear war. This is all true (though perhaps the nuke idea was a bit of a thumbsuck) and I will always advise others to write miniature essays in their game code.
Unfortunately, I fail horrendously when I need to do it myself.
follow: Dev.Mag on Facebook RSS Tweet with me