Foundation - Revision history

Rain-Islet: [bot] Batch update {{Bugs}} templates.

2025-07-02T15:25:20Z

[bot] Batch update {{Bugs}} templates.

← Older revision		Revision as of 17:25, 2 July 2025
Line 32:		Line 32:
	Foundation <code>0x0</code> works a bit differently from the others as well. Such structures are completely immune to normal [[Weapons\|weapon]] damage and thus cannot be destroyed in the standard way. They however ''are'' vulnerable to weapons whose [[Warheads\|warhead]] has {{f\|Temporal\|yes\|link}}. <code>0x0</code> structures do not occupy physical space, which allows units to move over the cell one of these structures was placed on. They also display their appropriate {{f\|UIName\|link}} strings if the cursor is hovered over the cell the structure was placed on. Apart from this, they function pretty much like structures with normal foundations, although the [[AI]] has some issues handling them[[{{PAGENAME}}#0x0AI\|{{sup\|{{arr\|d}}}}]].		Foundation <code>0x0</code> works a bit differently from the others as well. Such structures are completely immune to normal [[Weapons\|weapon]] damage and thus cannot be destroyed in the standard way. They however ''are'' vulnerable to weapons whose [[Warheads\|warhead]] has {{f\|Temporal\|yes\|link}}. <code>0x0</code> structures do not occupy physical space, which allows units to move over the cell one of these structures was placed on. They also display their appropriate {{f\|UIName\|link}} strings if the cursor is hovered over the cell the structure was placed on. Apart from this, they function pretty much like structures with normal foundations, although the [[AI]] has some issues handling them[[{{PAGENAME}}#0x0AI\|{{sup\|{{arr\|d}}}}]].
	'''WARNING: 0x0 buildings do NOT expand the base even when {{f\|BaseNormal\|yes\|link}}!'''		'''WARNING: 0x0 buildings do NOT expand the base even when {{f\|BaseNormal\|yes\|link}}!'''
	{{Bugs}}		=={{Bugs}}==
	This flag is read from {{Ini\|art}} 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		This flag is read from {{Ini\|art}} 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]		[GAYARD]

MarkJFox: 24 revisions imported

2025-04-04T18:47:19Z

24 revisions imported

← Older revision	Revision as of 20:47, 4 April 2025
(No difference)

en>Testid123 at 05:45, 3 March 2025

2025-03-03T05:45:10Z

← Older revision		Revision as of 07:45, 3 March 2025
Line 12:		Line 12:
	\|ares=yes		\|ares=yes
	}}		}}

	This flag determines the number of [[cell]]s a [[BuildingType\|structure]] occupies, and the arrangement of those cells.		This flag determines the number of [[cell]]s a [[BuildingType\|structure]] occupies, and the arrangement of those cells.

Line 91:		Line 90:

	===Notes===		===Notes===
	[[WeaponsFactory\|Weapons Factories]] are hard-coded to use the unit exit paths from the original game so changing the foundation for these buildings is not recommended.		*[[WeaponsFactory\|Weapons Factories]] are hard-coded to use the unit exit paths from the original game so changing the foundation for these buildings is not recommended.<br>
			The Custom Foundation Generator located with the Renegade Project Network is incompatible with Google Chrome, and results in gibberish. Be advised.<br>
	The Custom Foundation Generator located with the Renegade Project Network is incompatible with Google Chrome, and results in gibberish. Be advised.		*It's funny for units, if a unit is built too big,it will cause other objects to enter the unit's area (since the [[Foundation]] tag doesn't apply to units).<br>
			[!]This shouldn't be too hard for Westwood, and they should have done it since [[RA1]] and they had plenty of time before they were '''EA''' bought.

Crimsonum: Moved and updated note on weapons factories

2023-02-14T07:05:29Z

Moved and updated note on weapons factories

← Older revision		Revision as of 09:05, 14 February 2023
Line 44:		Line 44:
	===Construction Yards===		===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.		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.

			===Weapons Factories===

			The preferred exit point for a unit exiting a [[WeaponsFactory\|Weapons Factory]] is hardcoded to be the 8th and 11th cells in TS and RA2/YR respectively (counted from the building origin by increasing X, then Y).

	==Ares's Custom Foundations==		==Ares's Custom Foundations==
Line 87:		Line 91:

	===Notes===		===Notes===
	~~War~~ Factories are hard-coded to use the unit exit paths from the original game so changing the foundation for these buildings is not recommended~~. The preferred exit point for a unit exiting a War Factory is hard-coded to be the 11th cell of the Outline~~.		[[WeaponsFactory\|Weapons Factories]] are hard-coded to use the unit exit paths from the original game so changing the foundation for these buildings is not recommended.

	The Custom Foundation Generator located with the Renegade Project Network is incompatible with Google Chrome, and results in gibberish. Be advised.		The Custom Foundation Generator located with the Renegade Project Network is incompatible with Google Chrome, and results in gibberish. Be advised.

Crimsonum: Minor typo fix.

2020-09-30T10:02:33Z

Minor typo fix.

← Older revision		Revision as of 12:02, 30 September 2020
Line 16:		Line 16:

	=={{anchor\|values\|\|}}Accepted values==		=={{anchor\|values\|\|}}Accepted values==
	All values are case-insensitive. Any other values will simply be ignored and the default used instead; however [[Ares]] can be utilized to create custom foundations. The first number represents the cell-count along the NW-SE axis, the second along the NE-NW axis.		All values are case-insensitive. Any other values will simply be ignored and the default used instead; however [[Ares]] can be utilized to create custom foundations. The first number represents the cell-count along the NW-SE axis, the second along the NE-SW axis.

	0x0, 6x4, 3x4, 4x4, 5x3, 2x5, 2x6, 1x5, 1x4, 4x3, 3x1, 1x3, 3x3REFINERY, 4x2, 3x5, 3x3, 3x2, 2x3, 2x2, 1x2, 2x1, 1x1		0x0, 6x4, 3x4, 4x4, 5x3, 2x5, 2x6, 1x5, 1x4, 4x3, 3x1, 1x3, 3x3REFINERY, 4x2, 3x5, 3x3, 3x2, 2x3, 2x2, 1x2, 2x1, 1x1

en>Mrwinde: Custome Foundations

2017-05-19T08:52:31Z

Custome Foundations

@@ Line 44: / Line 44: @@
 ===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.
-<hr />

Crimsonum at 12:12, 23 December 2016

2016-12-23T12:12:37Z

← Older revision		Revision as of 14:12, 23 December 2016
Line 28:		Line 28:
	[[Image:6x4foundation.png\|frame\|{{f\|Foundation\|6x4}} grid illustration.]]		[[Image:6x4foundation.png\|frame\|{{f\|Foundation\|6x4}} grid illustration.]]

	6x4 ~~is another~~ unusual shape. ~~It produces almost~~ a ~~perfect~~ rectangle, but with three empty cells at the southwest side. It was used for the Scrin Ship ~~in Tiberian Sun~~ and probably coded to match the building art.		In Tiberian Sun, 6x4 produces an unusual shape. The foundation is shaped like a rectangle, but with three empty cells at the southwest side. It was used for the Scrin Ship and probably coded to match the building art.

	===0x0===		===0x0===

Crimsonum: Added information about Foundation value 6x4

2016-10-24T16:58:56Z

Added information about Foundation value 6x4

← Older revision		Revision as of 18:58, 24 October 2016
Line 24:		Line 24:

	Albeit containing "Refinery" in the value string, this will not work for a {{f\|Refinery\|link}} 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 foundation in this case.		Albeit containing "Refinery" in the value string, this will not work for a {{f\|Refinery\|link}} 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 foundation in this case.

			===6x4===
			[[Image:6x4foundation.png\|frame\|{{f\|Foundation\|6x4}} grid illustration.]]

			6x4 is another unusual shape. It produces almost a perfect rectangle, but with three empty cells at the southwest side. It was used for the Scrin Ship in Tiberian Sun and probably coded to match the building art.

	===0x0===		===0x0===

en>TAK02: 0x0 buildings can't expand the base

2016-01-28T07:04:43Z

0x0 buildings can't expand the base

← Older revision		Revision as of 09:04, 28 January 2016
Line 27:		Line 27:
	===0x0===		===0x0===
	Foundation <code>0x0</code> works a bit differently from the others as well. Such structures are completely immune to normal [[Weapons\|weapon]] damage and thus cannot be destroyed in the standard way. They however ''are'' vulnerable to weapons whose [[Warheads\|warhead]] has {{f\|Temporal\|yes\|link}}. <code>0x0</code> structures do not occupy physical space, which allows units to move over the cell one of these structures was placed on. They also display their appropriate {{f\|UIName\|link}} strings if the cursor is hovered over the cell the structure was placed on. Apart from this, they function pretty much like structures with normal foundations, although the [[AI]] has some issues handling them[[{{PAGENAME}}#0x0AI\|{{sup\|{{arr\|d}}}}]].		Foundation <code>0x0</code> works a bit differently from the others as well. Such structures are completely immune to normal [[Weapons\|weapon]] damage and thus cannot be destroyed in the standard way. They however ''are'' vulnerable to weapons whose [[Warheads\|warhead]] has {{f\|Temporal\|yes\|link}}. <code>0x0</code> structures do not occupy physical space, which allows units to move over the cell one of these structures was placed on. They also display their appropriate {{f\|UIName\|link}} strings if the cursor is hovered over the cell the structure was placed on. Apart from this, they function pretty much like structures with normal foundations, although the [[AI]] has some issues handling them[[{{PAGENAME}}#0x0AI\|{{sup\|{{arr\|d}}}}]].
			'''WARNING: 0x0 buildings do NOT expand the base even when {{f\|BaseNormal\|yes\|link}}!'''
	{{Bugs}}		{{Bugs}}
	This flag is read from {{Ini\|art}} 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		This flag is read from {{Ini\|art}} 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

en>Vinifera7: Thanks Starkku for the additional info. Edited for better grammar, clarity, and tagging.

2011-07-31T02:07:35Z

Thanks Starkku for the additional info. Edited for better grammar, clarity, and tagging.

← Older revision		Revision as of 04:07, 31 July 2011
Line 1:		Line 1:
	{{flag		{{flag
	~~\|name=Foundation~~
	\|files={{categ\|ini=art}}		\|files={{categ\|ini=art}}
	\|values={{values\|strings\|[[hardcoded]] values[[{{PAGENAME}}#values\|{{sup\|{{arr\|d}}}}]]}}		\|values={{values\|strings\|[[hardcoded]] values[[{{PAGENAME}}#values\|{{sup\|{{arr\|d}}}}]]}}
Line 14:		Line 13:
	}}		}}

	~~{{f\|Foundation\|link}}~~ determines the number of [[cell]]s a [[BuildingType]] occupies, and the arrangement of those cells.		This flag determines the number of [[cell]]s a [[BuildingType\|structure]] occupies, and the arrangement of those cells.

	=={{anchor\|values\|\|}}Accepted values==		=={{anchor\|values\|\|}}Accepted values==
	All values are case-insensitive. ~~Without Ares, 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.		All values are case-insensitive. Any other values will simply be ignored and the default used instead; however [[Ares]] can be utilized to create custom foundations. 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		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. Ares fixes this.~~

	===3x3REFINERY===		===3x3REFINERY===
	[[Image:3x3refinery.png\|frame\|{{f\|Foundation\|3x3REFINERY~~\|link~~}} grid illustration]] <code>3x3REFINERY</code> is an unusual shape. While all other ~~{{f\|~~foundation~~\|link}}~~ values are rectangles, this one has an empty cell in the center of the third row.		[[Image:3x3refinery.png\|frame\|{{f\|Foundation\|3x3REFINERY}} grid illustration]] <code>3x3REFINERY</code> is an unusual shape. While all other foundation 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 {{f\|Refinery\|link}} 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 ~~{{f\|~~foundation~~\|link}}~~ in this case.		Albeit containing "Refinery" in the value string, this will not work for a {{f\|Refinery\|link}} 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 foundation in this case.

	===0x0===		===0x0===
	Foundation <code>0x0</code> works bit differently from the others as well. Such structures are completely immune to normal weapon damage and thus cannot be destroyed ~~by normal means~~. They however ''~~'ARE'~~'' vulnerable to weapons ~~with a~~ warhead ~~that~~ has {{f\|Temporal\|link}} ~~set to 'yes'~~. ~~They~~ do not ~~physically~~ occupy ~~map cells~~, ~~and thus~~ units ~~can~~ move on the cell ~~such structure~~ was placed on. ~~These structures~~ also display their appropriate {{f\|UIName\|link}} strings if ~~you hover~~ the cursor over the cell ~~you placed~~ the structure on. Apart from this, they function pretty much like normal ~~structures~~, ~~altough~~ AI has some issues handling them ~~(see below)~~.		Foundation <code>0x0</code> works a bit differently from the others as well. Such structures are completely immune to normal [[Weapons\|weapon]] damage and thus cannot be destroyed in the standard way. They however ''are'' vulnerable to weapons whose [[Warheads\|warhead]] has {{f\|Temporal\|yes\|link}}. <code>0x0</code> structures do not occupy physical space, which allows units to move over the cell one of these structures was placed on. They also display their appropriate {{f\|UIName\|link}} strings if the cursor is hovered over the cell the structure was placed on. Apart from this, they function pretty much like structures with normal foundations, although the [[AI]] has some issues handling them[[{{PAGENAME}}#0x0AI\|{{sup\|{{arr\|d}}}}]].

	{{Bugs}}		{{Bugs}}
Line 37:		Line 34:
	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.		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.

	===Foundation 0x0 ~~& AI~~===		==={{anchor\|0x0AI\|\|}}AI Treatment of Foundation 0x0===
	The AI is apparently stupid enough to think that 0x0 structures don't actually exist on the battlefield, and continues to build more and more of them instead of just one.		The AI is apparently stupid enough to think that 0x0 structures don't actually exist on the battlefield, and continues to build more and more of them instead of just one.