Turn-based Strategy Game - Help

I am trying to create a turn-based strategy game that puts a player-controlled creature against a similar creature controlled by the computer. Having various options available to me, Attack, Special Attack, Dodge, Heal and Re-Charge, all performing their respective roles. This is to be done using the console window.

And of course this is my first University assignment and I'm new to the whole programming in C++. So where'd I start. I'm also expected to produce pseudo-code and flowcharts for this.

While I get extra marks for things like; - Multiple battles against the computer with score kept. - Each player brings multiple creatures to the arena; the victor must defeat all opposing creatures to earn the victory. - Creatures may be of different types with different attributes. - The computer opponent may use an algorithm to determine which action to take, rather than random choices. - Using advanced programming approaches and constructs that lead to high quality code. - Implementing a menu system that allows the player to replay the game or choose between options.

So how does a oblivious C++ programmer get started, note the fact that I know no programming at all and the lecturer has seemed to have thrown me into the deep end here. I'd love to hear your feedback and possible starting points for me. And of course this is incredibly appreciated.

_Ted :)
Start simple, start at the top. Drill down.

The very top is the game loop.

1
2
3
4
5
while (!gameFinished)
{
  // do things

}


Seriously. Get that program running. The aim is to have a working game at every stage.


What things need doing?

1
2
3
4
5
6
7
8
9
10
while (!gameFinished)
{
  informPlayerOfCurrentStateOfGame();
  getPlayerInput();
  processPlayerInput();
  calculateComputerPlayerInput();
  processComputerPlayerInput();

  gameFinished = isGameFinished();
}


Create those functions. Make them do something (just spit out "I'm running" to the screen). Get the whole thing building and running.

Keep going. Each time you break it down a level, you'll see what needs doing. You'll end up seeing what to draw out, what to chart, and so on. By having a working game at all times, you know that when it's time to hand it in you'll have *something* that works.
Might also be worth mentioning.
Whenever you add sth. to your app save it before under a different name so in case you mess up you can easily go back and start again.
Topic archived. No new replies allowed.