Map structure - Revision history

Nelson: some more tips for identifying tiles in game

2026-02-13T18:15:39Z

some more tips for identifying tiles in game

← Older revision		Revision as of 18:15, 13 February 2026
Line 52:		Line 52:
	** 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.		** 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 {{Keybinding\|F5}} is used to enable debug display. Configuring debug mode in this way allows {{Keybinding\|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.		** If '''debug''' is chosen the grid will become visible whenever {{Keybinding\|F5}} is used to enable debug display. Configuring debug mode in this way allows {{Keybinding\|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.
			* To see the tile types as simple squares instead of smoothly rendered contours, enable the debug setting '''show-raw-tile-transitions'''
			* Alt-clicking a tile in the terrain will bring up the Factoriopedia entry with the tile's name.
	{{C\|Main}}		{{C\|Main}}

Cardinal: /* Tile */ Link to tile page.

2025-11-17T02:44:35Z

Tile: Link to tile page.

← Older revision		Revision as of 02:44, 17 November 2025
Line 3:		Line 3:

	== Tile ==		== Tile ==
			''This section is about the area and distance unit. For placeable tiles, see [[tile]].''

	[[File:MapStructure-GridExample.png\|thumb\|right\|400px\|The tile grid shown in-game; chunks (32×32 tiles) are indicated by the thicker black lines. Click to see at higher resolution.]]		[[File:MapStructure-GridExample.png\|thumb\|right\|400px\|The tile grid shown in-game; chunks (32×32 tiles) are indicated by the thicker black lines. Click to see at higher resolution.]]

Quchen: /* Chunk */ Clarification: not a 20×20 square around the player is generated, it’s 20 tiles in each direction (effectively a 41×41 square)

2025-10-28T08:39:43Z

Chunk: Clarification: not a 20×20 square around the player is generated, it’s 20 tiles in each direction (effectively a 41×41 square)

← Older revision		Revision as of 08:39, 28 October 2025
Line 32:		Line 32:

	Several mechanics work on a chunk-by-chunk basis:		Several mechanics work on a chunk-by-chunk basis:
	* The map is generated chunk-by-chunk during play. ~~A 20x20 chunk area~~ around each player is slowly generated over time, or immediately if revealed directly and not yet generated.		* The map is generated chunk-by-chunk during play. 20 chunks distance in each direction around each player is slowly generated over time, or immediately if revealed directly and not yet generated.
	* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.		* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.
	* [[Pollution]] and [[Spores\|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)		* [[Pollution]] and [[Spores\|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)

HeliGungir: /* Chunk */

2025-08-30T03:48:03Z

Chunk

← Older revision		Revision as of 03:48, 30 August 2025
Line 32:		Line 32:

	Several mechanics work on a chunk-by-chunk basis:		Several mechanics work on a chunk-by-chunk basis:
	* The map is generated chunk-by-chunk during play. A 20x20 chunk area around each player is slowly generated over time, or immediately if revealed and not yet generated.		* The map is generated chunk-by-chunk during play. A 20x20 chunk area around each player is slowly generated over time, or immediately if revealed directly and not yet generated.
	* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.		* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.
	* [[Pollution]] and [[Spores\|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)		* [[Pollution]] and [[Spores\|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)

HeliGungir: /* Chunk */ Removed misleading "second definition" of the term chunk

2025-08-30T03:43:03Z

Chunk: Removed misleading "second definition" of the term chunk

← Older revision		Revision as of 03:43, 30 August 2025
Line 27:		Line 27:
	== Chunk ==		== Chunk ==

	[[File:radar_revealing_sectors.gif\|thumb\|220px\|Animation of radars revealing chunks.]]~~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.~~		[[File:radar_revealing_sectors.gif\|thumb\|220px\|Animation of radars revealing chunks.]]

	~~Chunks are used for~~:		The map is divided into a grid of '''chunks''', each 32x32 tiles (1024 tiles total).

			Several mechanics work on a chunk-by-chunk basis:
	* The map is generated chunk-by-chunk during play. A 20x20 chunk area around each player is slowly generated over time, or immediately if revealed and not yet generated.		* The map is generated chunk-by-chunk during play. A 20x20 chunk area around each player is slowly generated over time, or immediately if revealed and not yet generated.
	* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.		* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.

HeliGungir: /* Chunk */ SA stuff, pathfinding, more reworking

2025-08-30T03:28:04Z

Chunk: SA stuff, pathfinding, more reworking

← Older revision		Revision as of 03:28, 30 August 2025
Line 30:		Line 30:

	Chunks are used for:		Chunks are used for:
	* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] provide ~~visibility in~~ [[remote view]] on a chunk basis.		* The map is generated chunk-by-chunk during play. A 20x20 chunk area around each player is slowly generated over time, or immediately if revealed and not yet generated.
	* ~~The map is generated~~ on a chunk basis. ~~A 20x20 chunk area around each player is slowly generated over time, and~~ chunks ~~are generated immediately when revealed by radars, spidertrons, etc~~.		* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] reveal chunks and provide [[Radar#Coverage\|live coverage]] in remote view on a chunk basis.
	* ~~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~~ [[~~Time#Ticks\|tick~~]].		* [[Pollution]] and [[Spores\|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)
	* ~~The~~ [~~[pollution]~~] ~~model~~ is ~~based on chunks,~~ and ~~pollution spreads to neighboring chunks~~.		* [[Enemies#Expansions\|Enemy expansion]] is calculated on a chunk basis.
	* ~~[[Enemies#Expansions\|Enemy expansion]]~~ is ~~evaluated on a per-chunk basis~~.		* [[Demolisher]]{{SA}} territories are chunk-aligned.
			* Enemy pathfinding works in multiple stages, and the first stage is chunk-based. [https://factorio.com/blog/post/fff-317] An unintended result is enemies tend to walk along chunk borders. Also biters and spitters will sometimes attack obstacles at chunk borders that they would normally navigate around.
			* To reduce computation, entire chunks are set inactive when nothing important is happening in them. E.g.: Chunks with only fish or idling enemies may be set inactive, halting their idle movement.

	== Visualizing tiles and chunks in-game ==		== Visualizing tiles and chunks in-game ==

HeliGungir: /* Chunk */

2025-08-30T01:51:31Z

Chunk

← Older revision		Revision as of 01:51, 30 August 2025
Line 30:		Line 30:

	Chunks are used for:		Chunks are used for:
	* ~~Visibility in Remote View.~~ [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] provide visibility on a ~~chunk-by-~~chunk basis.		* [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] provide visibility in [[remote view]] on a chunk basis.
	* ~~Map generation.~~ The map is ~~slowly~~ generated ~~over time in~~ a 20x20 chunk area around ~~the~~ player, or immediately when ~~chunks are~~ revealed by ~~the player~~, ~~radars~~, etc.		* The map is generated on a chunk basis. A 20x20 chunk area around each player is slowly generated over time, and chunks are generated immediately when revealed by radars, spidertrons, etc.
	* 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 [[Time#Ticks\|tick]].		* 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 [[Time#Ticks\|tick]].
	* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.		* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.

HeliGungir: /* Chunk */ Split map generation and map revealing into separate bullet points

2025-08-30T01:07:06Z

Chunk: Split map generation and map revealing into separate bullet points

← Older revision		Revision as of 01:07, 30 August 2025
Line 30:		Line 30:

	Chunks are used for:		Chunks are used for:
	* ~~Map generation~~. ~~When the~~ [[~~player~~]] ~~moves~~, ~~has a~~ [[~~radar~~]] ~~explore the map via sectors~~, ~~or has~~ [[artillery ~~shell~~]]~~s fired across long distances, the~~ map is ~~revealed~~ in chunks.		* Visibility in Remote View. [[Player\|Players]], [[Radar\|radars]], [[Roboport\|roboports]], [[Spidertron\|spidertrons]], and fired [[Artillery\|artillery shells]] provide visibility on a chunk-by-chunk basis.
			* Map generation. The map is slowly generated over time in a 20x20 chunk area around the player, or immediately when chunks are revealed by the player, radars, etc.
	* 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 [[Time#Ticks\|tick]].		* 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 [[Time#Ticks\|tick]].
	* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.		* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.

HeliGungir: /* Chunk */ Moved detailed info about enemy expansions to Enemies#Expansions

2025-08-30T00:46:25Z

Chunk: Moved detailed info about enemy expansions to Enemies#Expansions

← Older revision		Revision as of 00:46, 30 August 2025
Line 33:		Line 33:
	* 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 [[Time#Ticks\|tick]].		* 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 [[Time#Ticks\|tick]].
	* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.		* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
	* [[Enemies#Expansions\|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.		* [[Enemies#Expansions\|Enemy expansion]] is evaluated on a per-chunk basis.

	== Visualizing tiles and chunks in-game ==		== Visualizing tiles and chunks in-game ==

Bilka: /* Visualizing tiles and chunks in-game */ fixed use of keybind template

2024-06-10T13:04:40Z

Visualizing tiles and chunks in-game: fixed use of keybind template

← Older revision		Revision as of 13:04, 10 June 2024
Line 39:		Line 39:
	A tile grid overlay is available which shows the grid upon which the map is built:		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 {{Keybinding\|~~Shift-Space~~}}).		* The grid can be shown whenever the player pauses the game (by default with {{Keybinding\|shift\|space}}).
	** This is configured under Settings->Interface->'''Show grid when game is paused'''.		** This is configured under Settings->Interface->'''Show grid when game is paused'''.
	* To see the grid while the game is still running, [[Debug mode\|debug settings]] can be used:		* To see the grid while the game is still running, [[Debug mode\|debug settings]] can be used: