Server Help

[Cyan~Fire]

Are the pointers (eg: Player *p) created by bot events valid until the player leaves the arena, or do they go away after a time limit?
I created an array of player pointers, but there's an error, I think the pointers are invalid...
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[Cyan~Fire]

Nevermind, asked Catid about this one.

[Mine GO BOOM]

[Cyan~Fire]

Yep, sorry.

BTW In case anyone wants to do something using my method:
What I did was create an array of player pointers in the class botInfo ("Player * caps[MAX_TEAMS];") and just store pointers in there from events ("caps[team] = p;"). It's a great way if you need to make a list of players. Just make sure you make a function like this one:

Code: Show/Hide bool botInfo::check_leave(Player *p, int team) //This doesn't have to be a separate function if you don't need it outside of EVENT_PlayerLeave {    if (team > setts.teams)      return false;    if (caps[team] == p)    {       caps[team] = NULL;       //Do stuff       return true;    }    return false; }

Or, if you don't want to specify a team, then just do a for loop.

[ExplodyThingy]

Or just use catid's linked list. Its much less likely to cause an error. For example, say you setup someone in caps[0] through [5], and player [3] leaves. When you iterate through the list, youll succeed on accessing info in caps[0] through 2, but in 3 therell be a null pointer. however, 4 and 5 will still exist. Cats list allows for a Delete method which goes ahead and takes the next item's previous and points it to the one previous, and the previsous's next item and points it to the next.
_________________
There are no stupid question, but there are many inquisitive idiots.
Loot

Dr Brain> I hate clean air and clean water. I'm a member of Evil Conservitive Industries

[50% Packetloss]

yah, everything in datatypes.h is very useful.

[Dustpuppy]

A linked list isn't necessary in this case, an array would do the job better.

[Cyan~Fire]

Yeah, linked list would mean making copies of every single player (lots of memory) and making sure you delete the entries, generally more complicated. I could see using linked list if I needed the players after they leave, but I don't.

[Dr Brain]

Uh, ever hear of pointers? And an array would have the same problem.

Choosing which data structure to use depends highly on the application. If you are going to have relitivly few inserts and deletes (random access), then an array/vector is the way to go, but if instead lookups are less common and you need to do a lot of changing, linked lists are the structure of choice.
_________________
Hyperspace Owner

Smong> so long as 99% deaths feel lame it will always be hyperspace to me

[Plody]

Theyre all pointers to the same block of memory. It wont make new copies of a player in the memory with either case, itll simply make a new refenerence to the same section. If you try to access the player from either of the list forms if the player has left, the core has already deleted the player's info in memory, and youll end up with pointers pointing to no where, and kablow.

The while loop in cats ll checks to make sure the parse pointer exists, which is a node of the list. You should add a "if(parse->item)" in this case, the item being the template class pointing to the Player. If the player doesnt exist, it will resolve false, save you from accessing nonexistant data, and allows you delete the node of the linkedlist.

[Cyan~Fire]

I just don't see why I should use something more complicated when it doesn't need it.

And about the invalid pointers, with that function I have, a player struct shouldn't be removed without that thing activating. It's worked so far.