https://wiki.bzflag.org/api.php?action=feedcontributions&feedformat=atom&user=Gilly 2026-04-06T20:50:27Z User contributions MediaWiki 1.43.5 https://wiki.bzflag.org/index.php?title=BZRobots/ShotsAndEnemies&diff=4088 2008-02-19T21:38:27Z

<p>Gilly: New page: = Overview = This page lists some ideas and issues in delivering the shot and player info to Frontend from Backend. = Shots = == In BZAdvancedRobot == * getShots() -type of functions (g...</p> <hr /> <div>= Overview =<br /> <br /> This page lists some ideas and issues in delivering the shot and player info to Frontend from Backend.<br /> <br /> = Shots =<br /> <br /> == In BZAdvancedRobot ==<br /> * getShots() -type of functions (get all shots, shots in certain volume, ...) return a list of shots (class Shot)<br /> <br /> == In Shot ==<br /> * getPosition(dt) -return position after dt seconds as is assumed<br /> * getType() - normal? gm? laser? ...<br /> * 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<br /> <br /> * unique identifier so that frontend and backend can refer to individual shots: can be composed using player id and shot id<br /> <br /> = Players =<br /> <br /> == About the current Tank system ==<br /> <br /> * We can only get all the players at the same time and all the information is sent too<br /> * Sending callsigns there is a problem with spaces in callsigns (i haven't tested it but I'd assume so)<br /> <br /> What could be instead?<br /> <br /> == In BZAdvancedRobot ==<br /> * getPlayers() -type of functions return a list of players (class Tank)<br /> <br /> == In Tank ==<br /> * getPosition(dt) -return assumed position after dt seconds, &quot;Haha meet my bullet there!&quot;<br /> * getVelocity() -return current velocity, &quot;So that's the speed you got&quot;<br /> * getAngularVelocity() -return current angular velocity, &quot;It's turning to face us! Fire!&quot;<br /> * getHeading() -which way the bot is heading? &quot;ARGH It's aiming us!&quot;<br /> <br /> * unique identifier so that frontend and backend can refer to individual players: we got playerid<br /> <br /> = Issues =<br /> <br /> Functions in Tank and Shot will have to call backend. Should we make a<br /> separate request for each of them or some kind of general<br /> &quot;GetShotInfoRequest &lt;command&gt; [arguments]&quot; ?<br /> <br /> Are there functions ready in bzflag to ask for assumed positions of tanks<br /> or bullets after dt seconds without updating them first?</div>

Gilly https://wiki.bzflag.org/index.php?title=BZRobots/Ideas&diff=4087 2008-02-19T21:33:23Z

<p>Gilly: </p> <hr /> <div>=Overview=<br /> 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 <br /> <br /> = Implementation ideas =<br /> * [[BZRobots/ShotsAndEnemies]]<br /> <br /> = Feature ideas =<br /> ==Scripting==<br /> * Integrate python as a scripting language on top of C++<br /> * Be able to load C++ or python modules transparently.<br /> <br /> ==API functions==<br /> * Provide global, team, admin, and report chat APIs so bots can communicate just like players, perhaps with some parsing helper functions.<br /> * Provide an API for visual targets based on the same rules a player would see.<br /> * Have methods to compute travel paths to desired locations, with updates for moving targets.<br /> <br /> == Input ==<br /> * Allows input of coordinates/properties from stdin, so info from other apps, gps, etc. can be pumped into the bot<br /> <br /> =See Also=<br /> * [[Google_Summer_of_Code|Google Summer of Code]]<br /> * [[BZRobots/About]]</div>

Gilly