Thread: Storing Monster Stats For Zelda Game

you could specify monster starting points in your map or make them random. when the 'player' enters a part of the screen where a monster position is visible, create the monster. after the monster is killed (or is outside the screen if thats what you want) then delete that instance of the monster object. just keep checking through your list of monsters to see if they are still needed (viewable/alive).

I use structs a lot. They're really easy to use for what you're doing. And since there won't be many mosters on the screen at a time (less than 50 i assume) you could:

A) Create 50 different variables of the struct type you made

B) Create an array of the struct type you made (much better than above answer)

C) Use a linked list with struct (More modular)

D) Use a class and linked list rather than struct and linked list

...there are other options as well. For the given situation I would think choice B is the simplest to implement

STL Vectors will work as well.

Vectors---

http://www.pixelate.co.za/issues/5/5...stl/part1.html

http://www.pixelate.co.za/issues/6/6...tl2/part1.html

both of those links have multiple parts to them...find the link go to the next part of the tutorial look down at the bottom of the page

as for using arrays with classes here is an example...

Code:

class Bla
 {
   public:
    short yippy;
    Bla::Bla();
    bool function();
 };

Bla bla[10];

Also, basically you're constructor is pretty much useless when having an array of objects.

>"Also, basically you're constructor is pretty much useless when having an array of objects"


isnt the constructor called for each object in the array when it is declared?

Originally posted by TechWins
Vectors---

http://www.pixelate.co.za/issues/5/5...stl/part1.html

http://www.pixelate.co.za/issues/6/6...tl2/part1.html

both of those links have multiple parts to them...find the link go to the next part of the tutorial look down at the bottom of the page

as for using arrays with classes here is an example...

Code:

class Bla
 {
   public:
    short yippy;
    Bla::Bla();
    bool function();
 };

Bla bla[10];

Also, basically you're constructor is pretty much useless when having an array of objects.

No it's not. If you don't initialize the array then the default constructor is called. You cAn CAll AN OvERLOADED CONSTRUCTOR BY GOING CRAZY AND DOING THIS!!!!!

Code:

#include <iostream>
using std::cout;

class test
{
public:
	test() { cout << "Default construct"; }
	test(int i) { cout << "Overloaded construct"; }

	~test() { cout << "Please don't kill me!"; }
};

int main(int argc, char **argv)
{
	test mytest[] = { test(2), test(4), test(6) };
        
    return 0;
}

Output:
Overloaded constructOverloaded constructOverloaded constructPlease don't kill me
!Please don't kill me!Please don't kill me!Press any key to continue

Nifty.

No it's not. If you don't initialize the array then the default constructor is called. You cAn CAll AN OvERLOADED CONSTRUCTOR BY GOING CRAZY AND DOING THIS!!!!!

Em, I didn't explain that very well. What I meant is when you initialize the array of objects (i.e. Bla bla[10] ) you don't need to call the constructor any longer. In fact you're not supposed to call the constructor, and you're not supposed to include any sort of processes in the constructor. At least that's true in the method I use, however, I could very well be wrong. I'm not all that up to date on my programming skils right now (haven't been programming for about a month now).

EDIT: Ok, I'm really tired right now, and I think I read your post wrong, too. sad lol