Map structure describes the division of the game world into standard units: tiles and chunks. Tiles are the building blocks of the game, upon which all distance and area measurements are based. Chunks are blocks of 32×32 tiles used for various area-based calculations.
A tile is a square which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The tile is the basis for all area and distance measurement. Entity sizes are defined in terms of tiles; for example the rocket silo - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9×9. The smallest possible entity size is therefore one tile, 1×1. Examples of 1×1 entities include transport belts and chests.
The maximum size of the map is a square 2 million tiles on each side, a total of 4 trillion tiles. In practice the map in an average game is likely to be in the range of hundreds of thousands of tiles up to a few million at most.
Tile grid alignment
Almost all placeable entities are aligned to the tile grid when placed in the game. Exceptions include the land mine and vehicles such as the car, tank, locomotive and wagons. Non-placeable entities that do not align to the grid include enemies, trees and decoratives.
- Area covered by Radar: about 200 tiles diameter (100 tiles in each direction, bounded to the matching chunk).
- It takes about 1 minutes and 52 seconds for a player to run 1000 tiles without being given a speed boost (such as via an exoskeleton).
Real world size analogy
One tile is generally assumed to be one square meter in size. This measurement is proven to be technically true, and can be verified in-game. A test conducted via car will reveal that covering 250 tiles at 208.0 km/h (57.777 m/s) will take 260 game ticks (4.333 s). Using this data, it can be proven that
57.777 m/s ÷ (250 tiles / 4.333 s) ≈ 1 m/tile.
A chunk is a unit defined as either an area of the map 32×32 tiles in size (containing 1024 tiles in total) or a distance of 32 tiles.
Chunks are used for:
- Map generation. When the player moves, has a radar explore the map via sectors, or has artillery shells fired across long distances, the map is revealed in chunks.
- Chunks are "switched off" to save CPU cycles. If nothing important happens in a chunk (e.g. nothing has moved except fish) the chunk is not computed in the next tick.
- The pollution model is based on chunks, and pollution spreads to neighboring chunks.
- Enemy expansion is evaluated on a per-chunk basis. The game scans the map chunk by chunk to decide whether each chunk is a valid expansion target. Valid chunks are called 'candidate chunks' and assigned a score from 0 to 1.0 indicating their relative suitability. A chunk is then picked at random using a weighted dice roll such that chunks with higher scores are chosen more frequently.
Visualizing tiles and chunks in-game
A tile grid overlay is available which shows the grid upon which the map is built:
- The grid can be shown whenever the player pauses the game (by default with Shift-Space).
- This is configured under Settings->Interface->Show grid when game is paused.
- To see the grid while the game is still running, debug settings can be used:
- Pressing F4 will show the Debug settings window.
- Ticking show-tile-grid under always will show the grid at all times; ticking it under debug will show it only when debug mode is activated.
- If debug is chosen the grid will become visible whenever F5 is used to enable debug display. Configuring debug mode in this way allows F5 to be used as a convenient toggle for turning the grid on and off, which can be useful when attempting to place entities according to a neat and/or symmetrical design.