DataMaster says:

"And because the capture cog captures individual things, it is usually used to handle specific things that have a special role in the game. A capture cog can capture as many things as needed. "

I would like to be able to handle all walkable architecture things messages in one cog. Can this be done with a single cog, using an array of things for instance?

Also, is there a maximum array size in cog? I've only gone up to 70-80...and I probably never even used half of that.

Yeah, you could loop through all of the things using CaptureThing(). But is there some reason you have to capture them? Why not just use a class cog - i.e., just add cog=whatever.cog to the template.



Cogs don't really use arrays so much as they use offset numbers. Say you have:

int red
int blue
int green

red[0] is red, red[1] is blue, and red[2] is green. I doubt they even have to be the same type. So it depends on the size of the variable type you use (e.g., a vector is three times as large as a flex) - you can have as many variables in your array as the cog has room for. And the exact size no one knows.

Ok, cool. Yeah, I knew about arrays actually being just a consecutive set of variables...but just how many variables can on cog have? Are you saying its virtually endless? (i.e., no one has met a limit)

Oh, there is a limit, but I don't know off-hand what it is. I believe it's relatively high, though; I've never had a probem with hitting the limit.

The limit is probably over 100, since rbots uses an array of size 100, and Warlord's cog had over like 120 sectors in an array...

And I'm sure it's clear by now, but a capture cog is like a secondary class cog, just assigned to a thing differently.

Too bad there isn't a CaptureSurface() or CaptureSector() verb of some sort -- those would have been handy on several previous occasions.

Ok, thanks guys. I think I'll probably just end up going with a class cog anyway and just attach it to the parent template of all the walkstructures.