This is the last game for this project. My schedule has just been getting too tight, and I need the time elsewhere. Today’s game, though, is Carrier; you run around a ship working on stuff so as to get the carrier moving again.

Here are a some points I collected during the project.

1.If you’re looking to learn a new language, or improve your knowledge of one you already know, projects like these are great. However, if making one game every day doesn’t really fit into your schedule, try going for making a game every week or month. Also, if you’re worried about flooding the internet with low quality games (and turning indie games into the new causal games) you can either jam them all into a single file, or just post screenshots and explanations of them.

2.If your looking to make a game that’s worth playing, but you don’t have a lot of time on your hands, opt for either a text adventure or a point and click. These two genres give you the best work-to-(how-long-its-going-to-take-to-play-the-game) ratio. Note, however, that text adventures can become very complicated very fast; find some way to plan out the one you’re making or your going to end up with a lot of extra work to do (the same probably goes for point and clicks).

3.Arcade games were probably the easiest games to make. They required very little time to get up and running, and ended up being some of the most complete-looking games I made during this project.

4.RTS’, RPG battle systems, and platformers all took a lot more time to get working than I expected they would. Games from these three genres ended being some of the most incomplete looking games I made during this project.

5.Tower defense games I tended to shy away from. I like them when their in the Plants vs Zombies format, (and I made two of them in said format) but otherwise I can’t stand them.

6.I didn’t really do any 3D projects. I made a few games with a 3D perspective (even though there was no actual 3D) but I wasn’t able to add much to them (and one caused what I believe was motion sickness) so I shied away from them.

7.Text adventures and Point and clicks had to be the games I had the most fun making. I was able to add a lot of stuff (most of the time) and a lot of depth with a very small amount of work. I couldn’t learn much from them though, so I only made around three.

8.I didn’t make a lot of games with a top-down perspective, but the ones that I did I’m sorta proud of.

9.The two-player games I made weren’t that good, (Fight! being absolutely terrible) and that’s probably the reason I only made two.

10.I didn’t make any puzzle games. I’m not really sure why…

11.I knew I wouldn’t be able to make a roguelike in an hour, but I still tried. The scrolling bar of text included in rougelikes though was surprisingly easy to make, and I used it in many subsequent projects.

12.I’d like to expand some of the games I made in this project at some point. I think a game like turntextrogue (an RPG done entirely in text) would be both a very fun game to make and a very fun game to play.

13.This project should probably have slowed me down when it comes to working on other projects, but it didn’t. Instead, I finished/started and finished at least three other games during this project: a scrolling shooter, a brick breaker, and an arena shooter.