Plan for John "Cycletronic" Atherton
by J. Alan Atherton · 01/20/2005 (10:33 pm) · 0 comments
This is my first posted .plan. I put a couple of posts on my blog earlier, and thought I should post them here, too. The blog is at alanatherton.blogspot.com if you want to subscribe or something. I do plan on copying my posts here too. Following are the two posts I've made to the blog so far.
posted by J. Alan Atherton at 11:38 AM 0 comments
Wednesday, January 19, 2005
Starting a New Game
Greetings. Since this is the first blog post, I'll explain what I plan to post here. I am a completely independent hobbyist game developer. That means my team consists only of me. I have a few tools (but I always want more, of course), and I'm poised to rattle off a game.
Since I'm a one-man team, I try to do everything. That includes game design, art assets (3D and 2D), coding (all aspects), sound, music, and marketing. Needless to say, it takes a long time this way. I did manage to get one game on store shelves (packaged with others) back in 1998. It's called Booym. The profits from that have stopped coming in, so I'm working on other projects.
For almost a year, I've been dabbling with one idea, called Captain Disaster. The basic gameplay was teams FPS with a goal other than shooting each other. You had to hunt down three different resources, bring them to processing machines, then take the processed material to another machine. Doing that the fastest would constitute a win. I never did really come up with good win critera... but getting that final machine loaded up was the first step. Each resource had different firepower properties... explosive, long-range, or mischief. That also depended on its "refinement." A few days ago, I decided this might not be the most-fun-to-play game. Not even a kind-of-fun-to-play game. It was taking a lot of work and a long time to get things into prototype phase really. I knew it would take at least a year to finish, and I wanted to finish a game sooner.
That leads us to the title... "starting a new game." The new game is (hopefully) much simpler. The gameplay is similar to the 1990-ish arcade game Rampart. You use tetris-like pieces to build a wall around your castle, place cannons, then fire away on the enemy (boats if single player, another castle if multiplayer). My version of the game will introduce a few new things, as well as a different feel. The theme won't be castles. It's not even going to be modern warfare. I haven't solidified what the theme(s) is going to be, so I won't hint at what it's going to look like yet. It's going to be different enough that Atari won't have grounds to sue me out of my pants. Well, at least not for copying their game.
After about 10 hours worth of work (mostly done Saturday) I already have something close to prototype. You can build walls out of single bricks, place cannons, and fire. This is all done with mouse clicking. This is being done with the Torque Game engine (3D), by the way (GarageGames - Torque). The firing is even fairly accurate. It's not perfect, but it might be good enough. There is a bug, though... there's only a 180-degree arc wherein the cannons fire correctly. Outside of that (I say "behind the cannons") the behavior is erratic... they fire straight up or randomly. So there's a bug in the code somewhere.
Before I fix the aiming, though, I'm going to put in some basic tetris-like pieces to build with (instead of single bricks) and the code to check for a closed-in area. You can only build cannons inside such closed areas, so that's an important step. Once those two things are done, the prototype will be playable, but not complete. I plan to change the controls to keyboard and add 2-players-crammed-together-on-the-same-computer support. That way I can play it with my wife. Then I'll start adding new features and have fun with it.
Thursday, January 20, 2005
One Hour of Productivity
The past 24 hours have been fairly productive! I managed to get 1 hour of game dev time into my busy school and work schedule. Last night I scaled the whole map down (trivial in Torque). I also started adding support for arbitrary "tetris-like" pieces. I almost finished, then had to go to a dinner meeting. While there, I tried to come up with an algorithm to find areas surrounded by a wall. I thought I had some good ideas, but each of them failed in one case or another.
After I got home, I looked up an algorithm for finding closed-in areas on a grid (areas surrounded by a wall). It took about 10 minutes to understand how the algorithm works. It's pretty neat, but will be fairly slow on my tentative 256x256 grid. But then it only needs to be done once every couple seconds at most. Optimization can wait.
I woke up early this morning to put in another half hour, and finished up the arbitrary piece code. It still has one small problem, but I'll sort that out soon enough. I also added rotation support, so each piece can be rotated 90 degrees. That's not tied to any controls yet, but that's not difficult. Once I polish off the piece code, I'll go back to the projectile aiming code to get rid of the problems. After that, it's changing the control scheme to use the keyboard for movement and piece rotation/placement. The mouse will be used to control the camera view. After that, the code to check for contained areas, and then it will be half playable!
posted by J. Alan Atherton at 11:38 AM 0 comments
Wednesday, January 19, 2005
Starting a New Game
Greetings. Since this is the first blog post, I'll explain what I plan to post here. I am a completely independent hobbyist game developer. That means my team consists only of me. I have a few tools (but I always want more, of course), and I'm poised to rattle off a game.
Since I'm a one-man team, I try to do everything. That includes game design, art assets (3D and 2D), coding (all aspects), sound, music, and marketing. Needless to say, it takes a long time this way. I did manage to get one game on store shelves (packaged with others) back in 1998. It's called Booym. The profits from that have stopped coming in, so I'm working on other projects.
For almost a year, I've been dabbling with one idea, called Captain Disaster. The basic gameplay was teams FPS with a goal other than shooting each other. You had to hunt down three different resources, bring them to processing machines, then take the processed material to another machine. Doing that the fastest would constitute a win. I never did really come up with good win critera... but getting that final machine loaded up was the first step. Each resource had different firepower properties... explosive, long-range, or mischief. That also depended on its "refinement." A few days ago, I decided this might not be the most-fun-to-play game. Not even a kind-of-fun-to-play game. It was taking a lot of work and a long time to get things into prototype phase really. I knew it would take at least a year to finish, and I wanted to finish a game sooner.
That leads us to the title... "starting a new game." The new game is (hopefully) much simpler. The gameplay is similar to the 1990-ish arcade game Rampart. You use tetris-like pieces to build a wall around your castle, place cannons, then fire away on the enemy (boats if single player, another castle if multiplayer). My version of the game will introduce a few new things, as well as a different feel. The theme won't be castles. It's not even going to be modern warfare. I haven't solidified what the theme(s) is going to be, so I won't hint at what it's going to look like yet. It's going to be different enough that Atari won't have grounds to sue me out of my pants. Well, at least not for copying their game.
After about 10 hours worth of work (mostly done Saturday) I already have something close to prototype. You can build walls out of single bricks, place cannons, and fire. This is all done with mouse clicking. This is being done with the Torque Game engine (3D), by the way (GarageGames - Torque). The firing is even fairly accurate. It's not perfect, but it might be good enough. There is a bug, though... there's only a 180-degree arc wherein the cannons fire correctly. Outside of that (I say "behind the cannons") the behavior is erratic... they fire straight up or randomly. So there's a bug in the code somewhere.
Before I fix the aiming, though, I'm going to put in some basic tetris-like pieces to build with (instead of single bricks) and the code to check for a closed-in area. You can only build cannons inside such closed areas, so that's an important step. Once those two things are done, the prototype will be playable, but not complete. I plan to change the controls to keyboard and add 2-players-crammed-together-on-the-same-computer support. That way I can play it with my wife. Then I'll start adding new features and have fun with it.
Thursday, January 20, 2005
One Hour of Productivity
The past 24 hours have been fairly productive! I managed to get 1 hour of game dev time into my busy school and work schedule. Last night I scaled the whole map down (trivial in Torque). I also started adding support for arbitrary "tetris-like" pieces. I almost finished, then had to go to a dinner meeting. While there, I tried to come up with an algorithm to find areas surrounded by a wall. I thought I had some good ideas, but each of them failed in one case or another.
After I got home, I looked up an algorithm for finding closed-in areas on a grid (areas surrounded by a wall). It took about 10 minutes to understand how the algorithm works. It's pretty neat, but will be fairly slow on my tentative 256x256 grid. But then it only needs to be done once every couple seconds at most. Optimization can wait.
I woke up early this morning to put in another half hour, and finished up the arbitrary piece code. It still has one small problem, but I'll sort that out soon enough. I also added rotation support, so each piece can be rotated 90 degrees. That's not tied to any controls yet, but that's not difficult. Once I polish off the piece code, I'll go back to the projectile aiming code to get rid of the problems. After that, it's changing the control scheme to use the keyboard for movement and piece rotation/placement. The mouse will be used to control the camera view. After that, the code to check for contained areas, and then it will be half playable!
About the author