Robocode/Game Physics

This page describes the game physics of Robocode.

Coordinates and direction conventions

https://i.imgur.com/7Pkqy65.gif

Coordinates system

Robocode uses the Cartesian coordinate system, which means that that the (0, 0) coordinate is located at the bottom-left corner of the battlefield.

Rotational direction system

Robocode uses a clockwise direction convention where 0°/360° is north, 90° is east, 180° is south, and 270° is west.

Time and distance measurements

Time measurement

Robocode time is measured in "ticks". Each robot gets one turn per tick. 1 tick = 1 turn.

Distance measurement

Robocode's units are basically measured in pixels, with two exceptions. First, all distances are measured with double precision, so you can actually move a fraction of a pixel. Second, Robocode automatically scales down battles to fit on the screen. In this case, the unit of distance is actually smaller than a pixel.

Robot movement physics

Acceleration (a)

Robots accelerate at the rate of 1 pixel/turn/turn. Robots decelerate at the rate of 2 pixels/turn/turn. Robocode determines acceleration for you, based on the distance you are trying to move.

Velocity equation (v)

v = at. Velocity can never exceed 8 pixels/turn. Note that technically, velocity is a vector, but in Robocode we simply assume the direction of the vector to be the robot's heading.

Distance equation (d)

d = vt. That is, distance = velocity * time

Robot, gun, and radar rotation

Maximum rotational rate of robot base

(10 - 0.75 * abs(velocity)) deg/turn. The faster you're moving, the slower you turn.

Maximum rotational rate of gun

20 deg/turn. This is added to the current rate of rotation of the robot.

Maximum rotational rate of radar

45 deg/turn. This is added to the current rate of rotation of the gun.

Bullets

Bullet damage

4 * firepower. If firepower > 1, it does an additional damage = 2 * (power - 1).

Bullet velocity

20 - 3 * firepower

Gun heat generated on firing

1 + firepower / 5. You cannot fire if gunHeat > 0. All guns are hot at the start of each round.

Energy returned on hit

3 * firepower

Collisions

Collision with another robot

Each robot takes 0.6 damage. If a robot is moving away from the collision, it will not be stopped.

Collision with a wall

AdvancedRobots take abs(velocity) * 0.5 - 1 (never < 0).

Robocode processing loop

The order that Robocode runs is as follows:

1. Battle view is (re)painted.
2. All robots execute their code until they take action (and then paused).
3. Time is updated (time = time + 1).
4. All bullets move and check for collisions. This includes firing bullets.
5. All robots move (gun, radar, heading, acceleration, velocity, distance, in that order).
6. All robots perform scans (and collect team messages).
7. All robots are resumed to take new action.
8. Each robot processes its event queue.

Most of this can be gleamed by following the method calls from BaseBattle.runRound() and Battle.runTurn() in the robocode.battle module.

Event dispatch happens from within commands that take a turn. So the call stack when an event is delivered usually looks like this:

Robocode internals → Robot's run method → Robocode internals → Event handler

However, event handlers can themselves make calls that take turns. If one of these happens to generate an event, we might see a call stack like

Robocode internals → Robot's run method → Robocode internals → First event handler → Robocode internals → Second event handler

But this kind of nesting could lead to a stack overflow. Or—more commonly—cases where the first handler finishes up its actions long after the response-provoking situation has passed. Thus, Robocode takes special steps for events generated within event handlers; these measures are implemented in EventManager.processEvents(). In particular, the call stack will get as far as

Robocode internals → Robot's run method → Robocode internals (including processEvents) → First event handler → Robocode internals (including processEvents)

but then the inner processEvents will detect the impending nesting and throw an EventInterruptedException, which unwinds the stack to the catch block in the outer processEvents:

Robocode internals → Robot's run method → Robocode internals (including processEvents)

effectively canceling whatever the running event handler was up to. Next, the event-delivering loop in the outer processEvents resumes delivering events, letting the second event handler execute unnested:

Robocode internals → Robot's run method → Robocode internals → Second event handler

It is possible, though not usually useful, to catch and respond to EventInterruptedExceptions in the first handler instead.

Firing pitfall

Because bullets are fired before the gun is moved, calling setFire() will cause the bullet to leave at the current gun heading. This may seem counter-intuitive if you are used to thinking in terms of pointing a gun, then shooting. It is also inconvenient because you can't call setTurnGun(...) and setFire(...) right after each other (not if you need perfect accuracy, anyway). Most of the time, the error will be so small you won't notice it, but if you're testing a pattern matcher against sample.Walls, you will occasionally spot the bug.

To get the bullet to leave after turning the gun, you will need to use code like this:

long fireTime = 0;
void doGun() {
    if (fireTime == getTime() && getGunTurnRemaining() == 0) {
        setFire(2);
    }

    // ... aiming code ...

    setTurnGunRight(...);
    // Don't need to check whether gun turn will complete in single turn because
    // we check that gun is finished turning before calling setFire(...).
    // This is simpler since the precise angle your gun can move in one tick
    // depends on where your robot is turning.
    fireTime = getTime() + 1;
}

See also

Robocode API

• Robocode API

Beginner Guides

• Welcome to Robocode
• System requirements
• Download and install
• Getting started
• Frequently asked questions
• My First Robot tutorial
• Game physics
• The anatomy of a robot
• Scoring in Robocode
• Using the robot console
• Downloading other robots
• Learning from other robots
• Package your robot
• Articles about Robocode
• Starting Robocode from the command line
• Graphical debugging

External Editors

• Using Eclipse with Robocode
• Creating a project in Eclipse
• Creating a robot in Eclipse
• Running your robot from Eclipse
• Debugging your robot with Eclipse
• Using NetBeans with Robocode
• Using Gradle with Robocode

.NET Robots

• Creating a .NET robot in Visual Studio
• Debugging a .NET robot in Visual Studio
• Robocode .NET API

Links

• Robocode homepage
• Robocode project at SourceForge
• Robocode code repository at GitHub
• Robocode Google Group
• Robocode downloads
• Robocode RSS feed
• LiteRumble
• Robots archive
• Wikipedia entry for Robocode