A little game

Ir0nRaven · 30 Apr 2003

Hey guys. I'm currently in AP Computer Science 2, and for our end of the year project, we have to write a game. I've decided on a mini-wargame, with some twists (yes, i stole "tickets" from Battlefield 1942. So sue me). Below is the design doc that i whipped up in 20 minutes... read it over and tell me what you think, please. I'm gonna start writing this on monday, i think, and i'd be happy to take any ideas ya'll have. Realize that I can't do 3d graphics... all i can do is little 800x600 images and stuff. So, here it is. It's formatting all wierd, and I don't know why. Don't feel like fixing it now.... it's not too bad to read.


Design Documentation

Metal of War
 

-         
Introduction

o      
Metal of War
is a dos text/graphic based game incorporating varying terrain, multiple types
of weaponry, turn based play, and 3 objective types.

-         
Interface/terrain

o      
Includes Graphical Map, with
capabilities to display the whole battlefield and/or localized parts for greater
detail. Includes map system allowing for water, and 3 levels of terrain and
barriers, to include greater versatility in strategy and attack/defense. Maps
definable via text files, and in later versions, and built in map editor.

-         
Weapons

o      
Army

§        
Infantry Units (Anti Land)

§        
Sniper Units (Anti Infantry)

o      
Navy

§        
Aircraft Carrier (Anti Air / Anti
Ship / Anti Land)

§        
Destroyer (Anti Ship / Anti Air)

o      
Air Force

§        
Bomber (Anti Land / Anti Ship)

§        
Fighter (Anti Ship / Anti Air)

o      
Armor

§        
Tank (Anti Land)

§        
AA (Anti Air)

-         
Play

o      
Player starts off with a base
(indestructible), Spawn point for all units. Has 500 “tickets”, which are used
to buy units, and gained for every kill made.

o      
Stage one of a player’s turn
consists of moving units. Individual units have a certain distance they can move
each turn, and a player may move no more than 10 units per turn.

o      
Stage two consists of a player
attacking any enemy units which are within range of a friendly unit. Hit/damage
points are dependant on a unit’s built in constants of power, and random roles
of a “dice”.

o      
Play moves around the board until
the objective of that game is met and/or one player is out of tickets and out of
units.

-         
Objectives

o      
Capture the flag – Get a friendly
unit within 2 tiles of the enemy base, and grab their flag. Make it back to your
base alive to win. Your flag must be at your base to win. A unit carrying a flag
that is killed will drop the flag at his death spot, and it can only be
retrieved by being carried by a certain unit.

o      
Defend & Destroy – Team A has an
objective. If it is destroyed, they lose. If the team defends the objective for
20 turns (# may be changed), then Team A wins.

o      
Elimination – First team to lose
all it’s units and run out of tickets loses.

-         
Stages of creation

o      
Build map system, including a
position class, and the ability to, using graphics, display the entire map or a
certain section of the map.

o      
Write the army, navy, air force,
and armor (tanks) classes. Create individual ways of displaying them on the map
(such as triangles, squares, etc) and different colors, depending on the team.

o      
Implement unit creation (no
tickets)

o      
Implement the moving system

o      
Implement the attack system

o      
Implement tickets, which are
awarded each time an enemy unit is killed, deducted any time a friendly unit is
lost, and used to buy / repair friendly units.

-         
Stuff I’d like to do, but don’t
know how

o      
Play the game across a network –
on player per computer. Requires a winsock library, and someone to tell me how
to use it.
 
 
 
Copyright David Winslow
April 2003 ir0nraven@houston.rr.com

Ir0nRaven · 30 Apr 2003

Changes:

Name: Metal of Honor (hahaha)

3 new units: Artillery, Submarine, Helicopter, Engineer

only Engineers can capture the flag

screw dice rolling

other changes to come...

Still want ppl's feedback! Thanks to Cygnus for his suggestions in IRC!

Racewiz · 30 Apr 2003

I'm tooting my own horn here and you may see feed back from Oed and Pump.

I work for THQ as a Senior Producer and have worked for Infogrames, been in the industry for almost 8 years now. Your design doc is good. You need to balance what you want to do with what you have time to do. You don't have a time line, you need one. If you don't have a feeling for time your best guess should do. You'll find this with any programing job.

You mentioned screw dice role, about every game made has a "dice role". You can keep that hidden or show it. I like showing the role in early stages of projects. You can then determine play balance and other issues. It also is a good way to determine random events.

You need to define hit points and damage points, What each unit can take or dish out.

This document should not be set in stone. It is a guide line for you as the programmer and if you were to publish it, a guide for the Prodcuer and/or publisher.

Whoha · 30 Apr 2003

Start small and work your way up, like 1 objective, and 1 unit. Some of that is obviously going to get axed.

Whoha · 30 Apr 2003

and just do hotseat for multiplayer

Ir0nRaven · 1 May 2003

Thanks guys, for your input (Racewiz -- timeline is about 2 weeks of 1.5 hrs/day, so it's not big... i probably will not get it all done)

and what's a hotseat?

Ouroboros · 1 May 2003

Hotseat is where one player is playing while the other player is out of the room or not watching. When player one ends his or her turn, the screen goes black or something with a click to continue button. Player two comes in and clicks continue, then it becomes his/her turn while player one leaves or doesn't watch. Kind of boring but it works for a turn based game.

Log in / Register

Forums

A little game

Ir0nRaven

Ir0nRaven

Racewiz

Whoha

Whoha

Ir0nRaven

Ouroboros

Share This Page