ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
Difference between revisions of "AIBuildsWalls"
From ModEnc
Nighthawk200 (talk | contribs) (Dedeerified.) |
EvilRenegade (talk | contribs) m (Replacing Template:TTL with Template:F.) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{flag |
| − | |name= | + | |name=AIBuildsWalls |
| − | |files={{ | + | |files={{categ|ini=rules}} |
| − | | | + | |values={{values|bool}} |
| − | | | + | |default=true |
| + | |types={{categ|General}} | ||
|ts=yes | |ts=yes | ||
|fs=yes | |fs=yes | ||
| Line 12: | Line 13: | ||
|ra2obsolete=yes | |ra2obsolete=yes | ||
}} | }} | ||
| − | |||
| + | ==In Tiberian Sun== | ||
| + | In {{ts}} and {{fs}}, when set to yes, this flag will cause the GDI AI to build walls. With the introduction of the new wall logic in one of the {{ts}} patches, the AI tends to block off its own base due to the inability to construct walls properly, thus leading to major performance hits due to pathfinding. Therefore it is probably better to keep this tag set to no. | ||
| − | In {{ra2}} and {{yr}}, this | + | ==In Red Alert 2== |
| + | In {{ra2}} and {{yr}}, this flag has no effect and has been superseded by the {{f|ProtectWithWall|link}} logic, which enables the AI to construct walls around [[BuildingTypes]] with {{tt|ProtectWithWall{{=}}yes}} set. | ||
Latest revision as of 09:12, 27 November 2009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | AIBuildsWalls |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | true |
| Applicable to: | General |
| |
In Tiberian Sun
In Tiberian Sun and Firestorm, when set to yes, this flag will cause the GDI AI to build walls. With the introduction of the new wall logic in one of the Tiberian Sun patches, the AI tends to block off its own base due to the inability to construct walls properly, thus leading to major performance hits due to pathfinding. Therefore it is probably better to keep this tag set to no.
