This wiki was in read-only mode for many years, but can now be edited again. A lot of information will need to be updated.
BZRobots/Ideas: Difference between revisions
Jump to navigation
Jump to search
Spatialguru (talk | contribs) No edit summary |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
This page is to | This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client | ||
= Suggested ideas = | |||
==API functions== | ==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. | * Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions. | ||
== 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 = | ||
* | ==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) | |||
Latest revision as of 18:37, 15 August 2009
Overview
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)