Prototype Encounter System

I am now working on an encounter system. I would like to be able to pre-define each monster type, its stats, level etc.. but i don't want to duplicate the combat function for each type of monster and for different levels.


So my plan is kind of for it to go like this


Game() > EncounterCheck() > Combat() > ExperienceCalculator() > Game()


in game You choose an option that triggers encounter
sends you to encounter check which loads specifc variables into global variable for that encounter type, then triggers combat function where you have your fight then triggers my experience levelup system to see if you need leveling etc. then returns back to game.



My thoughts are mainly how do i upon triggering the encounter function load the exact section of code needed to adjust the variables the best i could come up with is a ton of encounter functions just to store the variable transfer routines that way i dont have to duplicate the entire combat function

You should only need one function, and the rest is data

Eg.

Code:

---

struct monster {
  int hitpercent;  // chance of landing a hit
  int maxdamage;  // max damage, if a hit is made
};

---

Then you do

Code:

---

monster wasp = { 100, 1 };  // always stings, but no big deal
monster ogre = { 10, 1000 };  // lumbering brute, but very bad if it hits

---

Your eval function would be

Code:

---

void eval ( monster *m ) {
  if ( m->hitpercent )
  // .... and so on
}

---

Add variables as necessary to parametrize all your monsters.

I have never used structs before, and the chance to hit and other calculations are already part of the combat routine. I plan on storing the monster information in global variables. The only things i need is to figure out which monster and lvl pull the information from the variables and run it through the combat function. Could you post a full example?

> Could you post a full example?
Based on the size of the hole you've dug for yourself already - no.

> I have never used structs before
That's not an excuse for not starting now.

> I plan on storing the monster information in global variables.
If you plan on keeping with bad design, then there's nothing more I can do for you.