Difference between revisions of "Robocode/Game Physics"
< Robocode
Jump to navigation
Jump to search
(New page: {{stub}} == Robocode Game Physics == Category:Robocode Documentation) |
|||
Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
+ | |||
+ | This page describes the game physics of [[Robocode]] | ||
== Robocode Game Physics == | == Robocode Game Physics == | ||
+ | |||
+ | === Robocode Processing Loop === | ||
+ | The order that Robocode runs is as follows: | ||
+ | |||
+ | # Battle view is (re)painted | ||
+ | # All robots execute their code until they take action (and then paused) | ||
+ | # Time is updated (time = time + 1) | ||
+ | # All bullets move and check for collisions | ||
+ | # All robots move (heading, accelration, velocity, distance, in that order) | ||
+ | # All robots perform scans (and collect team messages) | ||
+ | # All robots are resumed to take new action | ||
+ | # All robots are processing their events | ||
+ | |||
[[Category:Robocode Documentation]] | [[Category:Robocode Documentation]] |
Revision as of 13:59, 28 November 2007
This article is a stub. You can help RoboWiki by expanding it. |
This page describes the game physics of Robocode
Robocode Game Physics
Robocode Processing Loop
The order that Robocode runs is as follows:
- Battle view is (re)painted
- All robots execute their code until they take action (and then paused)
- Time is updated (time = time + 1)
- All bullets move and check for collisions
- All robots move (heading, accelration, velocity, distance, in that order)
- All robots perform scans (and collect team messages)
- All robots are resumed to take new action
- All robots are processing their events