So, my schedule has been pretty hecktic, so I haven’t updated this place in a while. But I have been working on a few new projects, as well as taking part in the Philly Game Jam. I’ve posted up the page for it – Super Ultimate Ghost Fighter Turbo!(Say what you want, that’s the best title ever).
Also, the Global Game Jam wrapped up yesterday. I wasn’t able to participate, due to me taking a much needed vacation in Vermont. The QuadraTron team, however, got together with a few other people and formed Team Threshold and made an awesome game – Threshold.
So, there. That;s 2 games for ya. That should hold you over until the next time I post (which will (hopefully (Nested!)) be soon!).
OK, first off: No, I’m not dead. 2: No, I’m not a zombie. 3: Yes, zombies are considered dead. 4: I’d like to take a moment to consider a pivotal part of any game programmer’s arsenal of design patterns: The Observer.
The observer pattern, to put it simply, is an object that will only perform a specific action when another object/objects (called “the subject”) are in a particular state. A gentleman by the name of Bob Nystrom is working on an online (and soon physical) book regarding game programming, called GameProgrammingPatterns.com. In his book, he describes the fundamentals and design of the Observer pattern in a fun and simple way that can have even the most basic programmer up-and-running with Observers in no time; like a strange digital voyeur of code.
OK. That was disturbing.
Anywho, go run over to his site, and check out the other “chapters” he’s done. His book is still a WIP, but it’s already a classic. Take care!
One thing I always considered good practice is “If you know what you need, and ‘the wheel’ is over-bloated, it’s OK to reinvent.” I looked at animation systems involving many awesome features, but I wanted something really, really simple. Named after my room mate, here is the Super Simple Animation System (SSAS).
I know i’ve been out for a while – I’ve been SWamped up TO my eaRs in work.
Last month was the Global game jam 2012, and Me, Zenas Bellace and Christian Plummer returned to the battlefield. With the help of Moises Carreras and Matt Catron and George Harris, we dominated. Our task was to make 1 game. We made 3.
Imagine that you’re running at 10 MPH. While you’re running, you throw a ball at 5 MPH. Now, imagine the laws of physics are screwed up and the ball, instead of adding your running velocity to its own, only moves at its 5 MPH. Imagine the look on your face when you try to figure out how the heck you just did that. Imagine the towns’ people accusing you of being a witch and burning you at the stake. Gruesome.
This is (sorta) what happened to me. I instantiated particles, but they didn’t pick up the instantiators’ velocity. Well, here’s a handy script I found, and now I am sharing it to help get your game up to speed (Ugh. I rather just be burned at the stake than to hear another corny pun).
I’m working to get a good portion of my AI up here (in tutorial form) for my Unity 3D Flight Combat game. Since AI is a bit more complicated than a simple flight script, I’ll put it up piece-by-piece in the form of modular devices you can use for other aspects of the game. Today, I’m going to show you how to give your game a bit more insight (These jokes are killing me).