VBots v0.071 alpha test. Written by David Finch.

Most of the documentation is in the following text files:
	rdk.txt - Explanation of robot specifics and the functions and variables that VBots provides for the robots' use.
	rdk2.txt - Full listing of functions and variables, but not yet added to rdk.txt
	dde.txt - Explanation of how to write programs that communicate with VBots.
	telnet.txt - Explanation of how to communicate with VBots over the internet and other related things.

Other things you should know:
 *VBots requires the Microsoft Script Control. If you don't have it or you have the wrong version you can likely get a copy from the VBots home page.
 *If at any time you would like to prevent multiple copies of VBots from running, putting "noreload" in the parameter list should work.
 *If a robot needs to create an activex object, you will need to check "Allow Unsafe".
 *Scoring multibot matches by "kills only" is good to reduce the possibility of a robot like Target winning.
	
What is VBots:
	VBots is a programming game where you write robots in VBScript or JScript that fight each other (up to 100 robots) in an arena of any size (defaults to 800, but allows up to 30000 units across). The robots can communicate with each other and can also be assigned to teams.

Updates:
v0.03 - first public alpha release of VBRobots
v0.04
	Added match recording and a match viewer, playback is at fixed 54.6 turns/second
	Moved match settings to seperate dialog.
	Arena width and height do not have to be equal.
	Added match rules dialog, enabling people to further customize matches for special contests.
	Added simple file io features for robots, but limited to .rbf files in VBots dir.
	Fixed various bugs.
v0.05
	Name shortened to VBots
	It now saves settings.
	Supports JavaScript robots. Javascript version of Circle included.
	Robots can have custom colors. See circlejs.rba. Colors can be changed in realtime, but to avoid confusion it's not recommended. An all white robot is not recommended either.
	To make the colors easier to see, there is now an option to draw the robots bold.
	A few bug fixes.
	Some dead code removed from sample bots.
	Minor performance improvements.
	Other file extensions recognized: *.vbr;*.vbs=VBScript  *.jsr;*.js=JScript  *.rba=Detect language
v0.06
	Turn order is randomized each game to reduce the possibility of the order that the robots are loaded affecting the outcome. Partly because the second robot placed on the arena has no chance of being near the first.
	It tries harder not to start robots directly in front of each other.
	To allow user influenced robots for debugging or entertainment purposes, robots can get now the mouse position in the arena (mousex,mousey).
	The x,y variables of the robots are now called xpos,ypos to avoid confusion.
	Some more dead code removed from Circle.
	Robots should continue to function even if there is an error.
	Only the first error of each robot is reported.
	JScript version of Circle better suited for multibot situations.
	Added Target, a red and white sample robot that does nothing but charge energy.
	Also added Smallest.rba, the smallest possible robot that can be loaded into a match.
	Changed "fast animation" setting to draw only every other turn.
v0.07
	Clicking on a robot shows constantly updated stats on how it is doing. Right clicking stops tracking.
	Fixed a few bugs that crashed the game.
v0.071
	Realized I left out a vital part of the documentation for robot communication. See the top of rdk.txt for details.
	Fire now demonstrates team communication and energy sharing.
	Fixed a scanning bug.
	Added descriptions to rdk2.txt
v0.072
	Added bug-fix for GetAngle
	Added simple match results window
	Added midi sound (optional)

	

Some future ideas:
	With the sample robots:
		Comment the sample robots.
		Write simpler sample robots.
		Have both JScript and VBScript versions of each.
	With the interface:
		Make timeout settings changeable.
	With the game:
		Look for ways to get around the microsoftness of the script control so that I can add an EndTurn function. Apparently they expect me to write a multithreaded Visual Basic program to overcome their short sightedness.

		

