ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.

Difference between revisions of "BuildLimit"

From ModEnc
Jump to: navigation, search
(Rewrite and numerous updates.)
m (Marshall, can you use heading levels properly? k thx...)
Line 1: Line 1:
 
{{Flag
 
{{Flag
−
|name={{PAGENAME}}
 
−
|files={{Categ|Rules(md).ini}}
 
 
|values={{Values|signed integer}}
 
|values={{Values|signed integer}}
−
|special=Negative values (see [[#Special Values|Special Values]] below)
+
|special=Negative values{{Sup|[[{{PAGENAME}}#Special_Values|{{Arr|d}}]]}}
−
|default=2147483647 (the comment in rules(md).ini, which states that the default is -1, is incorrect, as is the stated effect of setting BuildLimit=-1)
+
|default=2147483647{{fnl|1}}
 
|types={{CatAllTypes}}
 
|types={{CatAllTypes}}
 
|ts=yes
 
|ts=yes
Line 14: Line 12:
 
}}
 
}}
  
−
Specifies the maximum instances of a particular unit that any given player may own before they will be prevented from building further instances. In the event that a player already owns a number of instances of a unit which is greater than or equal to the unit's {{TTL|BuildLimit}}, that unit's build icon will be greyed-out. The comparison is performed against the number of instances of each unit that the player presently controls, regardless of whether they were trained by the player, awarded to the player at game start, awarded to the player via a map trigger, obtained via a Cloning Vats, obtained via [[mutation]], or mind-controlled.
+
Specifies the maximum instances of a particular unit that any given player may own before they will be prevented from building further instances. Instances of a unit include those that were built by the player, awarded at the start of the campaign or skirmish, awarded via a map trigger, obtained via [[Cloning|Cloning Vats]], obtained via [[mutation]], or mind-controlled. In the event that a player already owns a number of instances of a unit which is greater than or equal to the unit's {{TTL|{{PAGENAME}}}}, that unit's build icon will be greyed-out and the player restricted from queuing it for construction. However the player is not prevented from obtaining additional instances beyond {{TTL|{{PAGENAME}}}} through any of the aforementioned methods other than normal construction.
  
−
A player may own more instances of a unit than the unit's {{TTL|BuildLimit}} permits by acquiring further instances of the unit through means other than building the unit themselves (examples of which are mentioned above).
+
Note that AI players are not subject to any unit's {{TTL|{{PAGENAME}}}}. AI players will build whichever units are required by the chosen {{TTL|TaskForce}} regardless of how many instances of those units the AI player already owns.
  
−
Note that AI players are not subject to any unit's {{TTL|BuildLimit}} - AI players will build whatever units are required by the chosen {{TTL|TaskForce}} regardless of how many instances of those units the AI player already owns.
+
==Special Values==
  
−
=Special Values=
+
Setting {{TTL|{{PAGENAME}}}} to any negative value has a different effect from the normal behaviour. The absolute value of the number is used as the build limit, however this is now a limit on the number of times you can actually build the unit yourself. For example, if {{TTL|{{PAGENAME}}|-5}} is set on the GI then you will only be able to build 5 GIs throughout the course of any given game. This is regardless of how many GIs you may have started with or obtain through other means. Once you have personally built |<tt>BuildLimit</tt>| instances of a unit, that unit's build icon will disappear from the sidebar until the next campaign or skirmish.
  
−
Setting {{TTL|BuildLimit}} to any negative value has a different effect from the normal {{TTL|BuildLimit}} behaviour. The absolute value of the number is used as the build limit, however this is now a limit on the number of times you can actually build the unit yourself. For example, if {{TTL|BuildLimit|-5}} is set on the GI then you will only be able to build 5 GIs throughout the course of any given game. This is regardless of how many GIs you may have started with or obtain through other means. Once you have personally built |<tt>BuildLimit</tt>| instances of a unit, that unit's build icon will disappear from the sidebar until the next game (the limit is per battle, not per {{Ra2}} or {{Yr}} session).
+
==Super Weapons==
  
−
=Super Weapons=
+
Each super weapon type in the game can only be instantiated once per player. If you were to own, say, two Nuclear Missile Silos, you would still only have one Nuclear Missile super weapon available. {{TTL|{{PAGENAME}}}} has no effect on this. Other special-function buildings (such as the Ore Purifier, Industrial Plant and Cloning Vats) ''can '' stack their effects - they simply have {{TTL|{{PAGENAME}}|1}} set for reasons of balance.
  
−
Each super weapon type in the game can only be instantiated once per player. If you were to own, say, two Nuclear Missile Silos, you would still only have one Nuclear Missile super weapon available. {{TTL|BuildLimit}} has no effect on this. Other special-function buildings (such as the Ore Purifier, Industrial Plant and Cloning Vats) ''can '' stack their effects - they simply have {{TTL|BuildLimit|1}} set for reasons of balance.
+
==Bug==
−
 
+
The BuildLimit system was created to allow the inclusion of so-called "hero" units, of which only one is supposed to exist at any given time. As such, the system was only designed to work for {{TTL|{{PAGENAME}}|1}}. Whilst you can set a higher {{TTL|{{PAGENAME}}}}, you will not be able to queue up the entire limit 'in a row' - you will have to queue the last one separately.<br>
−
=Bug=
+
For example, if you had a unit with {{TTL|{{PAGENAME}}|5}}, you would have to either
−
The BuildLimit system was created to allow the inclusion of so-called "hero" units, of which only one is supposed to exist at any given time. As such, the system was only designed to work for {{TTL|BuildLimit|1}}. Whilst you can set a higher {{TTL|BuildLimit}}, you will not be able to queue up the entire limit 'in a row' - you will have to queue the last one separately.<br>
 
−
For example, if you had a unit with {{TTL|BuildLimit|5}}, you would have to either
 
 
*Queue the first 4, build them, and then queue the final one.
 
*Queue the first 4, build them, and then queue the final one.
 
*Queue the first 4, add a different unit to the queue, queue the final one.
 
*Queue the first 4, add a different unit to the queue, queue the final one.
  
−
[[Category:INI Flags]]
+
==Footnotes==
−
[[Category:General Editing Information]]
+
{{fn|1|The comment in {{Rules}}, which states that the default is -1, is incorrect, as is the stated effect of setting {{TTL|{{PAGENAME}}|-1}}.}}
−
[[Category:rules(md).ini Flags]]
 
−
[[Category:InfantryTypes Flags]]
 
−
[[Category:VehicleTypes Flags]]
 
−
[[Category:AircraftTypes Flags]]
 
−
[[Category:BuildingTypes Flags]]
 

Revision as of 17:44, 23 April 2008

Tiberian Dawn The Covert Operations Red Alert Counterstrike Aftermath Tiberian Sun Firestorm HyperPatch Red Alert 2 Yuri's Revenge Ares Generals Zero Hour Tiberium Wars Kane's Wrath
Flag: BuildLimit
File(s): rules(md).ini
Values: Signed integers: All whole numbers from -2147483648 to 2147483647; in rare cases, only from -32768 to 32767.
Special Values: Negative values↓
Default: 21474836471
Applicable to: TechnoTypes:

AircraftTypes, BuildingTypes, InfantryTypes and VehicleTypes



Specifies the maximum instances of a particular unit that any given player may own before they will be prevented from building further instances. Instances of a unit include those that were built by the player, awarded at the start of the campaign or skirmish, awarded via a map trigger, obtained via Cloning Vats, obtained via mutation, or mind-controlled. In the event that a player already owns a number of instances of a unit which is greater than or equal to the unit's Template:TTL, that unit's build icon will be greyed-out and the player restricted from queuing it for construction. However the player is not prevented from obtaining additional instances beyond Template:TTL through any of the aforementioned methods other than normal construction.

Note that AI players are not subject to any unit's Template:TTL. AI players will build whichever units are required by the chosen Template:TTL regardless of how many instances of those units the AI player already owns.

Special Values

Setting Template:TTL to any negative value has a different effect from the normal behaviour. The absolute value of the number is used as the build limit, however this is now a limit on the number of times you can actually build the unit yourself. For example, if Template:TTL is set on the GI then you will only be able to build 5 GIs throughout the course of any given game. This is regardless of how many GIs you may have started with or obtain through other means. Once you have personally built |BuildLimit| instances of a unit, that unit's build icon will disappear from the sidebar until the next campaign or skirmish.

Super Weapons

Each super weapon type in the game can only be instantiated once per player. If you were to own, say, two Nuclear Missile Silos, you would still only have one Nuclear Missile super weapon available. Template:TTL has no effect on this. Other special-function buildings (such as the Ore Purifier, Industrial Plant and Cloning Vats) can stack their effects - they simply have Template:TTL set for reasons of balance.

Bug

The BuildLimit system was created to allow the inclusion of so-called "hero" units, of which only one is supposed to exist at any given time. As such, the system was only designed to work for Template:TTL. Whilst you can set a higher Template:TTL, you will not be able to queue up the entire limit 'in a row' - you will have to queue the last one separately.
For example, if you had a unit with Template:TTL, you would have to either

  • Queue the first 4, build them, and then queue the final one.
  • Queue the first 4, add a different unit to the queue, queue the final one.

Footnotes

1 ↑ The comment in Rules(md).ini, which states that the default is -1, is incorrect, as is the stated effect of setting Template:TTL.

Retrieved from "https://modenc.renegadeprojects.com/index.php?title=BuildLimit&oldid=14922"