PlaceAnywhere

Passes every placement legality test without examining a single cell.

Specification

Applies to

BuildingType

File

rules.ini

Section

[<ObjectType ID>]

Value

boolean

When omitted

no

The legality test a BuildingType is put through ordinarily walks its whole foundation and asks each covered cell whether it is clear to build: nothing already occupying it, inside the local radar bounds, no overlay in the way, off a bridge, off a cell under a bridge, off a ramp, and on a land type carrying Buildable=yes. A type that paves what it covers needs only one cell of the foundation to pass; every other type needs all of them.

This flag answers that test with success before any of it runs. The whole foundation is skipped, and so is the guard that would refuse a placement with no cell at all behind it. Five things ask the question and take the answer it gives:

• The structure’s own arrival on the map. A structure that fails the test is never put down; a flagged one is put down wherever it was asked for.
• The deploy cursor and the deploy order on a vehicle whose DeploysInto names the type, and the search a vehicle runs for a nearby spot it could deploy on.
• The unload step of a team script, which otherwise clears the cell and waits.
• The computer’s search for a spot in its base, which still applies its own spacing, height and adjacency conditions on top.

The placement cursor does not read the flag

The cursor drawn while a player carries a pending structure asks each covered cell whether it is clear to build directly, rather than through the type’s own legality test, so a flagged structure keeps showing the blocked cursor over ground it could not otherwise take. The click is gated on adjacency and shroud alone, so the placement then succeeds anyway.

See also — Buildable, DeploysInto, base-adjacency

Page feedback

Report an error or missing detail. The issue includes this page and revision.

Open issueSource revision 59fae722af8c