Dropshot

NicEastvillage edited this page Nov 4, 2018 · 36 revisions

As of August 19. 2018 the RLBot framework officially supports Dropshot with access to locations and states of floor tiles. This page contains information and useful values related to the Dropshot game mode.

To make RLBot start a Dropshot game you have to set the following values in rlbot.cfg:

game_mode = Dropshot
game_map = DropShot_Core707

Tiles

There are 140 tiles in total. Locations and owning team can be found in the agent's FieldInfo as GoalInfo objects. In Python self.get_field_info().goals will be a list of the floor tiles with following attributes:

GoalInfo: {
  'team_num': int,
  'location': Vector3,
  'direction': Vector3,
}

Example: To access the location of tile 0 in Python, write: self.get_field_info().goals[0].location

A list of all locations can be found here.

To access the state of tile 0 in Python, write: packet.dropshot_tiles[0].tile_state. This is an integer which corresponds to:

  • 0: Unknown
  • 1: Filled
  • 2: Damaged
  • 3: Open

The tiles will be sorted the same way in FieldInfo and GameTickPacket so indices match.

The tiles are hexagonal in shape. The distance between centres is 768 uu (except for the middle where the distance from blue tiles to orange tiles is 256 uu. A neutral strip about 128 uu wide covers the tiles partially). The image below shows the relative dimensions of a Dropshot tile.

A Dropshot tile's dimensions

Arena

The tiles are layed out in rows of 7,8,9,10,11,12,13 |middle| 13,12,11,10,9,8,7. Where tile 0 is in the blue corner (back left if you are on blue team) and tile 139 is in an orange corner (back left if you are on the orange team).

The overall layout of the arena and tile indices can be seen below.

Layout of Core707

The arena is a regular hexagon except its rounded corners. Here are some dimensions:

  • Center: (0, 0)
  • Floor level: 3.2 uu
  • Center to wall: 4555 uu
  • Center to corner: 5026 uu
  • Center to corner (without rounding walls): 5259.66 uu
  • Wall length: about 5026 uu
  • Arena height: 1986 uu

Note that the tiles on the boundaries are not complete - the rounded base of the walls overlaps the tiles to varying degrees (approximately 30-40% of the tile is overlapped, and the tile centrepoints are always visible).

You may notice that tiles' location are at z=0, but floor level is z=3.2. This is because the tiles has a thickness.

Within arena script

Here's a small script to check if a point is within the arena:

def is_within_arena(point):
	HEIGHT = 1986
	TO_WALL = 4555
	TO_CORNER = 5260  # 4555 / math.sin(60)
	
	if point.z < 0 or HEIGHT < point.z:
		return False
	
	ax = abs(point.x)
	ay = abs(point.y)
	
	if TO_CORNER < ax or TO_WALL < ay:
		return False
	
	return TO_WALL * TO_CORNER - TO_WALL * ax - 0.5 * TO_CORNER * ay >= 0;

Ball

Ball radius: 102.24 uu

The GameTickPacket contains Dropshot info about the ball. It can be found in the DropshotBallInfo object at packet.game_ball.drop_shot_info which contains the variables: absorbed_force, damage_index, and force_accum_recent.

The ball has three phases. The current phase is the variable damage_index where:

  • 0: Normal
  • 1: Charged
  • 2: Super Charged

The ball gains charge as it is hit by cars. When a car exerts a force on the ball, the ball charges up equal to the magnitude of the force (energy). The ball enters the next phase when it reaches a certain threshold:

  • Charged: 2500 energy
  • Super Charged: 11000 energy

The current amount of energy (force absorded) is the absorbed_force variable.

However, a hit does not always charge the ball. To make the ball charge up, the impact must be at least 500 energy, otherwise the ball will not charge at all. Furthermore, when the ball gets hit, it will temporarily accept less energy. The variable force_accum_recent stores the accumulated absorbed force (energy), but no more than 2500 energy. It decays over time at a rate of 2500 energy per second, and the ball will at most absorb 2500 - force_accum_recent energy on a hit. Combined, this prevents players from charging the ball too quickly, limited to 2500 energy every second.

Example: if you hit the ball with an impact of 2000 uu/s at t=0, and you hit the ball again with a force of 2000 uu/s at t=0.5, the force_accum_recent has decayed by 1250 and will be 750 when you hit the ball the second time, and therefore the ball will not accept more than 1750 energy, which means 250 energy gets lost.

The ball's charge is reset, whenever it damages a floor tile owned by the opponent of whoever last touched the ball. To make damage the ball must hit the tile with a velocity of 250 uu/s or more perpendicular to the surface of contact. The side of a tile can only be hit if there's an open tile next to it, so usually the ball will hit the top of the tiles, and in those cases only the Z velocity matters, and must be 250 uu/s or more to make damage. There is also must have passed 0.2 seconds since the last time the ball damaged a tile.

You can tell which team last hit the ball by checking the packet.game_ball.latest_touch object. See Input and output for more.

At kickoff the ball is launched straight up into the air with a velocity of 1000 uu/s and reaches a height of about 847 uu in 1.54 seconds.

Spawning

You always spawn with 100 boost.

Kickoff spawn locations are similar to soccer spawn locations, but not identical. In dropshot spawn locations are:

Kickoff Blue Orange
Right corner loc: (-1867, -2379), yaw: 0.25 pi loc: (1867, 2379), yaw: -0.75 pi
Left corner loc: (1867, -2379), yaw: 0.75 pi loc: (-1867, 2379), yaw: -0.25 pi
Back right loc: (-256.0, -3576), yaw: 0.5 pi loc: (256.0, 3576), yaw: -0.5 pi
Back left loc: (256.0, -3576), yaw: 0.5 pi loc: (-256.0, 3576), yaw: -0.5 pi
Far back center loc: (0.0, -4088), yaw: 0.5 pi loc: (0.0, 4088), yaw: -0.5 pi
Demolished Blue Orange
Right corner loc: (-2176, -3408), yaw: 0.5 pi loc: (2176, 3408), yaw: -0.5 pi
Left corner loc: (2176, -3408), yaw: 0.5 pi loc: (-2176, 3408), yaw: -0.5 pi

Boost regeneration

In Dropshot you regenerate boost at a rate of about 10 boost/sec. However, you do not regen boost while boosting. When you stop boosting (or run out of boost), there is a delay of about 0.5 second before you start gaining boost again. If you are at 0 boost and boost button is pressed, the timer will reset every 0.5 seconds until the button is released.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.