Yes! I can now add a couple of bouncing balls to a level, and run it, reset and run it again. I'm there, dog! Next step: a slew of tests, and then back to the game basecode and hook in keyboard controls.
Hah, unit testing actually caught a bug I introduced today. Calling ResetObject after adding it to the space (as I did) set the bodyAddedToSpace flag to false, which broke level teardown. Cool.
Added tests for editor classes Polygon and Floor. Works fine.
Right, how do I set up the input system? I'd like to have the pucks receive commands, but not keys directly, so that I can abstract away the source (have players, network interfaces and AI use the same interface). Granted, the input interface is limited: directions, jumps and weapon activations. That's a grand total of six inputs, that screams "enum".
2 comments:
Hello my friend. Just want to let you know that if you need any kind of help in any kind of way (level design, sketches, bug testing, etc.), please let me know. I just read through your dev log and the entire idea sounds like a very fun project.
P.S. - Remember I said (many, many moons ago) that I was planning on learning Maya... well, I just registered for a 14 week class from my previous college SVA. I have high hopes that this class will really help me get up to speed with modeling, texturing, and other technicalities of 3d game development.
I might well happen to call on your services, my friend. ;) Best of luck with your Maya class, I'm sure you'll do very well!
Post a Comment