BZRobots/Ideas - Revision history

Zehra: redirect, as content has been merged

2025-11-15T05:14:37Z

redirect, as content has been merged

← Older revision		Revision as of 05:14, 15 November 2025
Line 1:		Line 1:
	~~=Overview=~~		#REDIRECT [[BZRobots]]
	~~This page is to collaborate on ideas for the~~ [[BZRobots]] ~~Programmable Computer Player Client~~

	~~= Suggested ideas =~~
	~~==API functions==~~
	* Provide an API for visual targets based on the same rules a player would see.
	** This would only apply to maps using flags
	* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.

	~~== Input ==~~
	* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot
	** What to do when multiple bots are running in the same client?

	~~= Accepted ideas =~~
	~~==Scripting==~~
	* Be able to load multiple modules.
	** A small amount of work in bzrobots client should make this happen

	~~= Rejected ideas =~~
	~~==API functions==~~
	* Have methods to compute travel paths to desired locations, with updates for moving targets.
	** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)
	* Add a getTank(callsign) function
	** (Rejected due because BZRobots now supports the onScannedPlayer event)

Bulldozer at 18:37, 15 August 2009

2009-08-15T18:37:44Z

← Older revision		Revision as of 18:37, 15 August 2009
Line 1:		Line 1:
	=Overview=		=Overview=
	This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client		This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client

	~~= Implementation ideas =~~
	* [[BZRobots/ShotsAndEnemies]]

	= Suggested ideas =		= Suggested ideas =
	~~==Scripting==~~
	* Be able to load multiple modules.

	==API functions==		==API functions==
	* Provide an API for visual targets based on the same rules a player would see.		* Provide an API for visual targets based on the same rules a player would see.
			** This would only apply to maps using flags
	* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.		* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.
	* Have methods to compute travel paths to desired locations, with updates for moving targets.
	* Add a getTank(callsign) function

	== Input ==		== Input ==
	* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot		* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot
			** What to do when multiple bots are running in the same client?

	= Accepted ideas =		= Accepted ideas =
	* Add support for getShots() in BZAdvancedRobot - return a list of shots (class Shot)		==Scripting==
	* ~~Add support for a Shot class~~		* Be able to load multiple modules.
	** getPosition(dt) -return position after dt seconds as is assumed		** A small amount of work in bzrobots client should make this happen
	** getType() - normal? gm? laser? ...
	** ~~getHeading() - which way is the shot heading?~~
	** getShooter() - who shot it? at least own shots should ~~be distinguished because on no-rico servers we could just throw them away when doing collision forecasts~~
	** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id
	* Add support for getPlayers() in BZAdvancedRobot - return a list of players (class Tank)
	* Add support for a Tank class
	** getPosition(dt) - return position after dt seconds as is assumed
	** getVelocity() - return current velocity
	** getAngularVelocity() - return current angular velocity, i.e. how fast it is turning
	** getHeading() - which way the bot is heading?
	** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id

	= Rejected ideas =		= Rejected ideas =
Line 38:		Line 21:
	* Have methods to compute travel paths to desired locations, with updates for moving targets.		* Have methods to compute travel paths to desired locations, with updates for moving targets.
	** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)		** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)
			* Add a getTank(callsign) function
			** (Rejected due because BZRobots now supports the onScannedPlayer event)

Bulldozer: Undo revision 6589 by Bulldozer (Talk)

2009-08-04T06:10:55Z

Undo revision 6589 by Bulldozer (Talk)

← Older revision	Revision as of 06:10, 4 August 2009
Line 1:	Line 1:
		=Overview=
		This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client

		= Implementation ideas =
		* [[BZRobots/ShotsAndEnemies]]

		= Suggested ideas =
		==Scripting==
		* Be able to load multiple modules.

		==API functions==
		* Provide an API for visual targets based on the same rules a player would see.
		* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.
		* Have methods to compute travel paths to desired locations, with updates for moving targets.
		* Add a getTank(callsign) function

		== Input ==
		* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot

		= Accepted ideas =
		* Add support for getShots() in BZAdvancedRobot - return a list of shots (class Shot)
		* Add support for a Shot class
		** getPosition(dt) -return position after dt seconds as is assumed
		** getType() - normal? gm? laser? ...
		** getHeading() - which way is the shot heading?
		** getShooter() - who shot it? at least own shots should be distinguished because on no-rico servers we could just throw them away when doing collision forecasts
		** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id
		* Add support for getPlayers() in BZAdvancedRobot - return a list of players (class Tank)
		* Add support for a Tank class
		** getPosition(dt) - return position after dt seconds as is assumed
		** getVelocity() - return current velocity
		** getAngularVelocity() - return current angular velocity, i.e. how fast it is turning
		** getHeading() - which way the bot is heading?
		** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id

		= Rejected ideas =
		==API functions==
		* Have methods to compute travel paths to desired locations, with updates for moving targets.
		** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)

Bulldozer: Removing all content from page

2009-08-04T06:09:47Z

Removing all content from page

← Older revision		Revision as of 06:09, 4 August 2009
Line 1:		Line 1:
	~~=Overview=~~
	~~This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client~~

	~~= Implementation ideas =~~
	* [[BZRobots/ShotsAndEnemies]]

	~~= Suggested ideas =~~
	~~==Scripting==~~
	* Be able to load multiple modules.

	~~==API functions==~~
	* Provide an API for visual targets based on the same rules a player would see.
	* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.
	* Have methods to compute travel paths to desired locations, with updates for moving targets.
	* Add a getTank(callsign) function

	~~== Input ==~~
	* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot

	~~= Accepted ideas =~~
	* Add support for getShots() in BZAdvancedRobot - return a list of shots (class Shot)
	* Add support for a Shot class
	** getPosition(dt) -return position after dt seconds as is assumed
	** getType() - normal? gm? laser? ...
	** getHeading() - which way is the shot heading?
	** getShooter() - who shot it? at least own shots should be distinguished because on no-rico servers we could just throw them away when doing collision forecasts
	** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id
	* Add support for getPlayers() in BZAdvancedRobot - return a list of players (class Tank)
	* Add support for a Tank class
	** getPosition(dt) - return position after dt seconds as is assumed
	** getVelocity() - return current velocity
	** getAngularVelocity() - return current angular velocity, i.e. how fast it is turning
	** getHeading() - which way the bot is heading?
	** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id

	~~= Rejected ideas =~~
	~~==API functions==~~
	* Have methods to compute travel paths to desired locations, with updates for moving targets.
	** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)

Bulldozer: /* Accepted ideas */

2009-08-04T06:03:19Z

Accepted ideas

← Older revision		Revision as of 06:03, 4 August 2009
Line 23:		Line 23:
	** getPosition(dt) -return position after dt seconds as is assumed		** getPosition(dt) -return position after dt seconds as is assumed
	** getType() - normal? gm? laser? ...		** getType() - normal? gm? laser? ...
			** getHeading() - which way is the shot heading?
	** getShooter() - who shot it? at least own shots should be distinguished because on no-rico servers we could just throw them away when doing collision forecasts		** getShooter() - who shot it? at least own shots should be distinguished because on no-rico servers we could just throw them away when doing collision forecasts
	** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id		** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id
			* Add support for getPlayers() in BZAdvancedRobot - return a list of players (class Tank)
			* Add support for a Tank class
			** getPosition(dt) - return position after dt seconds as is assumed
			** getVelocity() - return current velocity
			** getAngularVelocity() - return current angular velocity, i.e. how fast it is turning
			** getHeading() - which way the bot is heading?
			** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id

	= Rejected ideas =		= Rejected ideas =

Bulldozer at 05:59, 4 August 2009

2009-08-04T05:59:39Z

← Older revision		Revision as of 05:59, 4 August 2009
Line 1:		Line 1:
	=Overview=		=Overview=
	This page is to ~~describe the community~~ ideas for the BZRobots ~~API that is to be provided as part of the~~ Programmable Computer Player Client ~~project for the Google Summer Of Code~~		This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client

	= Implementation ideas =		= Implementation ideas =
	* [[BZRobots/ShotsAndEnemies]]		* [[BZRobots/ShotsAndEnemies]]

	= ~~Feature~~ ideas =		= Suggested ideas =
	==Scripting==		==Scripting==
	* Integrate python as a scripting language on top of C++		* Be able to load multiple modules.
	* Be able to load ~~C++ or python~~ modules ~~transparently~~.

	==API functions==		==API functions==
			* Provide an API for visual targets based on the same rules a player would see.
	* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.		* Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.
	* Provide an API for visual targets based on the same rules a player would see.
	* Have methods to compute travel paths to desired locations, with updates for moving targets.		* Have methods to compute travel paths to desired locations, with updates for moving targets.
			* Add a getTank(callsign) function

	== Input ==		== Input ==
	* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot		* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot

	=~~See Also~~=		= Accepted ideas =
	* ~~[[Google_Summer_of_Code\|Google Summer~~ of ~~Code]]~~		* Add support for getShots() in BZAdvancedRobot - return a list of shots (class Shot)
	* [[BZRobots~~/About]]~~		* Add support for a Shot class
			** getPosition(dt) -return position after dt seconds as is assumed
			** getType() - normal? gm? laser? ...
			** getShooter() - who shot it? at least own shots should be distinguished because on no-rico servers we could just throw them away when doing collision forecasts
			** unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id

			= Rejected ideas =
			==API functions==
			* Have methods to compute travel paths to desired locations, with updates for moving targets.
			** (Rejected as it defeats the purpose of BZRobots as an AI learning tool)

Gilly at 21:33, 19 February 2008

2008-02-19T21:33:23Z

← Older revision		Revision as of 21:33, 19 February 2008
Line 1:		Line 1:
	=Overview=		=Overview=
	This page is to describe the community ideas for the BZRobots API that is to be provided as part of the Programmable Computer Player Client project for the Google Summer Of Code		This page is to describe the community ideas for the BZRobots API that is to be provided as part of the Programmable Computer Player Client project for the Google Summer Of Code

			= Implementation ideas =
			* [[BZRobots/ShotsAndEnemies]]

	= Feature ideas =		= Feature ideas =

Spatialguru at 21:43, 9 July 2007

2007-07-09T21:43:16Z

← Older revision		Revision as of 21:43, 9 July 2007
Line 11:		Line 11:
	* Provide an API for visual targets based on the same rules a player would see.		* Provide an API for visual targets based on the same rules a player would see.
	* Have methods to compute travel paths to desired locations, with updates for moving targets.		* Have methods to compute travel paths to desired locations, with updates for moving targets.

			== Input ==
			* Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot

	=See Also=		=See Also=
	* [[Google_Summer_of_Code\|Google Summer of Code]]		* [[Google_Summer_of_Code\|Google Summer of Code]]
	* [[BZRobots/About]]		* [[BZRobots/About]]

Daxxar: /* See Also */

2007-06-27T15:58:38Z

JeffM2501: /* See Also */

2007-06-26T16:53:40Z

← Older revision		Revision as of 15:58, 27 June 2007
Line 13:		Line 13:

	=See Also=		=See Also=
	[[Google_Summer_of_Code\|Google Summer of Code]]		* [[Google_Summer_of_Code\|Google Summer of Code]]
			* [[BZRobots/About]]

← Older revision		Revision as of 16:53, 26 June 2007
Line 13:		Line 13:

	=See Also=		=See Also=
	[[Google_Summer_of_Code]]		[[Google_Summer_of_Code\|Google Summer of Code]]