bluePrintsBook

I have a little saying, “If you are not passionate about what you are learning about, you will struggle to learn.” Meaning, that if you are studying something that you have no interest in, then the yield of studying that ‘something’ becomes substantially less that if you were to study something you are really interested in. I got into the 4th chapter of the previously discussed book, and it began talking about shaders. Shaders are in fact interesting to me, but I was really in a groove with building out little games while learning. So I swapped books.

If you are not passionate about what you are learning about, you will struggle to learn.

Enter Unity 5.x Game Development Blueprints. I moved over to this book and instantly became engrossed in the first game they had you build. It is labeled a ‘Twin Stick Shooter’, which was an Asteroid like shooter game. But instead of blowing up Asteroids, you defeat endless waves of enemy ships. At least that is the first chapter. The second chapter is all about setting up Menus. Which I had already tackled in the previous book, but this one did such a damn good job explaining things, I stuck with the Chapter.

TwinStick

Further more, I got the chance to really take what they had started, and add some code polish to make it a little more of a circular experience. While the code they had you write did a good job getting the basics of the game down, I really feel like all games should have a Beginning, a Middle, and an End. Specifically, they lacked Ending all together. Let the player know how they did, and give them a chance to do it all over again. Super important stuff.

In any case, I had to write that code. Which is great, because if you know anything about me and my educational methodologies, you know how important the ‘Write’ phase is. In any case, I am super happy with how it all wrapped up, and it even gave me a chance to plug in some of my own space art. I am going to continue with the Blueprints book as it covers more 2D focused concepts, which I think is a good place for me to learn at the moment.

Still loving this whole process, and yes, the GitHub updates are daily and constant.