Why not just make all positions same like for 8 bots and if theres 2 use only 1 and 2 it doesnt matter that they are not facing eachother or are not symetrical.
For this reason: I think as far as the championship ladder goes, all matches should be held in symmetrical arenas, which means it really is up to the bot's AI. But for casual matches, more casual arena layouts/random placement (based on seed #) would be good. -- Toby Zuydveld
For casual games, it wouldn't matter, but I think for Championship games, the only fair method would be to have completely symmetrical layouts. It really wouldn't be that hard anyways. 4 arenas x 4 layouts = 16 arenas. 4 of the arenas are completely open spaced and would take an experienced modeler less than 5 minutes to create them.As for the other 12, they don't have to be anything exotic. This is a community project, not a commercial one.
I think the Arena.dat and arena.bb are needlessly complex and might also make for creating arenas pretty tedious if you are trying to make any walls because you might make walls over starting positions.
I do agree that the arenas.dat file is a bit complex. I created it with the idea that it would suffice for now, and could be changed later. For instance, the bots starting positions could later be determined by placing nodes in with each arena model marking starting positions. But, since we don't have any arenas yet, or loading code for them, the arenas.dat file was a temporary move. I don't see what ArenaUpdate() could be used for
You never know. Mostly, it just complies with the coding conventions laid out... But THEN AGAIN since i like versatility, might as well have that in a file.
Exactly. Modifying Tournament rules only requires updating a .dat file and doesn't require recompiling any code.-------------------------------
Unfortunately, I'm going to be very busy this week with personal tasks I need to take care of, so I won't be helping out much this week. Don't let this stop anyone else from helping out though...