Foundation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | Foundation |
| File(s): | art(md).ini |
| Values: | Strings: Normal text. (Limited to: hardcoded values↓) |
| Default: | 1x1 |
| Applicable to: | BuildingTypes |
Template:TTL determines the number of cells a BuildingType occupies, and the arrangement of those cells.
Accepted values
All values are case-insensitive. Any other values will simply be ignored and the default used instead. The first number represents the cell-count along the NW-SE axis, the second along the NE-NW axis.
0x0, 6x4, 3x4, 4x4, 5x3, 2x5, 2x6, 1x5, 1x4, 4x3, 3x1, 1x3, 3x3REFINERY, 4x2, 3x5, 3x3, 3x2, 2x3, 2x2, 1x2, 2x1, 1x1
Note: You cannot make up other foundations, because these are actually hardcoded in the EXE, and only appear to be modifiable.
3x3REFINERY
3x3REFINERY is an unusual shape. While all other Template:TTL values are rectangles, this one has an empty cell in the center of the third row.
Albeit containing "Refinery" in the value string, this will not work for a Template:TTL because the harvester's docking point inside a refinery is hardcoded to be the second cell in the fourth row, which is outside of the Template:TTL in this case.
Bugs/Side-Effects/Unexpected Limitations
This flag is read from art(md).ini twice: from section you specified in rules as [object]->Image , and from simply [object] , and the second one overrules the first if present. This causes weird behaviour, like setting
[GAYARD] Image=NAHAND
in rules still requires a 4x4 Foundation to place, contrary to what logic dictates - you need to remove the Foundation flag from GAYARD to get it to use NAHAND's one.
Construction Yards
The AI seems to have a problem using a Construction Yard with any Foundation smaller than 2x2, it will deploy the construction yard but will not build anything.