New Text Battle Engine

Hey everyone. I just completed my first "real" game. It's a text battle engine thing. I hope everyone enjoys it. The source code and the executable are in the one .zip file. Tell me what you think and suggestions are welcome. I need them :D

why didnt you use multiple .cpp files instead of .h files?
and color doesnt work on my machine.

[edit] oh and your non standard functions need to be included inside " " instead of < >.
unless you put them in you include folder...

and where is this mystery load.h file?[/edit]

ok color was never implemented into the game. I removed that .h file from my zip program and I accidentally left load.h out. I have now included it in the zip file enjoy. I don't know why I used multiple .h files. I kindof like that. imo it was easy to seperate different functions that way. Why would local include files have to be in " ", is it syntax or is there a difference in the way the compiler reads it? What other comments do you all have? Is the layout for the battle system good. Is it comprehendable? More feedback thanks :D

>I don't know why I used multiple .h files. I kindof like that. imo it was easy to seperate different functions that way.

Dont worry I do the same thing. I completely agree with you.

>Why would local include files have to be in " ", is it syntax or is there a difference in the way the compiler reads it?

There is a difference in the way the compiler reads:

#include <someheader.h>

and

#include "someheader.h"

When you use the < > brackets, the compiler immediately goes to the "include" directory to look for the header file when including it. When you use the " " quotation marks, it searches the path that you give it, which would just be same directory that you are in if you do not give it a path.

>Is the layout for the battle system good.

It is awesome. I like it a lot. It reminds me of the first text game I made, except I didnt spend that much time on the layout :) I focused more on the storyline, but your game is meant just to be a battle engine while my first text game was meant to follow a story, so we had different objectives.

Anyways, I think you built an excellent battle engine there. It works very well, and the output is very clear and readable. I did not look at the code to see if it was portable, but if it is not portable I encourage you to make it portable because it betters your coding habits.

Overall: Excellent job. Good luck on your next project. :cool:

Thank you so much for the positive feed back :D . Yeah my next goal is to learn some open gl and a possibly port the battle algorithms to something with graphics. The eventual goal is something similar to the early final fantasy battle engines for the super nintendo. (I know that is a stretch but it is my long term goal :) )

There was an error that when the character died the window would close really fast. I corrected this problem. It should be fine now. :D

dont worry about color.
color in a console is not easily portable anyway.
your algorithms are good. i need to implement something similar in my text game.

Just one thing to point out. Header files should only have function declarations, not the actual implementations of the functions themselves. You should have 'load.h' contain all of the function prototypes, and then 'load.cpp' include 'load.h', and have the actual code in there. Your 'main.cpp' would then include 'load.h' only.

so what would I put in load.h? I probably could then just make it load.cpp and not have load.h at all then? The way it is coded one function opens up to another. Which might be bad I suppose. I probably would have to just code it completely differently then so that every function ends back in the function that initiated it instead of leading to more and more seperate functions.

yeah it is proper to put only function and variable declarations in the .h file, and then define them in a corresponding .cpp file, but i say to heck with that. That's one of the most annoying proper things to do.

In the case of header files when I create them, I usually have one major class per header file. I declare the class at the top and all of its members, and then below that I define them. That's my preferred way of doing things. It is still organized (class declaration in part 1, definitions in part 2) and takes less files.