Official Factorio Wiki - User contributions [en]

Artillery targeting remote

2019-04-04T11:19:15Z

TheBloke: Clarify that it's targets that expire, not the remote itself and that only one remote is needed per game. Also mention that the remote shows the number of targets on the quickbar as well.

{{Languages}}{{:Infobox:Artillery targeting remote}}
The '''Artillery targeting remote''' is used to manually designate targets for the [[artillery wagon]] and [[artillery turret]] by clicking somewhere with them - either from the map or normally from the world. Targets expire when an artillery wagon or turret shoots the spot they designate, or after 1 minute has elapsed. Placing targets with an artillery targeting remote does not use the item up - usually only one remote needs to be crafted per game. Using this item massively increases the range of artillery compared to having artillery fire automatically.

The number next to the remote when it is held in hand or pinned to the quickbar indicates how many artillery wagons or turrets are in range and contain ammunition. The remote has no effect if a designated location is outside of the range of all artillery.

== Gallery ==
<gallery widths=190px heights=190px>
File:artillery remote on map.png|Orange designated fire locations on the map.
</gallery>
== History ==

{{history|0.16.0|
* Introduced}}

== See also ==

* [https://www.factorio.com/blog/post/fff-220 Friday Facts #220 - The best Friday Facts ever]

{{CombatNav}}
{{C|Capsules}}

Deconstruction planner

2019-03-29T17:13:30Z

TheBloke: Remove text examples. Slightly expand label under one screenshot example. /* Configuration and filtering */

{{Languages}}
{{:Infobox:Deconstruction planner}}
The '''deconstruction planner''' is an item which allows the player to mark [[tile]]s and entities, including [[tree]]s, [[rock]]s, [[cliff]]s, [[fish]] and items on the ground, for removal. By default, tiles are only marked when no entities are found. Tiles or entities queued for deconstruction will be marked with a red 'X'. When within the range of [[construction robot]]s they will be removed by the robots and the resulting items stored in [[logistic network]] chests or, when a [[personal roboport]] is used, the player's inventory. [[Ghost]]s will be removed immediately. Anything marked for deconstruction will immediately stop functioning. Deconstruction orders can be cancelled prior to the removal of the target. The deconstruction planner can be used unfiltered (blank) to remove all entities or tiles within its selection area, or it can be filtered to specific targets.

== Usage ==

=== Getting a deconstruction planner ===

A planner can be obtained by:
* Clicking the red deconstruction planner icon ( [[File:DeconstructionPlanner-ShortcutIcon.png|25px]] ) in the [[shortcut bar]]. (Available once [[Construction robotics (research)|construction robotics]] is researched in at least one game.)
* Pressing the keyboard shortcut assigned to '''Make new deconstruction planner'''; default: {{Keybinding|ALT + D}}.
* Opening the blueprint library and selecting '''New deconstruction planner'''.
* [[#Exporting_and_importing_with_strings|Importing a deconstruction planner string]].

Once a new planner is in the hand it can be used immediately and then deleted by pressing {{Keybinding|Q}} to clear the hand. Alternatively, it can be dropped into the player's inventory for later use. Once in the inventory it can be pinned to a [[quickbar]] slot.

=== Accessing settings ===

The planner must be in an inventory in order for its configuration to be changed. Settings can be accessed by clicking {{Keybinding|rmb}} on a planner's icon, either in the inventory or on a quickbar link.

A full description of available settings and filters can be found under [[#Configuration and filtering|configuration and filtering]].

=== Deleting a planner ===

A planner that has been stored in an inventory can be deleted by clicking the red trash-can icon labelled '''Destroy deconstruction planner''' ( [[File:TrashCan.png|25px]] ) in the top right of its settings window.

Care should be taken when the planner has been configured as this operation is performed immediately without confirmation and cannot be undone.

=== Using the deconstruction planner ===

With a planner held in the hand the player can click-drag it ({{Keybinding|lmb}} is held down while moving the mouse) over existing structures and ghosts to mark them for deconstruction. A tooltip appears indicating what will be removed.

The planner can be used anywhere on the map where the player has [[radar]] coverage (map view).

Once {{Keybinding|lmb}} is released the deconstruction planner will take effect according to the rules listed below.

<gallery widths=400px heights=300px>
File:DeconstructionPlanner-DraggingAPlanner.png|Dragging a deconstruction planner.
File:DeconstructionPlanner-DraggingAPlannerTooltip.png|The tooltip shows what will be removed.
File:DeconstructionPlanner-DraggingAPlannerMarkers.png|Red Xs indicate queued deconstruction orders. Ghosts were immediately removed.
</gallery>

=== Effects of deconstruction ===

The following describes the possible results of using a deconstruction planner in the game world:
* Any selected entity ghosts and tile ghosts will be immediately removed.
* Any selected entities and tiles will be queued for deconstruction, indicated with a red X.
* Anything queued for deconstruction will stop functioning; for example [[transport belts]] will stop moving, [[assembling machine]]s will cease producing items, [[wall]]s stop connecting to each other, and so on. Laser and gun turrets will continue functioning even when marked for deconstruction.
* If the deconstruction orders are within the construction area of construction robots the orders will be added to the bots' queue and will be removed in due course:
** Bots will fly in and remove all entities and tiles and place the resulting items in logistic network chests, or the player's inventory when the bots flew from a personal roboport.
** Where there are items to be removed - for example being carried by transport belts or stored inside a chest or assembling machine - these will also be picked up by bots and placed in the appropriate storage.
*** Items must be removed before the entities that carry or hold them. For example if a [[wooden chest]] holding 500 [[iron plate]]s is marked for removal, the plates will be picked up first and only when all have been removed will the bots deconstruct the chest itself.
** Environmental entities such as trees, rocks and fish are handled in the same way, except bots mine them and collect and store the resource items they leave behind.
*** Cliffs are a special case: they are destroyed by bots carrying [[cliff explosives]] and do not yield any item to be stored.

=== Cancelling deconstruction orders ===

Queued deconstruction orders can be cancelled by holding {{Keybinding|Shift}} while click-dragging a deconstruction planner over the affected area.

When {{Keybinding|Shift}} is held down the area selection border will change from red to blue to indicate cancellation mode is in effect.

=== Undo ===

The undo tool can be used to revert the actions of a deconstruction planner. This applies both to pending deconstruction orders and completed removals.

Undo is triggered by pressing {{Keybinding|Control + Z}} (on macOS: {{Keybinding|Command + Z}})

Performing an undo will cancel any queued removal orders (red Xs) that have not yet been actioned. Any ghosts that were removed will be immediately replaced. Where built entities and tiles have already been removed the undo will reinstate them in the form of new ghosts that can then be re-built by any construction robots in range.

Items that were removed as part of the deconstruction - for example the inventory of chests or items carried by a transport belt - will not be restored by an undo. This means that a deconstruction that consisted exclusively of items, for example picking up [[stone]] from the ground, cannot be undone.

It is also not possible to undo the removal of trees, rocks, cliffs and fish.

<gallery widths=400px heights=230px>
File:DeconstructionPlanner-CancelDemo.gif|Cancelling deconstruction orders by dragging with {{keybinding|Shift}} held down. The entities start working when the deconstruction is cancelled.
File:DeconstructionPlanner-UndoDemo.gif|Using then undoing a deconstruction planner. Deconstruction markers are cancelled, ghosts re-appear, and removed entities are reinstated as new ghosts for bot rebuilding.
</gallery>

== Valid targets ==
[[File:DeconstructionPlanner-Fish.png|thumb|right|300px|Harvesting fish with a deconstruction planner.]]
The deconstruction planner can remove player-built entities, [[Ghost#Entities|entity ghosts]], tiles, [[Ghost#Tiles|tile ghosts]] and loose items. In addition, it can remove [[tree]]s, [[rock]]s, [[cliff]]s and [[fish]].

=== Tiles ===

[[Tile]]s are treated differently to entities, entity ghosts and tile ghosts. By default a deconstruction planner will not select any tiles unless the area selected contains ''only'' tiles; whenever one or more entities, entity ghosts or tile ghosts is included, tile selection is disabled. This is done to allow the player to use a deconstruction planner to remove entities that are placed on top of path tiles (such as [[concrete]]) without the floor always being removed as well.

When the user wishes to select tiles in areas where other objects also exist the deconstruction planner configuration must be changed as described in the next section.

=== Environmental entities ===

These are handled in the same way as entities and tiles placed by the player: they are marked with a red X and construction robots will remove them. A difference with environmental entities is that bots will collect resources rather than the entity itself, such as [[wood]] from trees and stone from rocks.

The removal of cliffs requires that the bots have access to cliff explosives. Cliffs do not leave behind any resource.

The ability to use a deconstruction planner to remove and collect fish provides a convenient way for a player equipped with a [[personal roboport]] to replenish their stocks of healing items even in the middle of combat. Fish marked with a deconstruction planner will stop moving.

== Configuration and filtering ==
[[File:DeconstructionPlanner-IconFiltered.png|thumb|right|An example of a filtered planner icon.]]
A new deconstruction planner is blank, meaning it removes according to a pre-defined set of rules. The planner can optionally be edited to provide a custom list of removal rules which control which types of entities and tiles will - or won't - be removed. These rules are called filters.

A filtered planner will show its filtered items on its icon. Up to the first four filters will be shown.

=== Blank planner rules ===

A blank planner will select:
* Any entities and entity ghosts, including trees, rocks, cliffs and fish;
* Tile ghosts;
* '''''Or''''', if and only if no entities, entity ghosts and tile ghosts are found, it will instead select tiles.

These rules are the base point from which a filtered planner can then be customized.

=== Filter settings window ===

The deconstruction planner interface is divided into two sections: '''entities''' and '''tiles'''.

<gallery widths=280px heights=150px>
File:DeconstructionPlanner-BlankEntities.png|The entities tab.
File:DeconstructionPlanner-BlankTiles.png|The tiles tab.
</gallery>

[[File:DeconstructionPlanner-ExampleWhitelistDefences.png|thumb|right|200px|A whitelist filter that removes only defensive structures.]]
[[File:DeconstructionPlanner-ExampleBlacklistPowerandRoboports.png|thumb|right|200px|A blacklist filter that removes everything except [[roboport]]s and [[Electric_system#Distribution|power poles]].]]

=== Principles of filtering ===

Each tab consists of 30 slots in which an entity or tile can be chosen. When one or more slots is filled the planner becomes filtered and will now act according to those filters.

A set of filters is either a whitelist or blacklist, and this is set with a toggle at the top of each tab. The default is whitelist. In whitelist mode the planner will act only upon those items added to the filter slots - any entities and tiles not added as filters will be ignored by the planner.

In blacklist mode the opposite applies: the planner will mark everything ''except'' the entities or tiles filtered on.

=== Setting and removing filters ===

Clicking any slot with {{keybinding|lmb}} will open the '''Set the filter''' window in which the desired item can be chosen. Alternatively, an item in the hand can be clicked into a slot to filter on that item.

A filter is removed by clicking on a filled slot with {{keybinding|rmb}}.

=== Entities tab ===

In the entities tab the user can select items to filter from the follow categories:
* Environment
* Logistics
* Production
* Combat
* Unsorted
[[File:DeconstructionPlanner-SetFilterEnvironment.png|thumb|right|200px|The Environment tab lists all types of trees and rocks, plus cliffs and fish.]]
Logistics, production and combat will be familiar to the player from the [[items|item selection]] window. Environment and unsorted are unique to the deconstruction planner.

The environment tab lists cliffs, fish, and every individual kind of tree and rock. This facilitates filtering on specific environmental entities if desired.

==== Trees/rocks only toggle ====

At the top of the entities tab is the '''Trees/rocks only''' tick-box. With this enabled the deconstruction planner will filter on all items listed in the Environment section, and the filter slots will be disabled. The Whitelist/Blacklist toggle is still in effect and controls whether the planner selects only environmental entities, or selects everything but them.

==== Special items in the Unsorted section ====

The unsorted section provides four special items, each using a red X icon.
* Entity ghost: To filter on any type of entity ghost, separate from constructed entities.
* Item on ground: Loose items on the ground, such as dropped by the player, spilled from removing [[armor]], and stones dropped from destroyed [[rock]]s. Does not include items on [[transport belts]].
* Item request slot: Filters on the pending addition of items such as [[module]]s to [[assembling machine 2]] or [[electric furnace]]. This would also target [[fuel]] queued for addition to a [[locomotive]]. Does not target items already installed, only those waiting to be added following the placement of a blueprint or as a result of an undo operation.
* Tile ghost: As with entity ghost, this will target [[tile]] ghosts separately from constructed tiles. If the user wants a deconstruction planner that only removes tile ghosts, they can place this item as an entity filter. If they want a filter that removes all types of tiles and tile ghosts, they should add '''Tile ghost''' under Entities and then set the Tiles tab drop-down to 'Always'.

=== Tiles tab ===

Clicking a filter slot will bring up the '''Set the Filter''' window showing the available tiles. [[Landfill]] is included in the list but has no function as landfill cannot be removed once placed.

At the top of the Tiles tab is a drop-down that controls constructed tile removal behavior. It has four options:
* Normal: The default. Constructed tiles are removed only when no entities, entity ghosts or tiles ghosts are found in the deconstruction area.
* Always: Constructed tiles are always removed, even if the deconstruction planner also selects entities or entity ghosts. Tile ghosts are not selected unless '''Tile ghost''' is added under the Entities tab.
* Never: Constructed tiles are never removed, even if they are the only object selected. Tile ghosts are not selected unless '''Tile ghost''' is added in the Entities tab.
* Only: Constructed tiles are always removed, and nothing else will be. Entities, entity ghosts and tile ghosts will be ignored. The Entities tab is effectively disabled when this mode is selected.

The deconstruction planner always follows the settings of this drop-down, regardless of any filters set in the Tiles tab. For example if a user wishes to configure a planner that removes both walls and [[concrete]], they must first set those filters in the Entities and Tiles tabs, and then also set the Tiles drop-down to '''Always'''. Without changing the drop-down the planner would only select concrete in places where no entities, entity ghosts or tile ghosts were found, as per the rules described under Normal in the above list.

=== Clearing all filters and configuration ===

All configuration can be removed from a planner by holding {{Keybinding|Shift}} while clicking on its icon with {{Keybinding|rmb}}. This returns it to the blank, unfiltered state.

=== Exporting and importing with strings ===

The settings for a deconstruction planner can be exported in string form.

Clicking the '''Export to string''' button ( [[File:ExportToString.png|25px]] ) in the top right of the planner edit window will pop up a window containing the '''Deconstruction item string'''. This string can be copied to the operating system clipboard, from where it could be saved to a text file or uploaded to a website.

To import a deconstruction planner the player can click the '''Import String''' icon on the [[shortcut bar]] ( [[File:ImportString.png|25px]] ) or choose the same option from the blueprint library. A dialogue box will appear into which the string can be pasted. This will result in a deconstruction planner appearing on the hand with the same configuration as the one that was exported.

The export/import process can be used to copy deconstruction planners between games and to other players.

== Achievements ==
{{Achievement|automated-cleanup}}

== History ==

{{history|0.17.0|
* Added cliffs as a valid deconstruction target.}}

{{history|0.15.0|
* Blueprint library: Allows for keeping players blueprints between individual game saves and allows sharing blueprints in multiplayer games.
* Added ability to export and import blueprints, blueprint books, and deconstruction planners as strings.
* Blueprints, blueprint books and deconstruction planners are obtainable from the library GUI with no crafting cost.}}

{{history|0.13.0|
* Several non-stackable items can be swapped directly with counterparts, this includes the deconstruction planner.}}

{{history|0.11.15|
* When using the deconstruction planner, the [[logistic network]] is not drawn if the mouse is over a GUI element.}}

{{history|0.11.0|
* Added a cancel deconstruction option to the deconstruction planner.}}

{{history|0.9.0|
* Introduced}}

== See also ==
* [[Blueprint]]
* [[Upgrade planner]]
* [[Roboport]]
* [[Construction robot]]

{{ProductionNav}}
{{C|Tools}}

Ghost

2019-03-28T13:38:42Z

TheBloke: Para break for train stuff /* Entities */

{{Languages}}
[[File:medium_electric_pole_ghost.png|thumb|180px|Ghosts of [[Medium electric pole]]s at the top row, with normally placed ones below.]]
A '''ghost''' is a semi-transparent marker for an entity or [[tile]] which can be placed as a planning tool for future manual building or for [[construction robot]]s to place using the supplies of a [[logistic network]]. A ghost does not perform any of the functions of the object it represents, but exists to mark the spot where the item should later be built or, in the case where an entity was destroyed, the place where it stood. A ghost can store configuration information such as the recipe used by an [[assembling machine]]; this configuration will become active when the real entity is placed on top of the ghost.

== Valid ghosts ==

=== Entities ===

The majority of entities placeable by the player can be ghosts. Exceptions include mobile entities such as the [[car]], [[tank]] and [[robot]]s.

[[Locomotive]]s, [[cargo wagon]]s, [[fluid wagon]]s and [[artillery wagon]]s are valid ghosts but must be placed on a [[rail]].

=== Tiles ===

Any tile that can be placed by the player is valid as a ghost.

== Usage ==
[[File:cursor_ghost.png|frame|right|The cursor as it appears prior to placing an entity ghost.]]
=== Placing single ghosts ===

Single ghosts are placed in the same way as normal entities and tiles: by clicking with {{keybinding|lmb}} on the map.

In order to place a ghost, the player must first have one in their hand:

==== Holding shift while holding an entity or tile ====

If {{keybinding|Shift}} is held with an entity or tile in the hand, the ghost symbol appears. Click {{keybinding|lmb}} will now place a ghost instead of the object itself.

==== Enabling '''Pick ghost item if no items are available''' ====

Under Settings->Interface is the option '''Pick ghost item if no items are available'''. If this is enabled a ghost item will be provided to the player whenever they select an entity or tile which is not available in their inventory. This affects both the pipette tool ({{keybinding|Q}}) and selecting an item from the [[quickbar]].

=== Blueprints ===

Placing a [[blueprint]] will place ghosts for all the entities and tiles contained within the blueprint.

=== Rail planner ===

When placing [[rail]]s the [[rail planner]] is a convenient way to place a large number of rails, and is required for placing curved rails. The rail planner will place ghosts when {{keybinding|Shift}} is held at the same time as clicking a rail planner arrow. In ghost mode the rail planner can be used to place ghost rails of any length.

=== Destroyed entities ===

Once [[Construction robotics (research)|construction robotics]] has been researched any entities that are destroyed (for example by [[enemies]]) will leave behind a ghost. This allows these buildings to be automatically re-built if construction bots are available in the area.

== Interaction with construction robots ==

Construction robots will place the real version of an entity or tile ghost if either of the following conditions are met:
* The materials required to build the object are available in the [[logistic network]], and enough construction robots are free to begin the placing.
* The materials required to build the object are available from the player's inventory, the player is equipped with one or more [[personal roboport]]s, and is carrying one or more [[construction robot]]s.

== Lifetime of ghosts ==

Ghosts that are placed by the player will last forever. Ghosts for destroyed entities will last a week of [[Time|game time]]. Their remaining time is indicated by the purple bar below the ghost.

== Gallery ==
<gallery widths=200px>
File:automated_construction_concrete.gif|Construction robots paving a [[Refined concrete]] path. ''(Click to see GIF animation)''
File:railway_three_ghost.png|The top and middle part of a 3-way railway in "ghost mode".
</gallery>

== History ==

{{History|0.17.0|
* Trains and wagons can now be blueprinted and therefore can be ghost entities.
* Added the setting '''Pick ghost item if no items are available'''.}}

{{History|0.16.0|
* When building a different entity on top of a ghost, settings from the ghost will be copied if possible.
* Blueprint previews and ghost entities now have their walls, pipes and belts connected.}}

{{History|0.15.0|
* Manual ghost building will mark trees/rocks for deconstruction.}}

== See also ==
* [[Blueprint]]
* [[Deconstruction planner]]
* [[Upgrade planner]]
* [[Blueprint book]]
* [[Logistic network]]
* [[Roboport]]
* [[Personal roboport]]
* [[Construction robot]]

Ghost

2019-03-28T13:38:09Z

TheBloke: Typo /* Valid ghosts */

{{Languages}}
[[File:medium_electric_pole_ghost.png|thumb|180px|Ghosts of [[Medium electric pole]]s at the top row, with normally placed ones below.]]
A '''ghost''' is a semi-transparent marker for an entity or [[tile]] which can be placed as a planning tool for future manual building or for [[construction robot]]s to place using the supplies of a [[logistic network]]. A ghost does not perform any of the functions of the object it represents, but exists to mark the spot where the item should later be built or, in the case where an entity was destroyed, the place where it stood. A ghost can store configuration information such as the recipe used by an [[assembling machine]]; this configuration will become active when the real entity is placed on top of the ghost.

== Valid ghosts ==

=== Entities ===

The majority of entities placeable by the player can be ghosts. Exceptions include mobile entities such as the [[car]], [[tank]] and [[robot]]s. [[Locomotive]]s, [[cargo wagon]]s, [[fluid wagon]]s and [[artillery wagon]]s are valid ghosts but must be placed on a [[rail]].

=== Tiles ===

Any tile that can be placed by the player is valid as a ghost.

== Usage ==
[[File:cursor_ghost.png|frame|right|The cursor as it appears prior to placing an entity ghost.]]
=== Placing single ghosts ===

Single ghosts are placed in the same way as normal entities and tiles: by clicking with {{keybinding|lmb}} on the map.

In order to place a ghost, the player must first have one in their hand:

==== Holding shift while holding an entity or tile ====

If {{keybinding|Shift}} is held with an entity or tile in the hand, the ghost symbol appears. Click {{keybinding|lmb}} will now place a ghost instead of the object itself.

==== Enabling '''Pick ghost item if no items are available''' ====

Under Settings->Interface is the option '''Pick ghost item if no items are available'''. If this is enabled a ghost item will be provided to the player whenever they select an entity or tile which is not available in their inventory. This affects both the pipette tool ({{keybinding|Q}}) and selecting an item from the [[quickbar]].

=== Blueprints ===

Placing a [[blueprint]] will place ghosts for all the entities and tiles contained within the blueprint.

=== Rail planner ===

When placing [[rail]]s the [[rail planner]] is a convenient way to place a large number of rails, and is required for placing curved rails. The rail planner will place ghosts when {{keybinding|Shift}} is held at the same time as clicking a rail planner arrow. In ghost mode the rail planner can be used to place ghost rails of any length.

=== Destroyed entities ===

Once [[Construction robotics (research)|construction robotics]] has been researched any entities that are destroyed (for example by [[enemies]]) will leave behind a ghost. This allows these buildings to be automatically re-built if construction bots are available in the area.

== Interaction with construction robots ==

Construction robots will place the real version of an entity or tile ghost if either of the following conditions are met:
* The materials required to build the object are available in the [[logistic network]], and enough construction robots are free to begin the placing.
* The materials required to build the object are available from the player's inventory, the player is equipped with one or more [[personal roboport]]s, and is carrying one or more [[construction robot]]s.

== Lifetime of ghosts ==

Ghosts that are placed by the player will last forever. Ghosts for destroyed entities will last a week of [[Time|game time]]. Their remaining time is indicated by the purple bar below the ghost.

== Gallery ==
<gallery widths=200px>
File:automated_construction_concrete.gif|Construction robots paving a [[Refined concrete]] path. ''(Click to see GIF animation)''
File:railway_three_ghost.png|The top and middle part of a 3-way railway in "ghost mode".
</gallery>

== History ==

{{History|0.17.0|
* Trains and wagons can now be blueprinted and therefore can be ghost entities.
* Added the setting '''Pick ghost item if no items are available'''.}}

{{History|0.16.0|
* When building a different entity on top of a ghost, settings from the ghost will be copied if possible.
* Blueprint previews and ghost entities now have their walls, pipes and belts connected.}}

{{History|0.15.0|
* Manual ghost building will mark trees/rocks for deconstruction.}}

== See also ==
* [[Blueprint]]
* [[Deconstruction planner]]
* [[Upgrade planner]]
* [[Blueprint book]]
* [[Logistic network]]
* [[Roboport]]
* [[Personal roboport]]
* [[Construction robot]]

Ghost

2019-03-28T13:37:57Z

TheBloke: Add links for train entities /* Valid ghosts */

{{Languages}}
[[File:medium_electric_pole_ghost.png|thumb|180px|Ghosts of [[Medium electric pole]]s at the top row, with normally placed ones below.]]
A '''ghost''' is a semi-transparent marker for an entity or [[tile]] which can be placed as a planning tool for future manual building or for [[construction robot]]s to place using the supplies of a [[logistic network]]. A ghost does not perform any of the functions of the object it represents, but exists to mark the spot where the item should later be built or, in the case where an entity was destroyed, the place where it stood. A ghost can store configuration information such as the recipe used by an [[assembling machine]]; this configuration will become active when the real entity is placed on top of the ghost.

== Valid ghosts ==

=== Entities ===

The majority of entities placeable by the player can be ghosts. Exceptions include mobile entities such as the [[car]], [[tank]] and [[robot]]s. [[Locomotive]]s, [[cargo wagon]]s, [[fluid wagons]]s and [[artillery wagon]]s are valid ghosts but must be placed on a [[rail]].

=== Tiles ===

Any tile that can be placed by the player is valid as a ghost.

== Usage ==
[[File:cursor_ghost.png|frame|right|The cursor as it appears prior to placing an entity ghost.]]
=== Placing single ghosts ===

Single ghosts are placed in the same way as normal entities and tiles: by clicking with {{keybinding|lmb}} on the map.

In order to place a ghost, the player must first have one in their hand:

==== Holding shift while holding an entity or tile ====

If {{keybinding|Shift}} is held with an entity or tile in the hand, the ghost symbol appears. Click {{keybinding|lmb}} will now place a ghost instead of the object itself.

==== Enabling '''Pick ghost item if no items are available''' ====

Under Settings->Interface is the option '''Pick ghost item if no items are available'''. If this is enabled a ghost item will be provided to the player whenever they select an entity or tile which is not available in their inventory. This affects both the pipette tool ({{keybinding|Q}}) and selecting an item from the [[quickbar]].

=== Blueprints ===

Placing a [[blueprint]] will place ghosts for all the entities and tiles contained within the blueprint.

=== Rail planner ===

When placing [[rail]]s the [[rail planner]] is a convenient way to place a large number of rails, and is required for placing curved rails. The rail planner will place ghosts when {{keybinding|Shift}} is held at the same time as clicking a rail planner arrow. In ghost mode the rail planner can be used to place ghost rails of any length.

=== Destroyed entities ===

Once [[Construction robotics (research)|construction robotics]] has been researched any entities that are destroyed (for example by [[enemies]]) will leave behind a ghost. This allows these buildings to be automatically re-built if construction bots are available in the area.

== Interaction with construction robots ==

Construction robots will place the real version of an entity or tile ghost if either of the following conditions are met:
* The materials required to build the object are available in the [[logistic network]], and enough construction robots are free to begin the placing.
* The materials required to build the object are available from the player's inventory, the player is equipped with one or more [[personal roboport]]s, and is carrying one or more [[construction robot]]s.

== Lifetime of ghosts ==

Ghosts that are placed by the player will last forever. Ghosts for destroyed entities will last a week of [[Time|game time]]. Their remaining time is indicated by the purple bar below the ghost.

== Gallery ==
<gallery widths=200px>
File:automated_construction_concrete.gif|Construction robots paving a [[Refined concrete]] path. ''(Click to see GIF animation)''
File:railway_three_ghost.png|The top and middle part of a 3-way railway in "ghost mode".
</gallery>

== History ==

{{History|0.17.0|
* Trains and wagons can now be blueprinted and therefore can be ghost entities.
* Added the setting '''Pick ghost item if no items are available'''.}}

{{History|0.16.0|
* When building a different entity on top of a ghost, settings from the ghost will be copied if possible.
* Blueprint previews and ghost entities now have their walls, pipes and belts connected.}}

{{History|0.15.0|
* Manual ghost building will mark trees/rocks for deconstruction.}}

== See also ==
* [[Blueprint]]
* [[Deconstruction planner]]
* [[Upgrade planner]]
* [[Blueprint book]]
* [[Logistic network]]
* [[Roboport]]
* [[Personal roboport]]
* [[Construction robot]]

Ghost

2019-03-28T13:29:20Z

TheBloke: Initial creation of page, merged from Entity_ghost

{{Languages}}
[[File:medium_electric_pole_ghost.png|thumb|180px|Ghosts of [[Medium electric pole]]s at the top row, with normally placed ones below.]]
A '''ghost''' is a semi-transparent marker for an entity or [[tile]] which can be placed as a planning tool for future manual building or for [[construction robot]]s to place using the supplies of a [[logistic network]]. A ghost does not perform any of the functions of the object it represents, but exists to mark the spot where the item should later be built or, in the case where an entity was destroyed, the place where it stood. A ghost can store configuration information such as the recipe used by an [[assembling machine]]; this configuration will become active when the real entity is placed on top of the ghost.

== Valid ghosts ==

=== Entities ===

The majority of entities placeable by the player can be ghosts. Exceptions include mobile entities such as the [[car]], [[tank]] and [[robot]]s. Trains and cargo wagons are valid ghosts but must be placed on a [[rail]].

=== Tiles ===

Any tile that can be placed by the player is valid as a ghost.

== Usage ==
[[File:cursor_ghost.png|frame|right|The cursor as it appears prior to placing an entity ghost.]]
=== Placing single ghosts ===

Single ghosts are placed in the same way as normal entities and tiles: by clicking with {{keybinding|lmb}} on the map.

In order to place a ghost, the player must first have one in their hand:

==== Holding shift while holding an entity or tile ====

If {{keybinding|Shift}} is held with an entity or tile in the hand, the ghost symbol appears. Click {{keybinding|lmb}} will now place a ghost instead of the object itself.

==== Enabling '''Pick ghost item if no items are available''' ====

Under Settings->Interface is the option '''Pick ghost item if no items are available'''. If this is enabled a ghost item will be provided to the player whenever they select an entity or tile which is not available in their inventory. This affects both the pipette tool ({{keybinding|Q}}) and selecting an item from the [[quickbar]].

=== Blueprints ===

Placing a [[blueprint]] will place ghosts for all the entities and tiles contained within the blueprint.

=== Rail planner ===

When placing [[rail]]s the [[rail planner]] is a convenient way to place a large number of rails, and is required for placing curved rails. The rail planner will place ghosts when {{keybinding|Shift}} is held at the same time as clicking a rail planner arrow. In ghost mode the rail planner can be used to place ghost rails of any length.

=== Destroyed entities ===

Once [[Construction robotics (research)|construction robotics]] has been researched any entities that are destroyed (for example by [[enemies]]) will leave behind a ghost. This allows these buildings to be automatically re-built if construction bots are available in the area.

== Interaction with construction robots ==

Construction robots will place the real version of an entity or tile ghost if either of the following conditions are met:
* The materials required to build the object are available in the [[logistic network]], and enough construction robots are free to begin the placing.
* The materials required to build the object are available from the player's inventory, the player is equipped with one or more [[personal roboport]]s, and is carrying one or more [[construction robot]]s.

== Lifetime of ghosts ==

Ghosts that are placed by the player will last forever. Ghosts for destroyed entities will last a week of [[Time|game time]]. Their remaining time is indicated by the purple bar below the ghost.

== Gallery ==
<gallery widths=200px>
File:automated_construction_concrete.gif|Construction robots paving a [[Refined concrete]] path. ''(Click to see GIF animation)''
File:railway_three_ghost.png|The top and middle part of a 3-way railway in "ghost mode".
</gallery>

== History ==

{{History|0.17.0|
* Trains and wagons can now be blueprinted and therefore can be ghost entities.
* Added the setting '''Pick ghost item if no items are available'''.}}

{{History|0.16.0|
* When building a different entity on top of a ghost, settings from the ghost will be copied if possible.
* Blueprint previews and ghost entities now have their walls, pipes and belts connected.}}

{{History|0.15.0|
* Manual ghost building will mark trees/rocks for deconstruction.}}

== See also ==
* [[Blueprint]]
* [[Deconstruction planner]]
* [[Upgrade planner]]
* [[Blueprint book]]
* [[Logistic network]]
* [[Roboport]]
* [[Personal roboport]]
* [[Construction robot]]

File:ImportString.png

2019-03-28T10:41:24Z

TheBloke: {{Screenshot}} The Import String icon on the shortcut bar. Can be used to import a string that re-creates a blueprint, blueprint book, deconstruction planner, or upgrade planner.

== Summary ==
{{Screenshot}}
The Import String icon on the [[shortcut bar]]. Can be used to import a string that re-creates a [[blueprint]], blueprint book, [[deconstruction planner]], or [[upgrade planner]].

File:DeconstructionPlanner-ExampleWhitelistDefences.png

2019-03-28T10:23:44Z

TheBloke: {{Screenshot}} An example of a deconstruction planner with a whitelist filter that will only walls, gates, gun turrets, laser turrets, flamethrower turrets, artillery turrets and landmines. This can be useful when the pl...

== Summary ==
{{Screenshot}}
An example of a [[deconstruction planner]] with a whitelist filter that will only [[wall]]s, [[gate]]s, [[gun turret]]s, [[laser turret]]s, [[flamethrower turret]]s, [[artillery turret]]s and [[landmine]]s. This can be useful when the player wishes to remove old defensive structures from areas that are now safe.

File:DeconstructionPlanner-SetFilterEnvironment.png

2019-03-27T18:33:58Z

TheBloke: {{Screenshot}} The deconstruction planner set filter window, showing the Environment tab. This lists cliffs, fish and all types of trees and rocks.

== Summary ==
{{Screenshot}}
The [[deconstruction planner]] set filter window, showing the Environment tab. This lists [[cliff]]s, [[fish]] and all types of [[tree]]s and [[rock]]s.

File:TrashCan.png

2019-03-27T17:42:41Z

TheBloke: {{Screenshot}} The trash can icon clicked on to delete blueprints, blueprint books, deconstruction planners and upgrade planners.

== Summary ==
{{Screenshot}}
The trash can icon clicked on to delete [[blueprint]]s, blueprint books, [[deconstruction planner]]s and [[upgrade planner]]s.

File:ExportToString.png

2019-03-27T17:41:48Z

TheBloke: TheBloke uploaded a new version of File:ExportToString.png

== Summary ==
{{Screenshot}}
The Export to String icon used for exporting [[blueprint]]s, blueprint books, [[deconstruction planner]]s and [[upgrade planner]]s.

File:DeconstructionPlanner-Fish.png

2019-03-27T15:00:26Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-Fish.png

== Summary ==
{{Screenshot}}
Using a [[deconstruction planner]] to mark [[fish]] for removal. The fish will be collected by any available [[construction robot]]s. This is especially useful when combined with a [[personal roboport]] as it provides the player with a means to replenish their supplies of healing items, even in the middle of combat.

File:DeconstructionPlanner-Fish.png

2019-03-27T14:50:42Z

TheBloke: {{Screenshot}} Using a deconstruction planner to mark fish for removal. The fish will be collected by any available construction robots. This is especially useful when combined with a personal roboport as it provides the player with a m...

File:DeconstructionPlanner-IconFiltered.png

2019-03-27T14:33:58Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-IconFiltered.png

== Summary ==
{{Screenshot}}
An example [[deconstruction planner]] icon, showing its first four filters. In this case the deconstruction planner is filtered on [[laser turret]]s, [[gun turret]]s, [[flamethrower turret]]s and [[artillery turret]]s.

File:DeconstructionPlanner-IconFiltered.png

2019-03-27T14:16:02Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-IconFiltered.png

File:DeconstructionPlanner-IconFiltered.png

2019-03-27T14:11:36Z

TheBloke: {{Screenshot}} An example deconstruction planner icon, showing its first four filters. In this case the deconstruction planner is filtered on laser turrets, gun turrets, flamethrower turrets and artillery turrets.

File:DeconstructionPlanner-ExampleBlacklistPowerandRoboports.png

2019-03-27T13:32:02Z

TheBloke: {{Screenshot}} An example of a deconstruction planner with a blacklist filter that will remove anything except small electric poles, medium electric poles, big electric poles, substations and roboports. This can be useful to rem...

== Summary ==
{{Screenshot}}
An example of a [[deconstruction planner]] with a blacklist filter that will remove anything except [[small electric pole]]s, [[medium electric pole]]s, [[big electric pole]]s, [[substation]]s and [[roboport]]s. This can be useful to remove production facilities without affecting power and logistic infrastructure.

Small electric pole

2019-03-27T13:30:59Z

TheBloke: Add Medium Electric Pole to the See Also list /* See also */

{{Languages}}
{{:Infobox:Small electric pole}}

The '''small electric pole''' is the basic [[Electric system#Distribution|electric pole]]. It has a short wire reach and small supply area, but it is also available from the beginning of the game. Typically, it is replaced in factories by [[medium electric pole]]s later in the game.

== History ==

{{history|0.17.0|
* Small electric poles are no longer usable as fuel.}}

{{history|0.11.0|
* Small electric poles now have a fuel value.}}

{{history|0.9.8|
* New small pole graphics.}}

{{history|0.9.0|
* Visualizations of Area of effect when hovering on pole.
* Further optimization on building while holding mouse down.}}

{{history|0.7.0|
* Poles now auto-connect to all poles in reach with no common neighbor.
* Building electric poles with shift pressed builds it without any connections.}}

{{history|0.6.3|
* Max wire distance between poles is limited to the smallest pole's when manually connecting.}}

{{history|0.5.0|
* Shows what is connected to the electric pole when selected.
* Added electric network statistics}}

{{history|0.2.1|
* Made building of electric poles more convenient}}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Electric system]]
* [[Medium electric pole]]
* [[Big electric pole]]
* [[Substation]]

{{LogisticsNav}}
{{C|Energy and fluid distribution}}

File:DeconstructionPlanner-DraggingAPlannerMarkers.png

2019-03-27T13:23:29Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-DraggingAPlannerMarkers.png

== Summary ==
{{Screenshot}}
The red 'X' markers that indicate queued destruction orders after a [[deconstruction planner]] is used.

File:DeconstructionPlanner-DraggingAPlannerTooltip.png

2019-03-27T13:22:50Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-DraggingAPlannerTooltip.png

== Summary ==
{{Screenshot}}
An example of the tooltip shown when a [[deconstruction planner]] is dragged over some entities.

File:DeconstructionPlanner-DraggingAPlanner.png

2019-03-27T13:22:10Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-DraggingAPlanner.png

== Summary ==
{{Screenshot}}
An example of dragging a blank [[deconstruction planner]] over some entities and tiles. All entities are selected but the tiles are not as they are not marked by a blank planner when entities are also present.

Cliff

2019-03-27T09:25:35Z

TheBloke: Added 0.17.0 history items /* History */

{{Languages}}{{:Infobox:Cliff}}
'''Cliffs''' are part of the natural terrain generation. Cliffs are usually generated in lines with gaps, creating significant obstacles that have to be avoided until they can be blown up using [[Cliff explosives]]. They do not drop any resources when removed. Driving into cliffs does not damage the [[vehicle]].

Cliffs should not be generated in the [[World_generator#Starting_area|starting area]], but [https://forums.factorio.com/54664 due to a bug], they can be generated there. While it looks like they create elevation, this is just a visual trick and no elevation is actually present. This means that other entites can be built around cliffs as usual, including underground belts/pipes going "under" cliffs.

[[Turret]]s can be placed "atop" cliffs for a tactical advantage - firing from an area the enemy can't easily get to. Players should be wary of the environment, as it's possible to be cornered in an area surrounded by cliffs; however, players can also use such a setup to funnel enemies into a specific area. Cliff walls going straight across and facing north can have [[long handed inserter|long handed inserters]] move items past them, though cliffs of any other nature are too thick for such inserters to reach across.

[[File:longinserter_cliff.png|thumb|right|180x180px|A long handed inserter reaching across the cliff.]]

== History ==

{{history|0.17.0|
* Map generation will now produce more predictable cliff placement.
* Map generation settings have better controls for cliffs.
* Cliffs can now be marked with the [[deconstruction planner]] and removed by [[construction robot]]s.}}

{{history|0.16.0|
* Introduced}}

== See also ==

* [https://www.factorio.com/blog/post/fff-219 Friday Facts #219 - Cliffs]

File:ExportToString.png

2019-03-26T22:48:57Z

TheBloke: {{Screenshot}} The Export to String icon used for exporting blueprints, blueprint books, deconstruction planners and upgrade planners.

== Summary ==
{{Screenshot}}
The Export to String icon used for exporting [[blueprint]]s, blueprint books, [[deconstruction planner]]s and [[upgrade planner]]s.

File:DeconstructionPlanner-UndoDemo.gif

2019-03-26T17:38:30Z

TheBloke: Typo fix and wording changes /* Summary */

== Summary ==
{{Screenshot}}
A demonstration of using Undo to revert the actions of a [[deconstruction planner]]. Items marked for removal with a red X have the marks removed; ghosts are replaced immediately; items already removed by construction bots are reinstated as ghosts so that bots can replace them.

File:DeconstructionPlanner-UndoDemo.gif

2019-03-26T17:37:40Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-UndoDemo.gif

== Summary ==
{{Screenshot}}
A demonstration of using Undo to revert the actions of a [[deconstuction planner]]. Items marked for removal with a red X have the marks removed; items already removed by construction bots are replaced with ghosts so that bots can replace them.

File:DeconstructionPlanner-UndoDemo.gif

2019-03-26T15:17:31Z

TheBloke: {{Screenshot}} A demonstration of using Undo to revert the actions of a deconstuction planner. Items marked for removal with a red X have the marks removed; items already removed by construction bots are replaced with ghosts so that bots can replac...

File:DeconstructionPlanner-Demo.gif

2019-03-25T22:32:37Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-Demo.gif

== Summary ==
{{Screenshot}}
A demonstration of the [[deconstruction planner]] being used to remove a [[electronic circuit]] production line.

File:DeconstructionPlanner-Demo.gif

2019-03-25T21:29:53Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-Demo.gif

== Summary ==
{{Screenshot}}
A demonstration of the [[deconstruction planner]] being used to remove a [[electronic circuit]] production line.

File:DeconstructionPlanner-CancelDemo.gif

2019-03-25T20:56:56Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-CancelDemo.gif

== Summary ==
{{Screenshot}}
A demonstration of using a [[deconstruction planner]] to cancel deconstruction orders previously placed with another deconstruction planner.

File:DeconstructionPlanner-CancelDemo.gif

2019-03-25T20:55:20Z

TheBloke: typo /* Summary */

== Summary ==
{{Screenshot}}
A demonstration of using a [[deconstruction planner]] to cancel deconstruction orders previously placed with another deconstruction planner.

File:DeconstructionPlanner-Demo.gif

2019-03-25T16:11:01Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-Demo.gif

== Summary ==
{{Screenshot}}
A demonstration of the [[deconstruction planner]] being used to remove a [[electronic circuit]] production line.

File:DeconstructionPlanner-CancelDemo.gif

2019-03-25T16:03:24Z

TheBloke: {{Screenshot}} A demonstration of using a deconstruction planner to cancel deconstruction orders previously with another deconstruction planner.

== Summary ==
{{Screenshot}}
A demonstration of using a [[deconstruction planner]] to cancel deconstruction orders previously with another deconstruction planner.

File:DeconstructionPlanner-DraggingAPlannerMarkers.png

2019-03-25T15:18:40Z

TheBloke: {{Screenshot}} The red 'X' markers that indicate queued destruction orders after a deconstruction planner is used.

== Summary ==
{{Screenshot}}
The red 'X' markers that indicate queued destruction orders after a [[deconstruction planner]] is used.

File:DeconstructionPlanner-DraggingAPlannerTooltip.png

2019-03-25T15:15:05Z

TheBloke: {{Screenshot}} An example of the tooltip shown when a deconstruction planner is dragged over some entities.

== Summary ==
{{Screenshot}}
An example of the tooltip shown when a [[deconstruction planner]] is dragged over some entities.

File:DeconstructionPlanner-DraggingAPlanner.png

2019-03-25T15:12:16Z

TheBloke: {{Screenshot}} An example of dragging a blank deconstruction planner over some entities and tiles. All entities are selected but the tiles are not as they are not marked by a blank planner when entities are also present.

Landfill

2019-03-25T12:10:39Z

TheBloke: Add 0.17 changes to landfill /* History */

{{Languages}}
{{:Infobox:Landfill}}
'''Landfill''' can be used to fill in water with grass, regardless of the type of surrounding terrain. Once an area has been filled, there is no way to revert the fill and return water. It is placed using {{Keybinding|lmb}} and the area in which it is placed can be increased and decreased by using {{Keybinding|numplus}} and {{Keybinding|numminus}}. Land-filled area is indistinguishable from normal terrain in terms of mechanics; it can be normally built and walked over.

Note that placing a landfill where [[raw fish]] are swimming will "destroy" them without being collected.

== History ==

{{History|0.17.10|
* Landfill is now a separate tile, differentiated from grass-1.}}

{{History|0.17.0|
* Landfill can now be included in blueprints and placed by construction robots.}}

{{history|0.13.0|
* Introduced}}

{{LogisticsNav}}
{{C|Terrain}}

File:DeconstructionPlanner-ShortcutIcon.png

2019-03-25T11:35:27Z

TheBloke: {{Screenshot}} The shortcut bar icon for the deconstruction planner.

== Summary ==
{{Screenshot}}
The [[shortcut bar]] icon for the [[deconstruction planner]].

File:DeconstructionPlanner-BlankTiles.png

2019-03-25T11:31:56Z

TheBloke: TheBloke uploaded a new version of File:DeconstructionPlanner-BlankTiles.png

== Summary ==
{{Screenshot}}
A blank [[deconstruction planner]] showing the [[tiles]] tab.

File:DeconstructionPlanner-Demo.gif

2019-03-25T11:21:19Z

TheBloke: {{Screenshot}} A demonstration of the deconstruction planner being used to remove a electronic circuit production line.

== Summary ==
{{Screenshot}}
A demonstration of the [[deconstruction planner]] being used to remove a [[electronic circuit]] production line.

File:DeconstructionPlanner-BlankEntities.png

2019-03-25T09:51:08Z

TheBloke: {{Screenshot}} A blank deconstruction planner showing the entities tab.

== Summary ==
{{Screenshot}}
A blank [[deconstruction planner]] showing the entities tab.

File:DeconstructionPlanner-BlankTiles.png

2019-03-25T09:50:35Z

TheBloke: {{Screenshot}} A blank deconstruction planner showing the tiles tab.

== Summary ==
{{Screenshot}}
A blank [[deconstruction planner]] showing the [[tiles]] tab.

Map structure

2019-03-16T13:56:15Z

TheBloke: Minor corrections

{{Languages}}

'''Map structure''' describes the division of the game world into standard [[Units|units]]: tiles, chunks and regions. Tiles are the building blocks of the game, upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

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 9x9. The smallest possible entity size is therefore one tile, 1x1. Examples of 1x1 entities include [[transport belts]] and [[chests]].

The [[World_generator#Maximum_map_size_and_used_memory|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 [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and decoratives.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]).
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real world size analogy ===

One tile is generally assumed to be one square meter in size (the same as used by Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this forum discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* 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.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|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 {{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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 262,144 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-16T13:44:35Z

TheBloke: Correct number of tiles in region. Was only an order of magnitude out. /* Region */

{{Languages}}

'''Map structure''' describes the division of the game world area into standard [[Units|units]]: tiles, chunks and regions. Tiles are the building blocks of the game, upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

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 9x9. The smallest possible entity size is therefore one tile, 1x1. Examples of 1x1 entities include [[transport belts]] and [[chests]].

The [[World_generator#Maximum_map_size_and_used_memory|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 [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and decoratives.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]).
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real world size analogy ===

One tile is generally assumed to be one square meter in size (the same as used by Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this forum discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* 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.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 262,144 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-15T20:57:16Z

TheBloke: Further changes throughout

{{Languages}}

'''Map structure''' describes the division of the game world area into standard [[Units|units]]: tiles, chunks and regions. Tiles are the building blocks of the game, upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

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 9x9. The smallest possible entity size is therefore one tile, 1x1. Examples of 1x1 entities include [[transport belts]] and [[chests]].

The [[World_generator#Maximum_map_size_and_used_memory|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 [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and decoratives.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]).
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real world size analogy ===

One tile is generally assumed to be one square meter in size (the same as used by Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this forum discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* 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.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 268,435,456 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-15T16:02:29Z

TheBloke: Actually, better to link to enemy expansion specifically here /* Chunk */

{{Languages}}

'''Map structure''' refers to the physical division of the game world into standard [[Units|units]] of area: tiles, chunks and regions. Tiles are the building blocks of the game upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

A '''tile''' is a square area which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The size of all entities is defined as a certain area of tiles, for example a [[rocket silo]] - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9x9. The smallest possible entity is the same size as one tile, or 1x1. Examples of 1x1 entities include [[transport belts]] and [[underground belts]], [[chests]], and [[small electric pole]]s and [[medium electric pole]]s.

The maximum number of tiles available in one map is 4 trillion - the [[World_generator#Maximum_map_size_and_used_memory|maximum size of the game map]] is a square 2 million tiles on a side. In practice the average game map is likely to consist of up to a few million tiles.

=== Tile grid alignment ===

Almost all placeable entities are aligned to the tile grid when placed in the game. Exceptions include the [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and certain decorative items.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]. Ror more information see [[Radar]].
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real size of tiles ===

1 tile is generally assumed to be 1 square meter in size (like Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
* [[Enemies#Expansions|Enemy expansion]] is based on chunks. 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 according to their suitability. A chunk is then picked at random using a weighted dice roll.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 268,435,456 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-15T16:01:04Z

TheBloke: Remove link to enemies as already linked in previous section /* Chunk */

{{Languages}}

'''Map structure''' refers to the physical division of the game world into standard [[Units|units]] of area: tiles, chunks and regions. Tiles are the building blocks of the game upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

A '''tile''' is a square area which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The size of all entities is defined as a certain area of tiles, for example a [[rocket silo]] - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9x9. The smallest possible entity is the same size as one tile, or 1x1. Examples of 1x1 entities include [[transport belts]] and [[underground belts]], [[chests]], and [[small electric pole]]s and [[medium electric pole]]s.

The maximum number of tiles available in one map is 4 trillion - the [[World_generator#Maximum_map_size_and_used_memory|maximum size of the game map]] is a square 2 million tiles on a side. In practice the average game map is likely to consist of up to a few million tiles.

=== Tile grid alignment ===

Almost all placeable entities are aligned to the tile grid when placed in the game. Exceptions include the [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and certain decorative items.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]. Ror more information see [[Radar]].
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real size of tiles ===

1 tile is generally assumed to be 1 square meter in size (like Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
* Enemy expansion is based on chunks. 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 according to their suitability. A chunk is then picked at random using a weighted dice roll.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 268,435,456 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-15T15:58:49Z

TheBloke: Wording changes, link fixes /* Tile */

{{Languages}}

'''Map structure''' refers to the physical division of the game world into standard [[Units|units]] of area: tiles, chunks and regions. Tiles are the building blocks of the game upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

A '''tile''' is a square area which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The size of all entities is defined as a certain area of tiles, for example a [[rocket silo]] - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9x9. The smallest possible entity is the same size as one tile, or 1x1. Examples of 1x1 entities include [[transport belts]] and [[underground belts]], [[chests]], and [[small electric pole]]s and [[medium electric pole]]s.

The maximum number of tiles available in one map is 4 trillion - the [[World_generator#Maximum_map_size_and_used_memory|maximum size of the game map]] is a square 2 million tiles on a side. In practice the average game map is likely to consist of up to a few million tiles.

=== Tile grid alignment ===

Almost all placeable entities are aligned to the tile grid when placed in the game. Exceptions include the [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[trees]] and certain decorative items.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]. Ror more information see [[Radar]].
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real size of tiles ===

1 tile is generally assumed to be 1 square meter in size (like Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
* [[Enemy]] expansion is based on chunks. 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 according to their suitability. A chunk is then picked at random using a weighted dice roll.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 268,435,456 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

Map structure

2019-03-15T15:53:45Z

TheBloke: Finished merge of tile, chunk and region into Map_structure. Added some example images.

{{Languages}}

'''Map structure''' refers to the physical division of the game world into standard [[Units|units]] of area: tiles, chunks and regions. Tiles are the building blocks of the game upon which all distance and area measurements are based. Chunks are blocks of 32x32 tiles used for various area-based calculations. Regions are much less commonly used, and may be seen only in certain debug text.

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

A '''tile''' is a square area which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The size of all entities is defined as a certain area of tiles, for example a [[rocket silo]] - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9x9. The smallest possible entity is the same size as one tile, or 1x1. Examples of 1x1 entities include [[transport belt]]s, all [[chests]], and [[small electric pole]] and [[medium electric pole]]s.

The maximum number of tiles available in one map is 4 trillion - the [[World_generator#Maximum_map_size_and_used_memory|maximum size of the game map]] is a square 2 million tiles on a side. In practice the average game map is likely to consist of up to a few million tiles.

=== Tile grid alignment ===

Almost all placeable entities are aligned to the tile grid when the player places them in the game. Exceptions include the [[landmine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include enemies, [[trees]] and certain decorative items.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]. Ror more information see [[Radar]].
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [https://wiki.factorio.com/Talk:Exoskeleton#Movement%20speed%20experiments] (As a side note, this would mean that the character is a very healthy person.)

=== Real size of tiles ===

1 tile is generally assumed to be 1 square meter in size (like Minecraft), as [https://forums.factorio.com/viewtopic.php?f=5&t=9182&p=73352#p73266 this discussion] confirms.

== Chunk ==

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 shell]]s 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|tick]].
* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
* [[Enemy]] expansion is based on chunks. 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 according to their suitability. A chunk is then picked at random using a weighted dice roll.

== 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 {{Keybinding|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 mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' while show it 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.

== Region ==

A '''Region''' is an area of 16 by 16 chunks; 268,435,456 tiles.

No game mechanic depends on regions and there are no [[modding]] APIs that access the game by region. Currently they are only used internally for organizing allocations, and there is a chance that they will be removed from the game in the future.

=== References ===
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5754

File:MapStructure-PlaceableOffGridExample.png

2019-03-15T15:34:56Z

TheBloke: {{Screenshot}} An example of entities that can be placed without being aligned to a tile. Some landmines, a tank and a car have been placed. The tile grid made visible using debug mode indicates that these entities are not aligned to th...

== Summary ==
{{Screenshot}}
An example of entities that can be placed without being aligned to a tile. Some [[landmine]]s, a [[tank]] and a [[car]] have been placed. The tile grid made visible using [[debug mode]] indicates that these entities are not aligned to the [[map structure|tile grid]].

File:MapStructure-GridExample.png

2019-03-15T13:16:37Z

TheBloke: {{Screenshot}} An example of the tile and chunk grid that can be accessed with debug settings, and can also displayed whenever the game is paused. Tiles are the building blocks on which the map structure is based. Chunks are 32x32 bl...

== Summary ==
{{Screenshot}}
An example of the tile and chunk grid that can be accessed with [[debug mode|debug settings]], and can also displayed whenever the game is paused. Tiles are the building blocks on which the [[map structure]] is based. Chunks are 32x32 blocks of tiles that used for many of the game's calculations, such as [[radar]] coverage and [[pollution].