eek. Actually i got the feeling we need to get something working first before even considering squad behaviour. Does this sound fuzzy? Don't bother then
Squad behaviour, i'd prefer the 'c&c method' (botman called it different though..., but meant the same). Ie, for each team its like a seperate class/machine 'watches over' the map. And places the pieces/bots to specific areas. And so it will send 2 bots here, 2 bots there, 3 bots here. Thats more like basic implementation of 'squad' behaviour. Actually, i would need a precise definition of 'squad behaviour'...
Anyhow, when coming into tight areas, its more difficult. Like storming through a door. One opens, 1 throws in a grenade, then the rest goes in and does a clean sweep. That kind of stuff would be tough. But... i can imagine you have a 'short list' of actions to do when you are encountering a door with multiple bots. However, here comes problem no1. You have to determine IN and OUTside. Then you have to determine, 1st time, 2nd time, ie, worthy to do the action list. And even apart from that, you have to make sure that bots know their tasks. It sounds pretty complicated to me for such a thing. Yet its not impossible
