I''m interested in seeing how other people are handling their bot, particularly in terms of movement. Hopefully I can get some ideas regarding my current method of making my bot turn, or maybe give others some ideas. In my bot, I store my current direction as a float (MyDirection). Since it is impossible(?) to figure out the "standard" directions (0 degrees on top, 90 degrees to the right or left, then 180, etc...) I simply assign what ever direction my bot is facing at the beginning as 0 degrees. Instead of using the built in g_pCore->Turn functions, I coded my own. Well, I still use the Turn() functions, but when I call my version of it, it automatically updates my direction (degrees) by an amount, depending on the speed (it''s easy to calculate; ie: TURN_FAST = 180 units per game second * .02222 (amount of time per update) and you get a delta of 4 degrees per update) My function looks a little bit like this:

void Flint::TurnRight(int Speed)
{
	g_pCore->TurnRight(Speed);
	MyDirection += DegreesPerUpdate;

	//bounds checking on the amount of degrees (0 to 360)

	if (MyDirection >= 360.0f)
	{
		MyDirection = MyDirection - 360.0f;
	}
};

Whenever I want to avoid something (if by turning), I store my target direction (the direction I want to end up in after the turn) I then set the State of my bot to TURN (an enumerated type) Every update, my state selector function is called (is this what is considered a finite state machine?), it looks for the TURN case, and executes my TurnToBearing() function. Depending on whether my current direction is higher or lower than my target direction, I will call g_pCore->Turn() until I reach the desired bearing. Once that''s done, I set the state to MOVE again. So basically, my state selector keeps jumping to the TURN case, until the desired direction is reached. Any thoughts on my method? Anyone else do something different? Yes, it is a contest, but since there are no prizes ATM, I think it would be fun to see what everyone is thinking, and share your own. Peon

Lol, well, I''d probably take a look at the code if I knew how, but I don''t, so you''re safe Actually, I don''t care much about putting my source code up so far, if anyone''s interested. It doesn''t fire or anything yet, but it might give (complete newbies) some ideas