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

Difference between revisions of "Armory"

From ModEnc
Jump to: navigation, search
(reworded bugs, added note on cloning)
(Lots more info added)
Line 12: Line 12:
 
}}
 
}}
  
This determines whether the building will automatically promote any infantry that enter it to Elite status. The {{TTL|Ammo}} flag on the building can be used to restrict the number of infantry that can be promoted by this armory. Once it has promoted this number of infantry it is no longer functional. Multiple units can be selected at once and ordered into the armory, this causes them to form a "queue", similar to when multiple units are ordered into a transport, and wait for the people ahead of them to finish in the armory before entering.
+
This flag determines whether the building will automatically promote any [[InfantryTypes|infantry]] that enter it to Elite [[veterancy]] status.
 +
 
 +
The {{TTL|Ammo}} flag ''must'' be used on an armory, otherwise it can only promote one soldier. It can also be used to restrict the number of infantry that can be promoted. Once it has used up all of its "promotions" it will no longer function as an armory. If no restriction is desired, using a value of <code>999</code> is practical.
 +
 
 +
If an armory has {{TTL|Powered|yes}}, it will still function even in a low-power situation.
 +
 
 +
If an armory is placed offline via an in-game mechanism (like in {{Ts}}), it will ''not'' function.
 +
 
 +
In {{Ra2}}, multiple soldiers can be selected at once and ordered into the armory; forming a queue line similar to the way multiple units enter a transport when ordered simultaneously. This makes promoting your soldiers a much less arduous task than it was in Tiberian Sun, where each soldier would have to be ordered into the armory separately.
 +
 
 +
 
  
 
==Bugs==
 
==Bugs==
When an infantry unit enters an Armory it dissappears and reappears a short time later in the upper left corner of the building. Unfortuantely, the unit does not move away from the building when it exits. The unit is partially obscured by the building and can be difficult to mouse-over the correct part of the screen in order to click to select the unit and move it away manually.
+
 
Units that have just exited the building will also block other units from being ordered to enter until the offending unit is moved away (however if units are already queuing for the building (see above) then the next unit in the queue will enter automatically as soon as the unit ahead of it is moved out of the way).
+
===Conyard Armory: Just Don't===
By making the Armory a {{TTL|Factory|InfantryType}} you are able to set a rally point in order to avoid the above problem, however doing so will cause any [[BuildingTypes]] you have with {{TTL|Cloning|yes}} set to spawn a copy of the newly-promoted unit (unpromtoed of course) as if you had just trained it.
+
Applying <code>Armory=yes</code> to a construction yard ({{TTL|ConstructionYard|yes}}) causes glitchy behavior. When sending an infantry unit in to be promoted, the building will cycle through its image frames rapidly and the unit will never come back out.
 +
 
 +
 
 +
 
 +
===Blocked Armory (RA2)===
 +
When an infantry unit enters an Armory it disappears and reappears a short time later in the upper left corner of the building. Unfortunately, the unit does not move away from the building when it exits. The unit is partially obscured by the building and can be difficult to mouse-over the correct part of the screen in order to click to select the unit and move it away manually.
 +
Units that have just exited the building will also block other units from being ordered to enter until the offending unit is moved away. However if units are already queuing for the building (see above) then the next unit in the queue will enter automatically as soon as the unit ahead of it is moved out of the way).
 +
===Partial Fix Accompanied by Cloning Bug (RA2)===
 +
By making the Armory a barracks ({{TTL|Factory|InfantryType}}) you are able to set a rally point in order to avoid the above problem, however doing so will cause any [[BuildingTypes]] you have with {{TTL|Cloning|yes}} set to spawn a copy of the newly-promoted unit (not promoted of course) as if you had just trained it.
 +
 
 +
 
 +
 
 +
===Screwy AI with Armory Barracks (TS)===
 +
If a barracks that the AI builds is given {{tt|Armory{{equal}}yes}}, it somehow screws up the AI by causing them to choose one type of infantry that they can train and mass produce it (non-stop).
 +
===Armory Barracks Jackpot IE of Death (TS)===
 +
Not only is the aforementioned AI bug a concern, but using a combination armory barracks has other complications as well &mdash; dire complications. If a player attempts to train infantry while promoting on the same building, there is a rare chance that both soldiers will try to exit the building at the same moment. This causes an [[IE]] '''(debug code needed)'''.
 +
 
 +
__NOTOC__

Revision as of 07:19, 15 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: Armory
File(s): Rules(md).ini
Values: Boolean values: yes or no, true or false, 1 or 0
Default: no
Applicable to: BuildingTypes


This flag determines whether the building will automatically promote any infantry that enter it to Elite veterancy status.

The Template:TTL flag must be used on an armory, otherwise it can only promote one soldier. It can also be used to restrict the number of infantry that can be promoted. Once it has used up all of its "promotions" it will no longer function as an armory. If no restriction is desired, using a value of 999 is practical.

If an armory has Template:TTL, it will still function even in a low-power situation.

If an armory is placed offline via an in-game mechanism (like in Tiberian Sun), it will not function.

In Red Alert 2, multiple soldiers can be selected at once and ordered into the armory; forming a queue line similar to the way multiple units enter a transport when ordered simultaneously. This makes promoting your soldiers a much less arduous task than it was in Tiberian Sun, where each soldier would have to be ordered into the armory separately.


Bugs

Conyard Armory: Just Don't

Applying Armory=yes to a construction yard (Template:TTL) causes glitchy behavior. When sending an infantry unit in to be promoted, the building will cycle through its image frames rapidly and the unit will never come back out.


Blocked Armory (RA2)

When an infantry unit enters an Armory it disappears and reappears a short time later in the upper left corner of the building. Unfortunately, the unit does not move away from the building when it exits. The unit is partially obscured by the building and can be difficult to mouse-over the correct part of the screen in order to click to select the unit and move it away manually. Units that have just exited the building will also block other units from being ordered to enter until the offending unit is moved away. However if units are already queuing for the building (see above) then the next unit in the queue will enter automatically as soon as the unit ahead of it is moved out of the way).

Partial Fix Accompanied by Cloning Bug (RA2)

By making the Armory a barracks (Template:TTL) you are able to set a rally point in order to avoid the above problem, however doing so will cause any BuildingTypes you have with Template:TTL set to spawn a copy of the newly-promoted unit (not promoted of course) as if you had just trained it.


Screwy AI with Armory Barracks (TS)

If a barracks that the AI builds is given Armory=yes, it somehow screws up the AI by causing them to choose one type of infantry that they can train and mass produce it (non-stop).

Armory Barracks Jackpot IE of Death (TS)

Not only is the aforementioned AI bug a concern, but using a combination armory barracks has other complications as well — dire complications. If a player attempts to train infantry while promoting on the same building, there is a rare chance that both soldiers will try to exit the building at the same moment. This causes an IE (debug code needed).