Plan for Jared Coliadis

Summer classes started up on Monday and I start a part-time summer job next week, drastically cutting into my experimentation time. I have a rather large-scale project in early pre-production stages still, and I'm going to try my hardest to get as many abstract designs down on paper as possible before I actually touch any code. It's still pretty hush-hush, but I can say that it is in vein of 2D Lucasarts adventure games of yore.

I'm going for as small of a dev team as possible to minimize creative conflict/credit sharing. The idea is that each person on the team has a role to hold full responsibility for. Being that the dev team is made up of college students dreaming of one day entering the gaming industry, the idea of creating a "full-scale" game should be looked at less as a product for sale, and more of a product for demonstrating talents in several different fields. I am in charge of programming and gameplay, someone is in charge of the story and dialog (and there will be plenty of it), and hopefully soon we'll be contacting some people at the nearby arts school to handle all of the assets. (If you have played either of my Game In a Day games, you'll know that I need an artist desperately...) Later in production, we will be recruiting more students to handle sound effects, music, and possibly voice-acting.

Being that I'm the one that has to put all of these parts together and make sure they are all formatted correctly, I am essentially leading the project. A dev team with one programmer? I've been continually analyzing what I'm most likely going to encounter, and I still think I can handle it by myself. Yes, there will be testers later, but they will most likely just be black-box. I think that the resources T2D provides give me enough of a start to do it.

I guess I'll find out soon enough.

Now, so this .plan won't be completely pictureless, here is an error I got when trying to fix a neighbor's printer: