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

From BZFlagWiki
Jump to navigation Jump to search
No edit summary
Bulldozer (talk | contribs)
No edit summary
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Feature ideas =
=Overview=
This page is to collaborate on ideas for the [[BZRobots]] Programmable Computer Player Client


Here '''everyone''' can post their feature suggestions for the new BZRobots :-)
= 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==
==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.
** A small amount of work in bzrobots client should make this happen


= Rejected ideas =
==API functions==
==API 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.
** (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)