The prototype contains only one level, and I’m pretty sure that a lot of people out there can do a much better job with level design and color coordination :). The game is very much playable, although I think there are better ways of implementing the ball/brick “physics”.

So this is how it’s going to work (this will be the general routine for most of the games): this first post will include a general overview of the project, and a zip file containing the prototype. The next posts shall discuss how the game was put together. Along the way, I hope to gather comments, suggestions, and help from everyone, and these will all be factored into the next iteration of the project. This process will just repeat itself until we come up with something that most, if not all of us, will be happy about :).

This game was written in Python, using the Pygame library. For me, Python is great to work with, and I would recommend it as a good first programming language. As most of you already know, Python code is very readable, and this is very important for an undertaking like this. I would just like to stress that this project could have been implemented in any other language – the choice of language is mainly due to personal preference.

To understand what’s about to happen, I would consider a working knowledge of Python as a prerequisite. For those of you who already know how to program, I assure you that you can easily pick up Python. With some basic knowledge of C and familiarity with programming, I was able to learn Python by reading the Python Tutorial that comes with the Python package. I think that a weekend is more than enough to go through this tutorial.

For those who haven’t programmed before, the Python website has a Getting Started page, which includes resources for non-programmers. If you’re a non-programmer, I encourage you to give it a shot! I was a non-programmer myself before, and I think that the effort was worth it.

To run the code, you will need to have Python and Pygame installed. Here is the zip file which contains the Arinoid source code and graphics (this should work for Windows, Mac OS X, and Linux).

Hi Johan! Thanks for pointing that out as well – I’ve fixed the link from the pygame site :). I just have to say that this is an early version and hopefully, it will be improved after the screencasts for it are done. I’d love to hear everyone’s ideas!

[…] To run the code for this screencast, you will need to have a data subdirectory containing the Arinoid sprite sheet file. You can easily fulfill this requirement by downloading the arinoid source from the post on Arinoid. Also, this will be needed for most, if not all, of the upcoming screencasts. […]

[…] 1945 is a clone of the popular vertical scrolling shooter 1942. Again, the graphics in the game were taken from the Spritelib by Ari Feldman. This game will serve as the basis for the screencasts once we finish Arinoid. The screencasts will probably begin with screencast 6. In the meantime, I am hoping that you’ll find the source code useful, and just leave a comment on the site if you have any questions . I posted this in advance because one of the site’s readers needed some help with animations, which this game has but Arinoid doesn’t. Aside from animations, this game also features a scrolling background. […]