ModEnc² - User contributions [en]

BalloonHoverHeight

2025-08-10T10:32:43Z

Rain-Islet: Replaced content with "{{del}}"

BalloonHoverDampen

2025-08-10T10:32:42Z

Rain-Islet: Replaced content with "{{del}}"

BalloonHoverBob

2025-08-10T10:32:42Z

Rain-Islet: Replaced content with "{{del}}"

BalloonHoverBoost

2025-08-10T10:32:41Z

Rain-Islet: Replaced content with "{{del}}"

BalloonHoverAcceleration

2025-08-10T10:32:41Z

Rain-Islet: Replaced content with "{{del}}"

BalloonHoverBrake

2025-08-10T10:32:40Z

Rain-Islet: Replaced content with "{{del}}"

ASW

2025-08-10T10:32:40Z

Rain-Islet: Replaced content with "{{del}}"

PreventAutoDeploy

2025-08-10T10:30:04Z

Rain-Islet: non-existent flag

PrismSupportModifier

2025-07-02T16:07:24Z

Rain-Islet:

{{flag
|values={{Values|floats}}
|default=100.0 (broken, see [[#Bugs|{{arr|d}} below]])
|types={{Categ|General}}
|ra2=yes
|yr=yes
|rp=yes
}}

This flag specifies a multiplier to damage when a building designated as {{f|PrismType|link}} fires its weapon supported by other buildings of the same type.

Actual damage done by a linked PrismType is calculated like this:

// naming: ''PSM.ini'' - the value specified for this flag in the rules.ini file
// DamageMultiplier is 1.0 on normal projectiles

Projectile->DamageMultiplier = ( ( (NumberOfSupportingPrisms * (''PSM.ini'' * 100) + 100) * 256 ) / 100 ) / 256;


=={{Bugs}}==
This flag is parsed in an incorrect way: after reading its value from the INI file, it's multiplied by 100 before being saved internally. Due to the fact that the ini parser reads each flag in {{sl|General}} whenever the {{Tt|[General]}} section is present in the file, and if it can't interpret the flag's value properly (say, the flag was not redeclared), it falls back to the value the flag already has. Which means, if the {{Tt|[General]}} section is present in the mpmode file/map, but this flag is not, then its value is multiplied by 100 ''again'' for each such case. Which results in a severely overpowered weapon.

[[Category:Resetting Flags]]

ZAdjust

2025-07-02T16:06:53Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Art(md).ini}}
|values={{Values|int}}
|default=0
|types=[[Animation|Animations]]
|ra2=yes
|yr=yes
|ares=yes
}}
This flag adjusts the animation's location on the Z-axis (depth), measured in [[leptons]]. Positive values move the animation "away from the screen" or "closer to the ground". Negative values do the opposite.

Adjusting the Z-offset is useful for rendering the animation behind or in front of other animations or objects.
==Note==
*Images in the [[ Particles]] section will not read this tag. Although the Image in the section [[Animations]] will have this tag.
=={{Bugs}}==
[[ZAdjust]] affects [[Animations]] of [[Anim]] sets under [[Primary]] or [[Secondary]] including [[Weapon]]. 
by larger values '''(ZAdjust=100,ZAdjust=1000,ZAdjust=10000)''', This will make [[Animations]] scroll down continuously '''(only some parts are visible)'''

*Note: Only [[BuildingType]], [[TerrainType]], [[OverlayType]], and Tile have ZAadjust. 
The ZAadjust of other objects is only used to compare levels with these contents. 
That is to say, there is no difference between two animations that use different ZAadjust. YSort controls their order, not ZAadjust.

[[OverlayTypes]] does not read or use their {{tt|ZAdjust}} flag, even though they actually have Z-depth.
*This bug has been fixed in Phobos Build#44.
==See also==
* [[NormalZAdjust]] – equivalent flag for [[BuildingTypes]]
* [[ActiveAnimZAdjust]] – equivalent flag for [[BuildingTypes]]'s [[ActiveAnim|ActiveAnims]]
* [[YSortAdjust]]
*The spatial coordinate relationship of ZAdjust
Here is a cross-sectional view parallel to the ground plane, equivalent to a perspective from southwest to northeast in the game (or from left to right for the screen):
*https://bbs.ra2diy.com/forum.php?mod=viewthread&tid=24951

YSortAdjust

2025-07-02T16:06:43Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Art(md).ini}}
|values={{Values|int}}
|default=0
|types=[[Animations]]
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

Defines the adjustment, in leptons, to apply when sorting this [[animation]] object in its [[layer]]. In most cases, this affects how the animation is drawn relative to other objects on the same layer. By default, objects are sorted based on the sum of their X and Y coordinates, on which {{f|{{PAGENAME}}}} is directly applied. Therefore, negative numbers sort the animation behind and positive numbers sort the animation in front of other objects.
==Note==
*Images in the [[ Particles]] section will not read this tag. Although the Image in the section [[Animations]] will have this tag.
=={{Bugs}}==
*{{f|{{PAGENAME}}}} only works on the ground [[layer]].

==See also==
* [[ZAdjust]]
* [[ActiveAnimYSort]]
* [[PowerUpXYSort]]

Webby

2025-07-02T16:05:42Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values={{values|boolean}}
|default=no
|types={{Categ|Warheads}}
|fs=yes
|hp=yes
}}

Specifies if this [[Warheads|warhead]] will capture [[InfantryTypes|infantry]] into sticky webs. Infantry [[WebRadius|caught within the radius of the warhead]] cannot move for the [[WebDuration|duration of the effect]].

==See Also==
*[[WebDuration]] - How long the web lasts
*[[WebDurationVariation]] - Random variance to the duration
*[[WebRadius]] - Specifies the area of effect
*[[IsWebImmune]] - Prevents infantry from being webbed

=={{Bugs}}==

If specific conditions are met, infantry will get stuck in an endless web sequence: The target must have both {{f|Fearless|yes|link}} and a healing weapon (one that deals positive [[damage]]).

WeaponsFactory

2025-07-02T16:05:32Z

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

{{Flag
|files={{Categ|rules(md).ini}}
|default=no
|values={{values|boolean}}
|types={{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}
The presence of <tt>WeaponsFactory=yes</tt> on a [[BuildingTypes|building]] turns it into a 'War Factory' with specific logic attached, and includes it in building ratio calculations: see [[WarRatio]].

One feature of such a building, is that it produces [[VehicleTypes]], which exit from a specific cell inside the building (based on foundation shape), either through a door for ground units, or through the roof for [[Jumpjet]] vehicles. Vehicles with {{f|Naval|yes|link}} can't be produced here, nor can [[InfantryTypes|infantry]].

=={{bugs}}==
Adding <tt>WeaponsFactory=yes</tt> to other production buildings, or buildings with [[Dock|docks]] may cause crashing, or break functionality.

==See Also==
[[Naval]]

[[ConstructionYard]]

[[RoofDeployingAnim]]

WeaponXTurretLocked

2025-07-02T16:05:22Z

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

{{Flag
|files={{Categ|ini=art}}
|values={{values|Booleans}}
|default=no
|types={{Categ|VehicleTypes}}
|yr=yes
|ra2=yes
|ts=yes
|fs=yes
}}
Can set will this vehicle lock the direction of the turret during firing and not turn to the direction of the target.

Correspondingly, since the turret direction is not towards the target, if the weapon is not set to '''[[OmniFire]]=true''', it will only be able to fire directly in front of itself.

=={{Bugs}}==

For vehicle that use [[IsGattling]] like Gattling Tank in [[YR]], although they also follow the above rules, their weapons will remain in the firing state (even if they are not actually fired) and will normally follow [[RateUp]] to increase the [[WeaponStages]] and play [[Report]] from Weapon's set of different stages.

*And when vehicle is reassigned to the direction it is facing, it will also use weapons from the new stage normally.

It is likely that Westwood did not use this logic at all, so it did not consider this new weapon system added in YR.

==Note==
Only [[WeaponXTurretLocked]] without Primary or Secondary TurretLocked.

WeaponX

2025-07-02T16:05:12Z

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

{{Flag
|files={{Categ|ini=rules}}
|values={{Values|uint}}
|default=0
|types={{Categ|VehicleTypes}}
|ra2=yes
|yr=yes
}}
This tag forms part of the turret changing logic {{ra2}}, either as part of {{f|IsChargeTurret|yes|link}} as in the case of the Prism Tank, or as part of the IFV passenger-based turret logic using {{f|Gunner|yes|link}}. It is also used by the Gattling tank weapon spooling system added in {{yr}}.

==IFV Logic==
Weapon number 'X' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'X', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.

There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], each with its own weapon. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.

Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.

{{HorizontalBar|[[Image:Cc_documentinfo.png‎|24px]] In YR there is a similar but unrelated [[OpenTopped]] logic, where infantry specify their [[OpenTransportWeapon]] instead.}}

==Charge Turret Logic==
This use of {{tt|WeaponX}} is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.

Charge turret logic also works backwards, and should be considered more like a recoil or cooldown animation, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.

==Gattling Logic==
Every two {{tt|WeaponX}} will form a group to handle the AG and AA tasks in each phase of Gattling. For specific operational details, please refer to [[IsGattling]].

=={{Bugs}}==
In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.
*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html

==See Also==
[[IFV Weapon System]]

WeaponCount

2025-07-02T16:05:02Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=unsigned integers, (0 to 18)
|default=uninitialized (see below)
|types={{Categ|InfantryTypes}},{{Categ|VehicleTypes}},{{Categ|BuildingTypes}}
|ra2=yes
|yr=yes
|rp=yes
}}
Specifies the amount of weapons this object has. Used for special weapon systems, for example, turret-changers ({{f|Gunner|yes|link}}), charge turrets ({{f|IsChargeTurret|yes|link}}), or gattling logic ({{f|IsGattling|yes|link}}).

In those cases, the game parses weapons specified by {{Tt|(Elite)Weapon''%d''=}} , where ''%d'' represents the number between 1 and {{f|WeaponCount}}, as opposed to {{Tt|(Elite)Primary/Secondary}} it loads normally. Then, {{Tt|(Elite)Weapon1}} is used as the default weapon instead of {{Tt|Primary}}.

Values larger than {{tt|18}} are not allowed and will corrupt memory.

=={{Bugs}}==
The game does not initialize this to a constant value. If this tag is not defined, random garbage in memory is used as weapon count, which can lead to desyncs, crashes during loading time, or -- in the worst case -- appear to be working. If {{f|TurretCount}} is greater than {{tt|0}}, set this value, too.

Wall

2025-07-02T16:04:25Z

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

==Buildings==
{{Flag
|values={{Values|bool}}
|default=no
|types={{Categ|BuildingTypes}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
This flag determines whether or not a [[BuildingTypes|building]] should have special wall construction logic, which will convert it to [[OverlayTypes|overlay object]] when it is created.

In order for this logic to work as desired—and ''not'' throw an [[IE]]—it is necessary for the building's corresponding {{art}} entry to have {{f|ToOverlay|link}} set to a valid overlay object with {{f|Wall|yes|link}}{{sup|[[#Overlay objects|{{arr|d}}]]}}. It is not necessary for the overlay object to share the same object name as the building, though doing so is certainly an acceptable shortcut.

As a special case, {{f|GuardRange|link}} can be used to facilitate faster wall construction.

==See Also==
{{f|FirestormWall|link}}

{{f|LaserFencePost|link}}

{{f|GuardRange|link}}

==Overlays==
{{Flag
|values={{Values|bool}}
|default=no
|types={{Categ|OverlayTypes}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
This flag determines whether or not an [[OverlayTypes|overlay object]] should have special logic classifying it as a wall.

An overlay object with {{f|Wall|yes}} and can be damaged by [[Warheads|warheads]] in the following ways:
{| cellpadding="4" class="table_descrow"
!Flag on warhead
!Result on overlay object
|-
|{{f|Wood|yes|link}}
|Damage, but only if overlay object has {{f|Armor|wood|link}}
|-
|{{f|Wall|yes}}{{sup|[[#Warheads|{{arr|d}}]]}}
|Damage, regardless of {{f|Armor}}
|-
|{{f|WallAbsoluteDestroyer|yes|link}}
|Instant destruction, regardless of the damage dealt
|}
Combinations of these flags results in the most inclusive case.

=={{bugs}}==
Although wall overlay can use [[remap]], such overlay are always rendered in the [[Houses|house]] color of the current player, instead of using the color of the player who built it.
*For {{yr}}, this is fixed in [https://ares-developers.github.io/Ares-docs/bugfixes/type2/remappablewalls.html Ares version 0.2].

==Warheads==
{{Flag
|values={{Values|bool}}
|default=no
|types={{Categ|Warheads}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This flag determines whether or not a [[Warheads|warhead]] can inflict damage on [[OverlayTypes|overlay objects]] with {{f|Wall|yes}}{{sup|[[#Overlay objects|{{arr|u}}]]}} as well as bridges (provided that {{sl|SpecialFlags|DestroyableBridges|yes}}) and ice.

==See Also==
{{f|Wood|link}}

{{f|WallAbsoluteDestroyer|link}}

[[Category:Bugs and Errors]]

WalkRate

2025-07-02T16:04:15Z

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

{{Flag
|name=WalkRate
|files={{Categ|ini=rules}}.
|values={{Values|uint|1 or higher}}
|default=1
|types={{Categ|TechnoTypes}}
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
Specifies the animation rate for moving units and defines after how many frames the animation advances to the next frame. Larger values mean slower playback. Can be specified for both SHP based and voxel based units.

The animation also plays with this rate when a {{f|HoverAttack|link}} VehicleType has a target and it isn't deployed.

The animation does not play in case the unit is warping in from a chrono-move or being warped out by {{f|Temporal|link}} weapons, or when attacked by {{f|IsLocomotor|link}} weapons.

=={{Bugs}}==
{{f|WalkRate}} cannot be {{tt|0}} or lower. If {{f|WalkRate|0}} you will get an [[IE|internal error]]: [[Internal_Error#eip_004C931E|EIP 004C931E]] in RA2, [[Internal_Error#eip_004DA90E|EIP 004DA90E]] in YR.

VoxelBarrelOffsetToBarrelEnd

2025-07-02T16:03:56Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|ini=rules}}
|types={{Categ|BuildingTypes}}
|values=F,L,H; {{Values|signed integers}}
|default=0,0,0
|fs=yes
|ra2=yes
|yr=yes
}}

Specifies the the end point, in leptons, for this [[BuildingTypes|building's]] [[BarrelAnimIsVoxel|voxel barrel]]. This is the point at the barrel where the actual bullet will exit, along with a [[Anim|muzzle animation]], if any. The offset is measured from the barrel pivot point defined by {{f|VoxelBarrelOffsetToBuildingPivotPoint|link}} and/or {{f|TurretAnimX|link}}/{{f|TurretAnimY|link}}).

This offset is expressed in F,L,H (Forward, Lateral, Height) format, with each value moving the barrel end point as follows:

* '''F''': Positive values move the point forward, negative values move the point backward.
* '''L''': Positive values move the point to the left, negative values move the point to the right.
* '''H''': Positive values move the point up, negative values move the point down.

See [[FLH]] for more information.

=={{bugs}}==

Similar to {{f|PrimaryFireFLH|link}}, if the building's weapon has {{f|Burst|2|link}} or higher, the second shot uses a mirror of the lateral offset. However, unlike {{f|PrimaryFireFLH}}, the third and any subsequent burst shots are always fired from the middle. This seems specifically coded with the Juggernaut's triple-barrel configuration in mind.

Also note that, due to using [[BarrelAnimIsVoxel|special voxel barrel logic]], normal firing offset adjustments like {{f|PrimaryFireFLH|link}} and {{f|PBarrelLength|link}} do not apply.

== See Also ==
* [[PrimaryFireFLH]]
* [[PBarrelLength]]
* [[BarrelAnimIsVoxel]]
* [[VoxelBarrelFile]]
* [[VoxelBarrelOffsetToPitchPivotPoint]]
* [[VoxelBarrelOffsetToRotatePivotPoint]]
* [[VoxelBarrelOffsetToBuildingPivotPoint]]
* [[VoxelBarrelScale]]

Veterancy

2025-07-02T16:03:25Z

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

{{Guideheader
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
Veterancy is the term used to describe unit promotion. By default there are two such levels, the first being 'veteran' followed by 'elite'. Units attain promotions by destroying objects, until the cumulative unit cost of destroyed enemies exceeds the units own [[Cost]] multiplied by [[VeteranRatio]].
 
Each promotion level reached modifies the properties of the unit, according to the following multipliers found under the [General] section:
*[[VeteranCombat]]
*[[VeteranSpeed]]
*[[VeteranSight]]
*[[VeteranArmor]]
*[[VeteranROF]]
*[[VeteranCap]]
==In {{ra2}}==
When a unit reaches its full promotion to 'elite', the unit will switch to use [[ElitePrimary]] and [[EliteSecondary]] weapons if it has them. If only one of those is present, the main [[Primary]] or [[Secondary]] weapon will be used for the other. The above multipliers will then cumulatively increase the effectiveness of the weapon upgrade, potentially making 'elite' level vehicles quite fearsome.

When achieving the first level of promotion, a sound effect defined by [[UpgradeVeteranSound]] will play, and upon the second level promotion [[UpgradeEliteSound]] will play instead. However in RA2/YR at least, the sound effect used by default is the same for both, unless substituted by a mod.

The unit will also flash brightly when promoted to 'elite' for a number of frames specified by [[EliteFlashTimer]] in [AudioVisual].
 
==In {{yr}}==
Unlike in base RA2, units can gain experience towards their promotion for their kills, while garrisoned. [[InfantryTypes|Infantry]] will accumulate points towards that promotion, but they will be held in reserve until the unit evacuates (un-garrisons) the building, only then will they receive the promotion they earned.
 
==Gaining New Abilities==
When promoted from base to 'veteran' level, a unit is also granted a list of explicit abilities defined by the [[VeteranAbilities]] list, if present in the unit code. For the second stage promotion it will gain what's in [[EliteAbilities]]. The following abilities can be specified:
*FASTER (speed multiplier)
*STRONGER (armor multiplier)
*FIREPOWER (damage multiplier)
*ROF (fire rate multiplier)
*CRUSHER (adds crushing ability regardless of [[SpeedType]])
*C4 (receives C4 planting ability, if weapon arrangement allows it)
*SCATTER (auto-scatter when attacked by vehicles with [[StupidHunt]] or [[AutoCrush]])
*GUARD_AREA (equivalent to [[DefaultToGuardArea]])
*SIGHT (sight range multiplier)
*SELF_HEAL (equivalent to [[SelfHealing]])
*FEARLESS (Infantry will not go prone when attacked)
*EXPLODES (Infantry will not use normal death [[Sequence]])
*RADAR_INVISIBLE (mini-map will not show unit to enemies)
*CLOAK (equivalent to [[Cloakable]])
*SENSORS (reveals cloaked units nearby)
*TIBERIUM_HEAL (used by Harvesters to regain health while on [[Tiberiums]])
*TIBERIUM_PROOF (won't take damage on Tiberium, irrelevant in RA2)
*VEIN_PROOF (won't take damage on Weeds, irrelevant in RA2)
=={{bugs}}==
<tt>VeteranAbilities</tt> and <tt>EliteAbilities</tt> don't stack, that is when promoted to 'elite' the unit will gain only new traits specified in <tt>EliteAbilities</tt>, not double the effect of traits duplicated in <tt>VeteranAbilities</tt>.

VeteranUnits

2025-07-02T16:03:15Z

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

{{Flag
|name=VeteranUnits
|files={{Categ|Rules(md).ini}}
|values=Comma-separated list of strings
|default=None
|types={{Categ|Countries}}
|ra2=yes
|yr=yes
|rp=yes
}}
This tag is used to list both land vehicles and ships that can be built and start the game as veterans by certain countries. The tag should be included under the relevant country header in the [[Country Statistics]] section i.e. 
'''[British]''' 
'''VeteranUnits=MTNK,BFRT,DEST''' 
The units listed must also be listed under the [{{f|VehicleTypes|link}}] list and should be owned by the country in question to prevent possible errors. 

=={{Bugs}}==
*'''Slave Miner''' produced by '''War Factory''' is affected by the tag. '''VeteranUnits''' but '''Slave Miner''' that come directly from build ([[BuildingTypes]]) are not affected by the tag. '''VeteranUnits'''

VeteranROF

2025-07-02T16:03:05Z

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

{{Flag
|name=VeteranROF
|files={{Categ|Rules(md).ini}}
|values={{values|float}}
|default=1.0
|types={{Categ|General}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This is one of the several veteran factors that control the bonuses given by {{f|VeteranAbilities|link}} and {{f|EliteAbilities|link}}. {{f|VeteranROF}} alters the {{f|ROF|link}} of the {{f|Primary|link}} and {{f|Secondary|link}}, and (in case of {{f|EliteAbilities{{equal}}ROF}}) {{f|Elite|link}} [[weapon]]s of units that benefit from the {{tt|ROF}} promotional bonus. Contrary to popular belief, these bonuses do ''not'' stack, meaning that a {{tt|ROF}} elite bonus will '''not''' further modify the rate of fire of a unit with a {{tt|ROF}} veteran bonus.

==In {{ts}} and {{fs}}==

{{f|VeteranROF}} acts as a divisor to {{f|ROF|link}}:
: [New ROF] = ROF / (1.0 + VeteranROF)'''

'''Example:''' if the weapon's {{tt|ROF}} is 30, then it would be decreased to 25 (assuming {{tt|VeteranROF{{Equal}}0.2}}).
: '''30 / (1.0 + 0.2) = 25'''

==In {{ra2}} and {{yr}}==
Like most of the other veteran factors, {{f|VeteranROF}} has been simplified; it is now a straight multiplier to {{f|ROF|link}}.

'''Example:''' if the weapon's {{tt|ROF}} is 20, then it would be decreased to 12 (assuming {{tt|VeteranROF{{Equal}}0.6}}).
: '''20 * 0.6 = 12.'''

'''Note:''' Since {{tt|ROF}} is really the delay between shots, smaller numbers yield faster firing. Values of {{tt|VeteranROF}} greater than 1.0 actually ''decrease'' the firing rate of the unit.

=={{Bugs}}==

{{f|VeteranROF}} has no effect if the weapon uses a [[IsSonic|sonic wave]] or has an [[AttachedParticleSystem|attached particle system]].

VeteranCombat

2025-07-02T16:02:55Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|ini=Rules}}
|values={{values|float}}
|default=1.0
|types={{Categ|General}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This is one of the several Veteran Factors that control the bonuses given by {{f|VeteranAbilities|link}} and {{f|EliteAbilities|link}}.

Contrary to popular belief, these bonuses do ''not'' stack, meaning that a {{tt|FIREPOWER}} elite bonus will '''not''' further increase the damage dealt by a unit with a {{tt|FIREPOWER}} veteran bonus.

==In {{ts}}==
{{tt|VeteranCombat}} is an additive multiplier to [[damage]] dealt by the object's [[Primary]], [[Secondary]], and, in case of {{f|EliteAbilities{{Equal}}FIREPOWER}}, [[Elite]] weapons.

: Damage * (1.0 + VeteranCombat)

'''Example:''' If the unit's weapon deals 100 base {{f|Damage}}, then the hit would be increased to 125 (assuming {{f|VeteranCombat{{Equal}}0.25}}).
: '''100 * (1.0 + 0.25) = 125'''

==In {{ra2}}==
Similar to TS, except the math has been simplified. {{tt|VeteranCombat}} is now a direct multiplier to the base {{f|Damage}} inflicted by the [[weapon]](s) of objects that benefit from the {{tt|FIREPOWER}} promotional bonus.

'''Example:''' If the unit's weapon deals 100 base {{f|Damage}}, then the hit would be increased to 110 (assuming {{f|VeteranCombat{{Equal}}1.1}}).
: '''100 * 1.1 = 110'''

=={{bugs}}==
{{tt|VeteranCombat}} has no effect if the weapon uses a [[IsSonic|sonic wave]].

Vertical

2025-07-02T16:02:45Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values={{Values|bool}}
|default=no
|types={{categ|Projectile}}
|ra2=yes
|yr=yes
}}
Can be set to ''' 'yes' ''' or ''' 'no' ''' and specifies that this projectile travels in a straight vertical line, up or down. This tag also requires a {{Tt|[[DetonationAltitude]]}} to be set on any projectile it is used on.

Such projectiles are meant to function as falling bombs and for the special case of the [[Type|Nuke]]'s upwards/downwards-going missiles. When fired by other weapons, such projectiles will, ironically, fly ''horizontally'' in the direction of the firer. In this case, they will never detonate, unless compelled to do so by other means, such as terrain collision or [[ProjectileRange]] (in Ares), and never hit their target if it is at a different altitude, flying in a straight line until they leave the map. However, they will not always hit their intended target even when facing it and will sometimes fly past it or even through it when fired at certain angles, preventing this from being used to create true horizontal projectiles. Voxel projectiles will also fail to have correct facing when used in this way, although SHPs do not have this issue.

==Notes==
* When combined with a positive {{Tt|[[ROT]]}}, it seems to take precedence over Vertical, turning the projectile into an ordinary homing projectile.
** {{f|ROT|1|link}} needs further investigation.
* When combined with {{Tt|[[Arcing]]}}, unforseen projectile and weapon behaviour results - the projectile will be invisible, no damage will be dealt and the weapon will be unable to fire after a few shots.
** Needs further investigation.
* Vertical projectiles can be used on [[AirburstWeapon]]s as intended, falling downwards from their spawning height with a correct facing.
* Seemingly, buildings cannot fire these projectiles either, although '''1x1''' buildings may be worth trying.
* Setting '''Vertical=no''' on a projectile used by a [[JumpJet]] unit with {{f|BalloonHover|yes|link}} will prevent it from trying to hover directly over its target, even though it's in range.
* If the weapon is launched by an [[AircraftTypes]], it will have a "solid impact" effect, not just for the terrain collisional.

=={{Bugs}}==
*If [[Projectile]] has {{f|AG|no|link}} you will get [[IE]] (for [[YR]] {{f|IE|007564B4|link}}).

==See Also==
[[Acceleration]] 
[[CourseLockDuration]] 
[[DetonationAltitude]] 
[[Level]] 
[[Dropping]]

UseSparkParticles

2025-07-02T16:02:02Z

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

Setting this to "yes" will make the weapon look for and use the particle system listed in [[AttachedParticleSystem]]= when firing. The effect is indistinguishable from [[IsRailgun]]=true and is not limited to spark particles. The effect of the tag depends on the listed ParticleSystem's [[BehavesLike]]= entry; =Spark type entries along with =Smoke types will be drawn at the weapon's [[PrimaryFireFLH]]=, =Railgun type entries will be drawn from the firing point to the target, and =FireStream types will likewise be drawn from firer to target. =Gas type is untested.

The firing weapon will be unable to fire again until the particle system has finished and despawned.

=={{Bugs}}==
When using Burst= weapons along with an offset FireFLH (a twin barrel tank, for example), the particle system will be spawned at the point opposite to the firing weapon's FireFLH

==See also==
[[IsRailgun]]

UseFireParticles

2025-07-02T16:01:52Z

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

{{DeeZireInclusion}} 
Can be set to 'yes' or 'no' and specifies that the weapon uses a 'fire' type particle system - one which is drawn horizontally along the projectile path.
=={{Bugs}}==
*The UseFireParticles tag causes the {{f|DirectRocker|yes|Link}} tag to not work properly. ([[VehicleTypes]] Most will not tip over).

UnloadingClass

2025-07-02T16:01:34Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|ini=rules}}
|types={{Categ|VehicleTypes}}
|values={{Values|Strings|VehicleTypes}}
|default=none
|ra2=yes
|yr=yes
}}
Specifies the vehicle that this unit should turn into when performing a special function. The unit doesn't actually turn into another vehicle, though, and usually only the [[Image]] value is read. The default value 'none' means that the original unit's image will be used. 
[[VehicleTypes]] that are contained within '''UnloadingClass''' can have {{f|Turret|yes|link}} and {{f|TurretSpins|yes|Link}}(But [[ROT]] is based on the default [[VehicleTypes]] only). 

The [[TurretRotateSound]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|Turret|yes|link}}. 

The [[NoShadow]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|NoShadow|yes|link}}. 

The [[FireAngle]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|FireAngle|x|link}}. 

The [[WalkRate]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|WalkRate|x|link}}. 

The [[IdleRate]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|IdleRate|x|link}}. 

The [[ZFudgeTunnel]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|ZFudgeTunnel|x|link}}. 

The [[ZFudgeColumn]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|ZFudgeColumn|x|link}}. 

The [[ZFudgeBridge]] tag also affects [[VehicleTypes]] that are contained within '''UnloadingClass''' if the [[VehicleTypes]] That invokes the {{f| IsSimpleDeployer|yes|link}} tag to have {{f|ZFudgeBridge|x|link}}. 

== Notes ==
Although this tag is parsed for all [[TechnoTypes]], the logic works only for [[VehicleTypes]] that make use of [[Dock]] and [[IsSimpleDeployer]].

=={{Bugs}}==
*[[VehicleTypes]] Types [[Voxel]] That uses the {{f|IsSimpleDeployer|yes|link}} tag cannot determine '''UnloadingClass=[[VehicleTypes]] SHP'''. (but I found a way to make it work[testid123])

UnitRepair

2025-07-02T16:01:24Z

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

{{flag
|values={{values|boolean}}
|types={{Categ|BuildingTypes}}
|default=no
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
|ares=yes
}}
If set to yes, [[VehicleTypes]] are able to dock with this structure and get repaired. Repair rate and cost is determined by the {{sl|General|URepairRate}} and {{sl|General|RepairStep}} flags. 
For [[YR]], if you use this tag on '''Bio Reactor''', it will allow [[InfantryTypes]] to enter '''Bio Reactor''' only if it receives the damage.
=={{bugs}}==
*In unmodded RA2 and YR, this flag is commented out from the entries for the Allied Airforce Command Center and its American equivalent, along with a comment '';gs this is part of reloading + being an aircraft (Repair code is oogly, only Reload got rewritten for four ports.)''. 
*The comment fails to mention any bugs, but reenabling it on such a structure will have adverse side-effects and even '''cause an [[Internal Error]]''' - when an AI's unit is damaged, it will attempt to find the closest structure it has with this flag enabled (regardless of whether the unit can actually enter it), and send the unit there for repairs. If that destination structure happens to be an airpad, the game will enter an infinite loop and crash. 
*In addition to this, even aircraft that can legitimately land in this structure will trigger its repair loop after landing, and this loop will kick them off once they're fully repaired, meaning that an aircraft sent to dock with such a structure will never manage to do it. 
*It's funny for [[TS]],[[FS]],Ra2 if [[BuildingTypes]] has a UnitRepair=yes tag (with no other tags associated with and UnitRepair=yes) Will prevent [[VehicleTypes]] on the ground from attacking [[BuildingTypes]] with the {{f|UnitRepair|yes|Link}} tag. ([[VehicleTypes]] with tag {{f|BalloonHover|yes|link}}+{{f|Naval|yes|link}} is still allowed to attack normally) 
*For YR [[VehicleTypes]] that uses vertical weapons Vertical(See Also {{f|Vertical|yes|link}}), If it is controlled by the player Those [[VehicleTypes]] cannot attack [[BuildingTypes]] with UnitRepair=yes tags. 
== Other notes ==
The AI is extremely dumb about using repair bays of any kind - it will blindly send Kirovs and Siege Choppers there despite the fact that they can never actually get repaired, and it will not differentiate between a land-based and water-based repair bay when a unit can reach both (e.g. Robot Tank). In some cases, a non Naval unit will enter a Shipyard for repairs, but the Shipyard will not repair it. So, it would be wise not to give the AI any repair bays.

UnitAbsorb

2025-07-02T16:01:14Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values={{Values|boolean}}
|default=no
|types={{Categ|BuildingTypes}}
|yr=yes
|ares=yes
}}
{{f|UnitAbsorb}} is an unused yet functional feature in [[YR]]. Similar to {{f|InfantryAbsorb|link}}, it lets [[VehicleTypes|vehicles]] enter the building (e.g. bio reactor) in order to generate extra [[power]].

=={{Bugs}}==
*Setting '''UnitAbsorb=no''' (without tag {{f|PipScale|Passengers|link}},[[Passengers]],[[SizeLimit]]) give to a '''Refinery''' building type will cause the [[VehicleTypes]] to be connected to this building (with the tag {{f|Dock||link}}) cannot be connected.
*Setting '''UnitAbsorb=yes''' (without tag {{f|PipScale|Passengers|link}},[[Passengers]],[[SizeLimit]]) give to a '''Refinery''' building type will cause the [[VehicleTypes]] to be connected to this building (with the tag {{f|Dock||link}}) has strange behavior, When connected to the said building. [[File:UnitAbsorb=yes and Ore Refinery.gif]] '''UnitAbsorb=yes and Ore Refinery''' 

== See Also ==
* [[InfantryAbsorb]]

Underwater

2025-07-02T16:01:04Z

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

{{Flag
|name=Underwater
|files={{Categ|Rules(md).ini}}
|values=boolean
|default=no
|types={{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, {{Categ|BuildingTypes}}, {{Categ|Projectiles}}
|ra=yes
|ra2=yes
|yr=yes
|rp=yes
}}

{{tt|Underwater{{Equal}}yes}} has three known effects and one untested effect:
* Primarily, it is used to classify the object as being underwater, for the purposes of the {{f|NavalTargeting|link}} logic.
* It will also stop the object from displaying the {{f|Wake|link}} animation when traveling over water.
* It will disable the "sinking" death logic for the unit, instead displaying explosions
* {{tt|It will also restrict units from recloaking when it is in fact on land.}}

For [[Red Alert]] this is used with [[Projectiles]] which works like a [[Level]] tag (I'm not sure Has it been replaced by a name change?)
=={{Bugs}}==

If you give '''Underwater=yes''' to any building that is in the water Those buildings will suffer the same negative effects as units in water.

'''[GAYAYD]'''

'''Underwater=yes'''

When we force '''Destroyer(DEST)''' to attack the '''Allied Shipyard(GAYARD)'''

'''Destroyer(DEST)''' will attack the '''Allied Shipyard(GAYARD)''' with a secondary weapon([[Secondary]]) instead of the main weapon([[Primary]]).

UndeploysInto

2025-07-02T16:00:54Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=strings (names of [[VehicleTypes]])
|special=none (needs confirmation)
|types={{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}
Specifies the [[VehicleType]] that this BuildingType can undeploy into (you can set which VehicleType deploys into this BuildingType by using the {{f|DeploysInto|link}} flag). This BuildingType's {{f|Buildup|link}} animation is played (in full length, unlike when you sell this building) in reverse direction.

[http://forums.renegadeprojects.com/showthread.php?tid=1219&pid=13563#pid13563 It has been reported] that using <code>UndeploysInto=none</code> results in the object automatically being sold when undeployed.

== Undeployed vehicle facing ==

Mind that if the game doesn't know which direction the VehicleType should be facing when it undeploys, it will undeploy the building without spawning the vehicle. The facing can be specified in the following ways:
{| border=1 class="table_descrow"
! INI Flag || Facing
|-
| {{f|ConstructionYard|yes|link}} [[Image:Warning small.png]] '''Warning:''' Side-effects.|| South-West
|-
| {{f|TickTank|yes|link}} || North-West
|-
| {{f|Artillary|yes|link}} || North-East
|-
| {{f|ICBMLauncher|yes|link}}
| rowspan=2 | North-East
|-
| {{f|SensorArray|yes|link}}
|-
| {{yro}}{{f|DeployFacing|link}}
| rowspan=2 | As set
|-
| {{yro}}{{f|DeployDir|link}}
|}

=={{Bugs}}==
*If [[BuildingTypes]] has UndeploysInto=(name of vehicle) but no {{f|Buildup|(name of animation)|Link}} [[BuildingTypes]] cannot be restored to [[VehicleTypes]]. 
*Even if you specify name [[VehicleTypes]] that do not exist, such as UndeploysInto=AAA
tags UndeploysInto will work as expected, along with [[VehicleTypes]] that do not contain images. There is no information and {{f|Locomotor|{4A582747-9839-11d1-B709-00A024DDAFD1}|Link}}. 
(If you specify the name of [[AircraftTypes]] You must have complete information of specified [[AircraftTypes]] and importantly it will become [[VehicleTypes]] completely even if there is a match, e.g. ORCA) 
*If [[BuildingTypes]] has [[DeploysInto]] and [[UndeploysInto]] [[BuildingTypes]] will not be repairable.
*Using this with construction yardwill cause an error if construction yard does not have {{f|UndeploysInto||link}}{{f|BaseUnit|link}}.
*If you set it like this:
'''[GAPILL]''' 
'''UndeploysInto=GAPILL''' 
And you need to have a [[Voxel]] file named '''GAPILL''' when you undeploy.
You will be presented with [[VehicleTypes]] which has images with but no data whatsoever.
Although '''[GAPILL]''' has information in the [[BuildingTypes]] however

TurretOffset

2025-07-02T16:00:40Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Art(md).ini}}
|values={{Values|integer}}
|default=0
|types={{Categ|TechnoTypes}}
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}
==For VehicleTypes==
TurretOffset provides additional degree of control over [[Voxel Turret and Barrel Positioning|turret/barrel positioning]]. Unlike voxel header editing, which uses voxel blocks as measure units, this tag takes value in [[lepton]]s. It allows you to move the turret "box" forward or backward over the z axis. (And by doing so, it affects the barrel's location on the z-axis the same way.)

- = reverse, + = forward, its actually sensible for once
==For BuildingTypes==
You can use this tag with [[BuildingTypes]] (discovered by testid123) with the following conditions: 
1. You need the files Voxeltur.hva (Turret name must be the same as the Image used with [[BuildingTypes]]) and Voxeltur.vxl (Turret name must be the same as the Image used with [[BuildingTypes]]). 
2.[[Image]] of [[BuildingTypes]] that use the TurretOffset=x tag must have {{f|Voxel|yes|link}} in [[Artmd.ini]];;Yet it still suffers from the side effects of tag errors TurretOffset=x The [[TurretAnim]] of [[BuildingTypes]] changes based on the x value of the tag. TurretOffset [[File:TurretOffset on BuildingTypes.png]]
=={{Bugs}}==
*Changed the basic attack position of any units and buildings. with '''TurretOffset=x'''([[FLH]] position depends on turret?) 
*When the turret position is not at [[VehicleTypes]] Voxel turrets are displayed incorrectly
*Although TurretOffset For Building is effective, only the image offset will follow the direction of the building, and the firing coordinates will not change with the direction, but simply move to a new fixed point that is offset by the amount set by TurretOffset in the east direction of the original fixed point.

TurretCount

2025-07-02T16:00:30Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=unsigned integers
|default=0
|types={{Categ|InfantryTypes}},{{Categ|VehicleTypes}},{{Categ|AircraftTypes}},{{Categ|BuildingTypes}}
|ra2=yes
|yr=yes
|rp=yes
}}
Specifies the amount of turrets this object has. Used for special weapon systems, for example, turret-changers ({{f|Gunner|yes|link}}), charge turrets ({{f|IsChargeTurret|yes|link}}), or gattling logic ({{f|IsGattling|yes|link}}).

In those cases, the game loads files {{Tt|''objectname''tur''%d''.vxl/hva}}, where ''%d'' represents the number between 1 and {{f|TurretCount|link}}, as opposed to plain {{Tt|''objectname''tur.vxl/hva}} it loads normally.

=={{Bugs}}==
When setting {{f|TurretCount}} to a value greater than {{tt|0}}, see that {{f|WeaponCount|link}} is also set correctly. This has to be done because the latter is not initialized to a constant value, and garbage in memory could lead to unexpected results, like corrupting memory. In the best case it crashes when starting a game.

*Allows [[InfantryTypes]] to use Weapons with '''Burst=2''' are possible.

If [[InfantryTypes or AircraftTypes]] has {{f|TurretCount|1|Link}}
{{f|WeaponCount|2|Link}}

[[Weapon1FLH]](in [[Art.ini]] or [[Artmd.ini]])

[[Weapon2FLH]](in [[Art.ini]] or [[Artmd.ini]])

[[EliteWeapon1FLH]](in [[Art.ini]] or [[Artmd.ini]])

[[EliteWeapon2FLH]](in [[Art.ini]] or [[Artmd.ini]])

[E1]

TurretCount=1

WeaponCount=2

Weapon1=AGGattling

EliteWeapon1=AGGattlingE

Weapon2=AAGattling

EliteWeapon2=AAGattlingE

[[File:Burst=2.png]]

And the [[WeaponX]] system initiated in this way can also be used normally in modern engines with [[DeployFireWeapon]] to specify weapons beyond 2.

TurretAnim

2025-07-02T16:00:20Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|ini=rules}}
|types={{Categ|BuildingTypes}}
|default=none
|values={{values|string|[[Animations]]}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
This flag should be set to the [[animation]] to be rendered as a [[turret]] on this [[BuildingTypes|building type]]. The turret animation can be of three types:

== Voxel Turret ==
To render a [[voxel]] turret on a building, simply put the voxel's file name into the {{f|TurretAnim}} input and give the building the additional tag {{f|TurretAnimIsVoxel|true|link}}; the game will render the voxel directly onto the building without a need for a corresponding {{ini|art}} entry.

Through my various tests, I found that Voxel Turret can have more than one turret. [[File:Voxel Turret x2.png]] 
Normally you cannot specify '''TurretAnim=VoxelWO''' is possible, but if you define it like this: It will be available. 
example: 
'''[GAPOWR]''' 
'''{{f|Image|DESTWO|ink}}''' 
'''{{f|Turret|yes|ink}}''' 
'''{{f|TurretAnim|DEST|ink}}''' 
'''{{f|TurretAnimIsVoxel|True|ink}} 
'''...''' 
Results [[File:TurretAnim=DEST.png]] 
If you don't follow the above method. But it's set normally. 
'''[GAPOWR]''' 
'''{{f|Image|DEST|ink}}''' 
'''{{f|Turret|yes|ink}}''' 
'''{{f|TurretAnim|DESTWO|ink}}''' 
'''{{f|TurretAnimIsVoxel|True|ink}}''' 
'''...''' 
It will give results like this [[File:TurretAnim=DESTWO.png]] 

== SHP Turret ==
[[File:Turretrotation.png|thumb|frame|Turret shape orientation should start from the ▲ direction and rotate counter-clockwise, like in this example.]] To render a turret [[SHP|shape]] on a building, list the [[SHP|.shp]] animation entry in the {{f|TurretAnim}} input and see that {{f|TurretAnimIsVoxel|false|link}}; the game will expect that the turret animation has an {{ini|art}} entry. Turret shapes should have 32 frames and can have shadow frames, which unlike .shp-based vehicles turrets, do animate their shadows.

It will also need these: 
{{f|LoopStart|0|link}}
{{f|LoopEnd|32|link}}
{{f|LoopCount|-1|link}}
{{f|Rate|0|link}}

SHP images in TurretAnim can be replaced with other SHP images if the SHP file is specified in the TurretAnim tag. has the tag {{f|Theater|yes|link}} (applies only to theaters where the SHP file has the extension of that theater, such as testtur.tem). 
Normally name of the SHP turret must be specified in the section. [[Animations]] to make it available. 
But if the turret name SHP'''(animation)''' is defined in the [[Trailer]] and [[TrailerAnim]] You do not need to specify Put it in the section [[Animations]] 
example: 
'''[RING1]''' ;Name of Animations in this section must be specified in the section. [[Animations]] also, otherwise doing this would be useless. 
{{f|Trailer|TURSHP|link}} 
{{f|TrailerAnim|TURSHP|link}} 

== Charge Animation ==

Here the turret logic has been "hijacked" for a special purpose. If the building has no turret ({{f|Turret|no|link}}) but has a valid {{f|TurretAnim}} entry and a [[primary]] weapon with {{f|Charges|yes|link}}, then this animation is used for the weapon charge-up animation. When the building acquires a target, this animation will play before the weapon can actually fire. An example of this is the Obelisk of Light in {{ts}}. Use {{f|TurretChargeAnimRate|link}} to specify the animation speed.

=={{Bugs}}==
;Even though the turret voxels cannot have shadows But you can create one fake turret and then lowerits height.
until it is level with the ground And then you adjust it to black. to create fake shadows

[[File:Fake Shadow(Voxel).png]][Fake Shadow(Voxel)] 

==Note==
*Can be replaced with [[VoxelBarrelFile]] (Disable tag "TurretAnim" and use the [[VoxelBarrelFile]] tag instead).

== See Also ==
* [[TurretAnimIsVoxel]]
* [[TurretAnimDamaged]]
* [[TurretAnimX]]
* [[TurretAnimY]]
* [[TurretAnimZAdjust]]
* [[TurretChargeAnimRate]]

Turret

2025-07-02T16:00:10Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=boolean
|default=yes on BuildingTypes, no on other objects
|types={{Categ|VehicleTypes}}, {{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}
Specifies whether this object has a turret.
;On VehicleTypes
:The turret filename has to be the same as the object's, with the suffix {{Tt|tur}}, and be in [[VXL]] format, with an accompanying [[HVA]]. Should [UNIT] have Turret=yes set but no file with the name unittur exist, the game will crash.
;On AircraftTypes
It was hardcoded to not have a turret. Even though there is a tag Turret=yes.
;On BuildingTypes
:The turret filename is specified by {{f|TurretAnim|link}}, should be the same as on VehicleTypes, and its format is specified by {{f|TurretAnimIsVoxel|link}}. If the turret is in [[SHP]] format, it should be defined in art(md).ini and listed in [Animations] in order to be loaded by the game. If the turret is in VXL format, this is not necessary. 
If [[BuildingTypes]] does not have the tag [[TurretAnim]], but has the tag {{f|TurretAnimIsVoxel|yes|link}} and other related tags
([[TurretAnimX]],[[TurretAnimY]],[[TurretAnimZAdjust]]) The game will use the Voxel turret image according to the image of the [[BuildingTypes]] defined, e.g. 
[GAPILL] 
Image=LTNK 
The game uses the image of the Lasher Light Tank's turret instead. 
If you wish to have [[BuildingTypes]] use this [[BuildingTypes]] turret You must meet the following conditions: 
You need the files Voxeltur.hva (Turret name must be the same as the Image used with [[BuildingTypes]]) and Voxeltur.vxl (Turret name must be the same as the Image used with [[BuildingTypes]]) and [[Image]] of [[BuildingTypes]] must have {{f|Voxel|yes|linkl}} in [[Artmd.ini]] 
*for a [[Voxel]] turret. Even though it is a [[Voxel]] file, those [[Voxel]] turrets It's not sloping Along the sloping area.(My opinion: Since [[BuildingTypes]] cannot use [[Locomotor]], it [[BuildingTypes]] cannot tilt along sloped terrain). 
[[File:TurretAnimIsVoxel=True on a sloping area.png]]

=={{Bugs}}==
*I don't know for what reason. This caused the voxel turret to always have no shadows, and Westwood never thought about fixing this problem from [[TS]] until [[RA2]](This issue was fixed in [[Ares]],[[Phobos]]).
*If [[VehicleTypes]] [[SHP]] has Turret=yes there will be a shadow above the ground. When floating above the ground by any means 
*If Buildings that infantry canable occupy '''({{f|CanBeOccupied|yes|Link}})''' have '''{{f|Turret|yes|Link}}''' after infantry leaves the building. Will not be able to go back in again ('''Bio Reactor''' is not affected by this glitch. Instead, the owner of the '''Bio Reactor''' cannot release the [[infantryTypes]] inside). [[File:Bio Reactor and Turret=yes.gif]] 
*Causes shadows of [[VehicleTypes]] to display incorrectly(This issue was fixed in [[Ares]],[[Phobos]]). 
*At least in {{ts}}, [[VehicleTypes|Vehicle]] [[SHP|shapes]] with a turret are limited to a 160x160 pixel canvas. Any pixels beyond this limit are not drawn. 
IE Warning: 
Without considering any extension engines, for a vehicle with Image=<none>, even if it should not have an image or create an empty Shape image due to Image settings, if you add '''Turret=yes''', the game will still attempt to obtain a Voxel Turret section, and you will receive a internal error. Congratulations. xD
Only God knows about such an outrageous work logic.

Tubes

2025-07-02T15:59:59Z

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

{{WrongTitle|[Tubes]}}

{{MappingBar}}

This section lists all the Tunnels in this map. Note that internally each Tunnel listed here is one cell wide and one way, meaning a typical three-cell wide two-way tunnel construct requires ''six'' entries in this section, three running one way and three going backwards. While you can give each one a different path, it is not recommended since it breaks the unit pathfinding.

(You don't need the [[Terrain Expansion]] to make use of tunnels in YR, they're still part of the engine, but it'll be necessary if you want it looking pretty.)

__TOC__

== Section ==

=== {{td}} ===
Tunnels don't exist.

=== {{ra}}, {{cs}}, {{am}} ===
Tunnels don't exist.

=== {{ts}}, {{fs}}, {{ra2}}, {{yr}} ===

The [{{Tt|Tubes}}] section takes the following format:

[Tubes]
Index=ENTER_X,ENTER_Y,FACING,EXIT_X,EXIT_Y,DIRECTIONS

{| style="width: 80%" border=1 class="table_descrowdesccol"
|+ Meanings of each string
! style="width: 13em; " | String
! Meaning
|-
! {{Anchor|Index|ts}}
| This is an index into the list, not parsed, so any string without equals-signs will do. '''Note''': The game was not designed to support more than 127 entries in this list (which is 127/6 = 21 typical tunnel constructs). Exceeding that limit will cause problems.
|-
! {{Anchor|ENTER_X|ts}}
| The X coordinate of the entrance cell. Each tunnel should have a different entrance cell.
|-
! {{Anchor|ENTER_Y|ts}}
| The Y coordinate of the entrance cell.
|-
! {{Anchor|FACING|ts}}
| The numeric value of the facing the unit should assume before entering this tunnel. 0 - 7, with 0 standing for game North (NorthEast of the screen) and rotating clockwise.
|-
! {{Anchor|EXIT_X|ts}}
| The X coordinate of the exit cell.
|-
! {{Anchor|EXIT_Y|ts}}
| The Y coordinate of the exit cell.
|-
! {{Anchor|DIRECTIONS|ts}}
| A comma-separated list of directions the unit should follow as it moves through the tunnel. Up to 100 directions can be specified in one tunnel, list should end with -1.
|}

Special care should be taken to ensure the entrance and exit cells are at the same height, or units will get stuck in them, [https://ppmforums.com/post-581645#581645 see here] (VXL and SHP units can and will get stuck; train units can get stuck too in RA2YR). Also, due to the fact that Tunnels were never a proper feature in RA2/YR, they don't cooperate well with new additions such as Battle Bunkers. It is advised to keep the edges of tunnel roofs unbuildable. 

In the event a Tube doesn't actually reach the ending coordinate (because Tunnel Drawer only lets you move 100 cells so you have to force-end it) units will teleport to exit coordinates.
You can abuse this to create portals. Note that it '''seems like''' InfantryTypes don't teleport to exit coordinates and instead simply "exit" the tunnel; VehicleTypes are teleported without trouble.

=={{Bugs}}==
Note the game was not designed to support more than 127 entries in this list (which is 127/6 = 21 typical tunnel constructs). Exceeding that limit will cause problems.

==See also==
[https://ppmforums.com/topic-37881/ts-ra2-tunnel-drawer/ Tunnel Drawer (requires Flash Player; scroll to last post on thread for mirror)]

[[Category:Map Information]]

Translucent

2025-07-02T15:59:47Z

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

{{Flag
|name=Translucent
|files={{Categ|Art(md).ini}}
|values={{values|boolean}}
|default=no
|types={{Categ|Animations}}
|ts=yes
|fs=yes
|hp=yes
|ets=yes
|ra2=yes
|yr=yes
|ares=yes
}}
If set to 'yes', animation will be drawn with a gradual fade-out effect, starting as 100% opaque and fading to 100% transparent. Actual length of the fade-out effect is determined by the length of the animation. Defaults to 'no'.

==Note==
*If used together with the [[Reverse]] tag, it will cause transparency to work in reverse. That is, transparency will start at '''75''' then '''50''' then '''25''' then '''0'''.

=={{Bugs}}==
*If this were to be used with the SHP turret Will have the following results:
The more the turret is turned to the left, the Transparency will only be greatly reduced.
The more the turret is turned to the right, the Transparency will only increase.

[[File:Translucent on SHP turret1.png]] [[File:Translucent on SHP turret2.png]]

==See also==
*{{f|Translucency|link}}
*{{f|TranslucencyDetailLevel|link}}

Translucency

2025-07-02T15:59:37Z

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

{{Flag
|name=Translucency
|files={{Categ|Art(md).ini}}
|values=[[Help:Values#Integers|Integers]] (one of 0,25,50,75)
|default=0
|types={{Categ|Animations}},{{Categ|Particles}}
|ts=yes
|fs=yes
|hp=yes
|ets=yes
|ra2=yes
|yr=yes
|ares=yes
}}
Is used to make animation appear transparent. Animation will retain same level of transparency during it's entire lifetime. Valid values are 0, 25, 50 and 75, which stand for 0%, 25%, 50% and 75% transparent respectively.

=={{bugs}}==
[[Translucent]] conflicts with <tt>Translucency</tt>, and the object will obey <tt>Translucent</tt> instead.

==See also==
[[TranslucencyDetailLevel]]

[[DetailLevel]]

[[UseNormalLight]]

TrailerAnim

2025-07-02T15:59:27Z

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

{{Flag
|name={{PAGENAME}}
|files={{Ini|art}}
|default=none
|values={{Values|string|[[Animation]] IDs}}
|types=[[Animations]], [[VoxelAnims]][[#bugs|{{sup|1}}]]
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
Specifies the [[Animation]] to play as a trailer behind the parent animation. The parent object can be any [[SHP]] or [[VoxelAnims|voxel]][[#bugs|{{sup|1}}]] animation aside from [[projectiles]], which use the flag {{f|Trailer|link}} instead.

{{Automatictypelist|Animations|Animations}}

=={{Bugs}}==
{{sup|1}} Although TrailerAnim works on [[VoxelAnims]], the trailer's velocity is bugged, causing it to fly in a much higher arc than the parent object.

==See also==
* [[TrailerSeperation]]
* [[ExpireAnim]]
* [[Spawns]] and [[SpawnCount]]
* [[Next]]

Tmcj4f.ini

2025-07-02T15:59:11Z

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

{{Cheat|THETEAM}}

Secret .ini file originally found in the Tiberian Sun CDs, contains easter eggs - infantry and unit types from Tiberian Sun with different weapons and names of the Westwood development team. Activated by typing "THETEAM" in the startup screen.

A former Westwood programmer ''Denzil Long'' has stated he is the author of this easter egg and clarified the cryptic filename to be an abbreviation of "Totally Cool Mission Just 4 Fun" (with a typo, no less). ([http://www.petroglyphgames.com/forums/index.php?showtopic=4056&view=findpost&p=109334 Source]) 
When activated, this file is loaded after the real rules and treated like an additional rules file, but only for skirmish (not singleplayer campaigns and not multiplay) games. 

==Note==
*Most of the data in the file ''' 'Tmcj4f.ini' ''' is quite outdated. [[RA2]],[[YR]], although it still works. But you still have to add the information you want.

[[Category: General Editing Information]]
[[Category: INI Files]]
=={{Bugs}}==
*In [[YR]], this can cause pre placed buildings on the map to lose their working animations, such as the national flag with only flagpoles left, and the radar at the tech airport stopping to swing. etc
*It is strange that '''Lasher Light Tank'''' can appear in [[RA2]] (As a matter of fact, the '''Light Tank''' exists in [[RA2]], but is not used,and [[Westwood]] used it in [[YR]] instead).

Tiled

2025-07-02T15:59:01Z

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

{{Flag
|files={{Categ|Art(md).ini}}
|values={{Values|Boolean|yes|no|1|0}}
|types={{Categ|Animations}}
|ts=no
|fs=no
|ets=no
|ra2=yes
|yr=yes
|rp=no
}}
Tiled=yes makes the anim "stack" upwards. It is used in Tiberian Sun's [IONBEAM] so the beam draws from the top of the screen to target cell. 
In theory, you can see the anim playing from top of the map to the bottom of the map. If Tiled=yes is used with the SHP turret It will look incredibly funny. [[File:Tiled on SHP turret.png]]
==Note==
*Because this is a tag used for Animation rather than for Particles, it has no effect on the images called by Particles, which is a natural thing.
=={{Bugs}}==
* [[Animations]]are hardcoded to use the {{f|AnimPalette|yes|Link}} palette Always
*This bug has been fixed in [[Phobos]] Build33.
"[https://phobos.readthedocs.io/en/latest/Fixed-or-Improved-Logics.html#bugfixes-and-miscellaneous Animation with Tiled=yes now supports CustomPalette.]"

TickTank

2025-07-02T15:58:51Z

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

{{Flag
|files={{Categ|ini=rules}}
|values={{Values|Boolean}}
|default=0
|types={{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|hp=yes
|ets=yes
|ra2=yes
|yr=yes
|ares=yes
}}
This flag acts similar to {{f|Artillary|link}} and {{f|IsJuggernaut|link}} as they control the direction a unit will turn to before deploying into a structure. When enabled on a [[BuildingType|building]], any unit that deploys into said building will turn to face [[Compass|east]] (bottom-right) before deploying.

=={{bugs}}==
===Hardcoded AI behavior===
Although generally useful, it is worth noting that this flag affects the deployer unit behavior when AI-controlled. Whenever the unit that can deploy into this structure engages with an enemy vehicle or an armed defensive structure, it will deploy, if able.

===Hardcoded theater-specificity===
If the building has a [[turret]], the building's art entry requires {{f|NewTheater|yes|link}}, else the turret won't show. This in turn requires that the building [[shape]] files are found in theater-specific [[MIX]] files.

Tiberiums

2025-07-02T15:58:41Z

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

{{guideheader
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
Tiberium is the resource used for energy and money replacement in {{td}} and {{ts}}/{{fs}}. In the Red Alert series, the ore and gems are still internally referred to as Tiberium variants.

==Game Lore==
Tiberium landed on Earth via a meteorite which crashed close to the Tiber River in Italy, hence spawning the name 'Tiberium'. Tiberium exists as crystalline formations situated on small ground pods. These crystals spawn toxic spores which travel through the air, contaminating and mutating whatever organic material they come into contact with. Tiberium works by creating large roots down into the soil, these roots leach minerals and other valuable materials upward into the ground pod, which then uses them in their crystals, making Tiberium a very valuable resource.
Sometimes the airborne spores come into contact with plant matter, and, in the case of trees, can mutate them into what are known as Blossom Trees, these spawn more green Tiberium crystals. All Tiberium types, except the basic Riparius are explosive.

==The 4 Tiberium Types==
*{{co|Tiberium Riparius|green}} : The basic green Tiberium, spawned from Blossom Trees. It has a moderate value.
*{{co|Tiberium Vinifera|blue}}: A more valuable form of Tiberium, its crystals are blue and is spawned from large blue Vinifera seed crystals.
*{{co|Tiberium Cruentus|navy}}: It exists solely as a large dark blue crystal, it can be destroyed, but not harvested .
*{{co|Tiberium Aboreus|red}}: This form of Tiberium is listed in TS inis, but is unused in game.

Modders sometimes enable usage of Aboreus, giving it the appearance of 'red' Tiberium, and making it an even more valuable, but scarce variant.

==In the Game==
The [Tiberiums] section of [[Rules|rules(md).ini]] is a list of all available Tiberium/Ore/Gem types in the game. What's not listed doesn't get parsed and therefore doesn't exist. Tiberium is a special type of [[OverlayTypes|overlay]], and while adding new types may be possible, they'll be subject to the same restrictions as the original unused types, Vinifera and Aboreus. Since these two are at least in the game already, it's probably smarter to alter them rather than adding new types.

In {{ra2}} and {{yr}} the basic 'ore' is internally Riparius, and 'gems' are Cruentus.

== Applicable INI Flags ==
{{Applicable INI Flags}}
<onlyinclude>
{{Applicable INI Flags Header|Tiberiums (Riparius/Vinifera/etc..)}}
|-
| {{Ini|Rules}} || Object's ID || {{f|Name|link}} || str || 1 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Image|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Spread|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|SpreadPercentage|link}} || float || 0.1 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Growth|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|GrowthPercentage|link}} || float || 0.1 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Value|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Power|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Color|link}} || ColorName || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|Debris|link}} || vector<Animation> || {} || +
|}
</onlyinclude>
==Note==
[[Image]] on Tiberium types doesn't function the way it does on other objects. Instead of an explicitly named image to use, it takes values 1-4, associated with hardcoded [[OverlayTypes|OverlayType]] indexes. Note that the position (index) of the overlay in the internal array differs from the [OverlayTypes] list in {{ini|rules}}.
 
The possible values of [[Image]] are listed below with their corresponding overlay indexes.
{| class="wikitable"
|-
! Image !! Internal Index !! INI Index !! Overlays in Set
|-
| 1 (Riparius) || 102 || 105 || 20
|-
| 2 (Cruentus) || 27 || 28 || 12
|-
| 3 (Vinifera) || 127 || 130 || 20
|-
| 4 (Aboreus) || 147 || 150 || 20
|}
For Tiberiums that use 20 overlays, the last 8 overlays are used for overlays placed on slopes. Note that this only works correctly in Tiberian Sun, as Tiberiums don't typically appear on slopes in Red Alert 2 and Yuri's Revenge.
=={{bugs}}==
There is a commented out <tt>Shard</tt> tag listed under this section in {{ini|rules}}, however, it does not actually exist in the game executable. The closest matching the description is [[Debris]].

Adding more Tiberium variants with the TS [[Vinifera|Engine Extension Vinifera]] is possible, see: [https://vinifera.readthedocs.io/en/latest/New-Features-and-Enhancements.html#new-tiberiums Official Documentation]

==See also==
[http://ppmsite.com/forum/viewtopic.php?t=2621 Creating a new Resource System] (Tutorial for RA2/YR at PPM)

[http://forums.revora.net/index.php?showtopic=31031 Automatic Ore Generation] (Tutorial for RA2/YR at Revora)
*To create a new ore mine spawning a new type of resource, combine both tutorials above.

[http://en.wikipedia.org/wiki/Tiberium Wikipedia: Tiberium]

[http://planetcnc.gamespy.com/View.php?view=Encyclopedia.Detail&id=13#tiberium Planet CnC/C&C Encyclopedia: Tiberium]

[[OverlayTypes]]
[[Category:Rules(md).ini Sections]]
[[Category:General Editing Information]]
[[Category:Information]]

Thief

2025-07-02T15:58:09Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=Booleans
|default=no
|types={{Categ|InfantryTypes}}
|ra=no
|cs=no
|am=no
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|rp=yes
}}

In {{ra}}, the Thief was an [[InfantryType|infantry unit]] that could enter a Refinery or Silo and steal 50% of the credits it contains.

== In {{ts}} and {{fs}} ==

The {{f|Thief}} flag was introduced in Tiberian Sun, and as its name and {{Categ|ini=rules|rules.ini}} description suggests, it was supposed to make the unit able to steal credits just like the Thief in Red Alert. Unfortunately, the flag does nothing at all.

== In {{ra2}} and {{yr}} ==

{{f|Thief|yes}} allows the infantry to enter a refinery when used with {{f|Infiltrate|yes|link}} in RA2 but it does not steal any money. For the same in YR, the infantry is rejected from entering, so it cannot enter the buildings. Stealing credits is now achieved by using {{f|Agent|yes|link}} in RA2/YR.

{{f|Thief|yes}} is also required for {{f|VehicleThief|yes|link}} to work correctly.

=={{Bugs}}==
In {{Yr}} at least, if {{f|Thief|yes|link}} is set on an [[InfantryType]] then that [[InfantryType]] will be unable to enter guard mode. For example, setting {{f|Thief|yes|link}} on an Attack Dog will prevent the Attack Dog from detecting and attacking disguised enemy units automatically.

Theater

2025-07-02T15:57:59Z

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

==On ObjectTypes==
{{Flag
|files={{Categ|ini=art}}
|values={{values|boolean}}
|default=no
|types={{Categ|Objects}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
Specifies if an alternate [[image]] should be loaded for the object based on the map's [[Theaters|theater]]. If this is set, the game will discard the {{Tt|SHP}} extension of the filename and use the same extension this theater's terrain tiles use. Correspondingly, the file it uses is not necessarily the standard tem file, such as the original {{tt|tree##.tem}}. The characters used for each theater can be found on the [[Theaters]] page.

In {{ra2}}/{{yr}}, {{f|Theater|yes}} essentially hardcodes the object to be a [[TerrainTypes|terrain object]]. Ore can spawn and grow in their [[Foundation]] range, and they can use the relevant {{f|SpawnsTiberium|link}}, {{f|IsAnimated|link}}, {{f|AnimationRate|link}}, and {{f|AnimationProbability|link}} flags associated with spawning ore.

Objects with {{f|Theater|yes}} will furthermore not accept most art flags such as {{f|ActiveAnim|link}} or {{f|Palette|link}}.

==Note==
*For the [[TerrainTypes]] object, even if '''Theater=yes''' is not specified, if you have an object file whose extension ends with a theater abbreviation, such as .tem .sno .urb etc., when you play in that theater, the object image will change to the current image in that theater file.

=={{Bugs}}==
* Although this flag is parsed on all object types, it only works properly on [[shape]] art.
* This flag does not work with [[InfantryTypes]].

==On Maps==
{{Flag
|files={{Categ|Maps}}
|values={{values|string|[[Theaters]]}}
|types={{Categ|Maps}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
Specifies which [[Theaters|theater]] this map should use. Technically, this allows you to change the theater of the map at will, for example from a snow map to a temperate map, without otherwise editing the map or creating a whole new map. 
However, most theaters have minimal interchangeability because their tilesets don't always have equivalents in all theaters. Therefore, changing the map theater may result in graphical errors.

==Example==
<div><ul>
<li style="display: inline-block;">[[File:Hill Between(Original).png|frame|A Hill Between (Original, Theater=URBAN)]]</li>
<li style="display: inline-block;">[[File:Hill Between(NEWURBAN).png|frame|A Hill Between (Theater=NEWURBAN)]]</li>
</ul></div>

The Prerequisite System

2025-07-02T15:57:49Z

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

The Prerequisite System controls the conditions required to build a certain object. Those conditions are:
:{|style="border: 1px solid #aaaaaa; background:#e5e5e5; border-spacing: 5px;"
|
; Is this object's TechLevel valid?
: Checks if the TechLevel of the object is above -1 and below [{{f|MultiplayerDialogSettings|link}}]→{{f|TechLevel|link}}.
; Is this house not forbidden from owning this object?
: Checks if the house is not listed in {{f|ForbiddenHouses|link}}.
; Is this house allowed to own this object?
: Checks if the house is listed in {{f|RequiredHouses|link}}.
; Does this house own all the prerequisite structures?
: Checks if the house owns the prerequisite structures listed in {{f|Prerequisite|link}}
; Is this object stolen technology?{{yro}}
: If the unit contains {{f|RequiresStolenAlliedTech|link}}<tt>=yes</tt>, {{f|RequiresStolenSovietTech|link}}<tt>=yes</tt>, or {{f|RequiresStolenThirdTech|link}}<tt>=yes</tt>, has the apropriate lab get spied upon?
|}
If all conditions are met, the house is ''theoretically allowed'' to build that object, signaled by a [[EVA_NewConstructionOptions|"New Construction Options"]] announcement. 
Next, the game determines whether the house ''actually can'' build the object:
:{|style="border: 1px solid #aaaaaa; background:#e5e5e5; border-spacing: 5px;"
|
; Does the house own a {{f|Factory|link}} of the appropriate type?
: Checks whether the house has at least one structure with {{f|Factory|link}} matching the object's type.
; Can this house own this object?
: Checks if your {{f|Factory|link}} contains atleast 1 {{f|Owner|link}} listed as this units {{f|Owner|link}}.
; If the object in question is a VehicleType, does the house have a {{f|Factory|VehicleType|link}} with the same {{f|Naval|link}} setting as the object?
: Checks whether the house has a War Factory if it's trying to build land-based ({{f|Naval|no|link}}) vehicles, and whether it has a Shipyard if it's trying to build water-based ({{f|Naval|yes|link}}) vehicles.
|}

==Overrides==
*If an object has a {{f|PrerequisiteOverride|link}} BuildingType (or multiple BuildingTypes) set, a house will be allowed to build the object as soon as it possesses any single one of those listed BuildingTypes, no matter what prerequisites the object usually requires. (Hence the name.)
*The same applies to objects from {{f|SecretLab|yes|link}} buildings: If a house gains an object through a Secret Lab, it will be allowed to build that object immediately, no matter what prerequisites the object usually requires. Such an object will be buildable even if it has {{f|TechLevel|11|link}} set.
*In addition, AI players do not check {{f|Prerequisite|link}} and {{f|TechLevel|link}} tags when they're trying to build the Power Plants listed under {{f|GDIPowerPlant|link}}, {{f|NodRegularPower|link}}, {{f|ThirdPowerPlant|link}}{{yro}}.
*AI players also ignore all {{f|Prerequisite|link}} settings except {{f|TechLevel|link}} on all other objects, they build objects in the order dictated by the {{Ini|ai}} file (the order of BuildingTypes is controlled by different methods covered [[AI base building|here]]).
''All cases under the presumption that the house owns a factory of the appropriate type.''

==Prerequisite Groups==
A "prerequisite group" refers to a list of structures, and any single one of them is sufficient to fulfill the type. See: [[Generic Prerequisites]].

=={{bugs}}==
Only one building specified by <tt>PrerequisiteOverride=</tt> activates production, meaning that it's not a cumulative list like <tt>Prerequisites=</tt>.
* Ares can allow more types of prerequisite alternatives, see: https://ares-developers.github.io/Ares-docs/new/prerequisites.html

At least in {{ra2}} and {{yr}}, the AI players ignore <tt>Prerequisites=</tt> for building queues, limited instead by [[AIBuildThis]], [[Owner]], [[RequiredHouses]], [[ForbiddenHouses]], and stolen tech requirements.

Also in {{ra2}}, the [[AITriggerTypes]] in {{ini|ai}} instruct the AI player to produce [[TaskForces]] disregarding <tt>Prerequisites</tt> altogether, as well as [[TechLevel]], limited by other factors as above.

[[Category: Systems]]

TerrainTypes

2025-07-02T15:57:35Z

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

{{sectionheader
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}

This section of [[Rules|rules(md).ini]] lists all terrain objects, typically trees, the game should be able to use. Terrain objects not listed here cannot be placed on a map by an editor, and if found on a map they will be ignored by the game.

== Applicable INI Flags ==
{{Applicable INI Flags}}
{{:AbstractTypes}}
{{:ObjectTypes}}
<onlyinclude>
{{Applicable INI Flags Header|TerrainTypes}}
|-
| {{Ini|Rules}} || Object's ID || {{f|IsVeinhole|link}} || boolean || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|WaterBound|link}} || boolean || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|SpawnsTiberium|link}} || boolean || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|IsFlammable|link}} || boolean || 0 ||
|-
| {{Ini|Art}} || Object's Image || {{f|Foundation|link}} || Foundation || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|RadarColor|link}} || Color || {0;0;0} ||
|-
| {{Ini|Rules}} || Object's ID || {{f|IsAnimated|link}} || boolean || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|AnimationRate|link}} || int || 0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|AnimationProbability|link}} || float || 0.0 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|TemperateOccupationBits|link}} || int || 7 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|SnowOccupationBits|link}} || int || 7 ||
|-
| {{Ini|Rules}} || Object's ID || {{f|YDrawFudge|link}} || int || 0 ||
|}
</onlyinclude>
=={{bugs}}==
Due to the way art is used by the game, [[Voxel|Voxels]] which use UNITxxx.PAL palettes, as their lighting/shading is dependent on the [[VPL]], can't be used as <tt>TerrainTypes</tt>, which use the ISOxxx.PAL [[Theaters|Theater-specific]] palettes.

[[Category:Rules(md).ini Sections]]

Temporal

2025-07-02T15:57:25Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=boolean
|default=no
|types={{Categ|Warhead|Warheads}}
|ra2=yes
|yr=yes
|rp=yes
}}

{{SourceCode|http://dc.strategy-x.com/src2/TemporalClass/TemporalClass.hpp|tr=yes}}

If {{f|Temporal|yes|link}} is set on a weapon's [[warhead]], then the target will be "frozen" and gradually erased from time. The affected unit is rendered transparent, and the animation specified by [{{f|AudioVisual|link}}]{{arr|r}}{{f|ChronoSparkle1|link}} is played over it. Whilst a unit is frozen it cannot be targeted or affected by any other [[warhead]] (except other {{f|Temporal|yes|link}} [[warheads]]), and is unable to move or attack.

The firing unit must continue firing the weapon at the target until the target is erased, otherwise the target will unfreeze unharmed. The delay necessary to erase an object depends on the weapon's {{f|Damage|link}} - each frame, a Temporal weapon firing at a target "takes away" as many points as its Damage dictates, and the unit gets erased when 10 * its maximum hitpoints have been "taken away". The duration completely ignores warhead percentages or current unit hitpoints.

Objects that have {{f|Warpable|no|link}} set cannot be targeted (and thus cannot be affected) by a {{f|Temporal|yes|link}} [[warhead]].

Note that {{f|Temporal|yes|link}} warheads will cause an [[Internal Error]] when detonated if any of the following conditions are true:
*Firing weapon is a shrapnel weapon and [[DeathWeapon]].
*Firing weapon is an urban combat weapon (fired from an occupied building).
*Warhead has a non-zero {{f|CellSpread|link}} set.
*Warhead also uses the {{f|Culling|yes|link}} flag (which doesn't apply to non-squidlike units anyway).
*Firing weapon is a secondary weapon (except for Infantry with {{f|Deployer|yes|link}} and {{f|DeployFire|yes|link}}). ;(The problem was resolved by adding Temporal=yes to the warhead of [[Primary]] and [[ElitePrimary]])
==Note==
[[TechnoTypes]] that are higher than ground are not affected by this tag. even if an Aircraft [[FlightLevel]] only 1. ([[Ares]] fixed) 
Effects from this tag It will happen only when it actually affects the actual target. The attack on the ground was nothing more than a deception.
=={{Bugs}}==
*If there Is Temporal=yes tag This tag will disable the tag [[Particle]]

Teleporter

2025-07-02T15:57:15Z

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

{{Flag
|name=Teleporter
|values={{values|boolean}}
|special=
|default=no
|types={{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}
|ra2=yes
|yr=yes
}}

This flag has two meanings.

If Teleporter is set to {{f|yes}} on an InfantryType, then said [[InfantryTypes]] can be teleported by the Chronosphere without being killed.

If Teleporter is set to {{f|yes}} on a [[VehicleTypes]] with the chrono [[Locomotor]] set, then said VehicleType will only teleport to dock to a building which has {{f|DockUnload|yes}} set.
==Nost==
[[VehicleTypes]] with tags Teleporter=yes and
{{f|Locomotor|{4A582747-9839-11d1-B709-00A024DDAFD1}|Link}}
If we control the [[VehicleTypes]] mentioned above and press the Z key [[VehicleTypes]] will not move automatically.

[[VehicleTypes]] with tags Teleporter=yes and {{f|Locomotor|{4A582746-9839-11d1-B709-00A024DDAFD1}|Link}} The [[Turret]] will automatically turn in any direction. and attack animations will be on the wrong side.

[[File:Teleporter=yes and Locomotor=4A582746-9839-11d1-B709-00A024DDAFD1.gif]]
=={{Bugs}}==
[[InfantryTypes]] with tags Teleporter=yes and {{f|C4|yes|Link}} will not die when hit by a warp Enter the water.
ิby [[Superweapons]]

==See also==
{{f|Organic|no|link}}

TechLevel

2025-07-02T15:57:05Z

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

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}, {{Categ|Maps}}
|values=signed integers
|default=<nowiki>-1 (255 on TechnoTypes)</nowiki>
|types={{Categ|MultiplayerDialogSettings}} ([[Image:Ra2small.png]]{{yro}}) , {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, {{Categ|BuildingTypes}} (rules(md).ini), {{Categ|Houses}} (maps)
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}

== On BuildingTypes ==

By constructing the building, the house's "technology level" is ''increased'' to this value, if necessary.

== On Infantry/Vehicle/Aircraft Types ==

This flag specifies the "technology level" necessary to build this object.

== In [{{f|MultiplayerDialogSettings|link}}] ==

This flag specifies the maximum TechLevel achievable in the game. In previous games, you could control this by means of another slider, like the one used for Starting Money or Game Speed. The effect of this limit is that only TechLevel values in the interval 0 - this value (inclusive) are considered "allowed", and all others are disabled.

== On {{f|Houses|link}} ==

This flag specifies the starting tech level for this AI-controlled house.

== Limitations of this system ==

{| style="border: 1px dashed #aaa; text-align: center; border-collapse: collapse;" border=1
|+ TechLevel limitations
|- style="background: #eee;"
! rowspan=2 | TechLevel
! colspan=4 | Can be
|- style="background: #eee;"
! Built by AI
! Built by Humans
! A Crate goodie
! A Secret Lab boon
|-
| style="text-align: left;" | -1
| {{Y}} || {{N}} || {{Y}} || {{Y}}
|-
| style="text-align: left;" | 0 through the maximum (set in MultiplayerDialogSettings)
| {{Y}} || {{Y}} || {{Y}} || {{Y}}
|-
| style="text-align: left;" | above the maximum
| {{N}} || {{N}} || {{N}} || {{Y}}
|}

TechLevel -2 and below are considered as buildable at any TechLevel.

And AI doesn't build Techlevel -1 units even if given in TaskForces. Buildings case is covered in the table above.

==Additional note==
The hack that Westwood used to make battle bunkers in YR stay owned when empty and not evict infantry when damaged is tied to Techlevel= ; if the techlevel is -1, the building will be treated as a normal civilian building. If the techlevel is anything besides -1, it will be treated with battle bunker logic
=={{Bugs}}==
[[File:TechLevel=-1 Bug.gif]]
If [[TechnoTypes]] with tag TechLevel=-1
and our [[ BuildingTypes]] has {{f|SecretLab|yes|Link}} tags and unlocks those [[TechnoTypes]] TechLevel=-1 .
When we make a purchase [[TechnoTypes]] TechLevel=-1 mentioned above. The download will only stop at 50%.