Qrow: 1 revision imported

2026-02-24T06:08:39Z

1 revision imported

← Older revision	Revision as of 23:08, 23 February 2026
(No difference)

interaidev>Paulomorfeo at 21:59, 22 October 2014

2014-10-22T21:59:37Z

New page

[[AI:Development|AI Development]] < AI Development - The maps

=The maps provided by the AI Interface=
The SpringRTS engine has a 3 Dimensional game area (x; y; z) but it works by mapping the dimensions X and Z (the ones we see when looking from above) into several bi-demensional "maps", each representing a different game mechanic. This page describes how the Interface exposes those maps to the AI.

== Maps available ==
The game area is broken down into (at least) these maps:
* HeightMap - map of terrain heights.
* SlopeMap - TODO
* CornersHeightMap - TODO (complicated...)
* LosMap - map of where in the game area you have visibility (Line of Sight).
* RadarMap - map of where in the game area you have radar coverage.
* JammerMap - map of where in the game area you have radar-jamming coverage.
* ResourceMapRaw - map of where in the game area there is metal and/or other resources.
Additionally, there's the game area which is where the units will exist, but is not "mapped" - units will be at position (x; y; z) in the game area but no map for it exists.

== Interface exposure ==
Each of the maps is bi-demensional (x; z), representing the dimensions "x" and "z" of the game area (x; y; z). However, the Interface exposes each map as a '''list''' of values.
<code><pre>List<float> heightMap = _Callback.getMap().getHeightMap();</pre></code>
This list will contain each row (dimension X) sequentially (Z0, Z1, Z2, ...). Therefore, each position <code>(x;z)</code> of each map will exist in the list at the index <code>(x + z * {map's width})</code>.

== Granularities ==
The game areas are large battlefields and the engine does not map them unit by unit. Instead it breaks down the game area in blocks - "granularity" (http://en.wikipedia.org/wiki/Granularity) - creating maps much smaller than the game area. Additionally, each map has a different granularity and, thus, a different size.

The map HeightMap should be considered the main map and the sizes of all other maps (as described in the documentation) are relative to the size of that map.

* HeightMap - main map (ex: 256x256)
* Game area - the game area will be the HeightMap * 8 (ex: 2048x2048)
* SlopeMap - 1/2 the size of the HeightMap (ex: 128x128)
* CornersHeightMap - TODO (complicated...)
* LosMap - size is variable per mod: see below
* RadarMap - 1/8 the size of the HeightMap (ex: 32x32)
* JammerMap - 1/8 the size of the HeightMap (ex: 32x32)
* ResourceMapRaw - 1/2 the size of the HeightMap (ex: 128x128)

== LosMap ==
The map of Line-of-sight has a granularity that is specified per game ("mod"). Each "mod" will specify the property LosMipLevel:
<code><pre>int losMipLevel = _Callback.getMod().getLosMipLevel();</pre></code>
Raising 2 to the "power" of LosMipLevel will give the relation of the size of LosMap to the HeightMap.<br>
Ex:<br>
# LosMipLevel=0 | 2^0 = '''1''' | Size of the LosMap = size of HeightMap * 1/'''1'''
# LosMipLevel=1 | 2^1 = '''2''' | Size of the LosMap = size of HeightMap * 1/'''2'''
# LosMipLevel=2 | 2^2 = '''4''' | Size of the LosMap = size of HeightMap * 1/'''4'''

http://springrts.com/phpbb/viewtopic.php?f=15&t=32674

[[Category: AI Dev]]

AI:Development:TheMaps - Revision history

Qrow: 1 revision imported

interaidev>Paulomorfeo at 21:59, 22 October 2014