https://modenc2.markjfox.net/api.php?action=feedcontributions&feedformat=atom&user=Crimsonum 2026-06-06T01:53:31Z User contributions MediaWiki 1.43.0 https://modenc2.markjfox.net/index.php?title=Passive&diff=28631 2025-06-25T20:28:21Z

<p>Crimsonum: This page was totally wrong.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Rules(md).ini}}<br /> |values={{Values|bool|}}<br /> |types={{Categ|VehicleTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> If set, makes this [[VehicleTypes|vehicle]] unable to move by itself. This is meant to be used on units such as train cars, which are scripted in the [[map]] to [[Units_(maps)#ts_FOLLOWS_INDEX|follow]] the movement of the locomotive.<br /> <br /> ==See Also==<br /> *[[Units_(maps)#ts_FOLLOWS_INDEX|Unit follower parameter]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=FiringSyncFrame1&diff=28630 2025-06-23T20:44:14Z

<p>Crimsonum: </p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|art(md).ini}}<br /> |values={{values|unsigned integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |fs=yes<br /> }}<br /> <br /> Specifies the [[frame|time frame]], 0-based index, in this unit's [[FiringFrames|firing sequence]] to fire the [[weapon]] at. Only applies if the unit has {{f|FiringFrames|link}} defined.<br /> <br /> == Notes ==<br /> *[[SHP|Shape-based]] vehicle units' firing sequences are played in reverse relative to the normal frame order, i.e. from the highest firing frame index to lowest firing frame index. However, this flag is calculated in the ''opposite'' (normal) direction, from lowest frame index to highest frame index. In other words, higher values mean the weapon is fired sooner.<br /> <br /> *Every firing frame lasts for ''two'' time frames.<br /> <br /> *If the unit has a weapon with multiple [[Burst|bursts]], you '''must''' define {{f|FiringSyncFrame2|link}} else the weapon will ignore any [[ROF|cooldown]].<br /> <br /> == Example ==<br /> <br /> Suppose that a unit has a firing sequence that consists of eight frames ({{f|FiringFrames|8}}). If you want the unit to fire its weapon right away, you would use {{f|FiringSyncFrame1|15}}. If you want the unit to fire its weapon at the end of the firing sequence, you would use {{f|FiringSyncFrame1|0}}.<br /> <br /> {{bugs}}<br /> * Specifying this flag has the peculiar side-effect of allowing the unit to fire both its [[Primary]] and [[Secondary]] weapons simultaneously.<br /> * Overrides {{f|BurstDelay|link}} on the weapon(s), if any.<br /> <br /> == See Also ==<br /> * [[FiringSyncFrame2]]<br /> * [[FiringFrames]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Template:Bugs&diff=28629 2025-06-23T19:33:47Z

<p>Crimsonum: Undo revision 28628 by Crimsonum (talk)</p> <hr /> <div>=={{Anchor|Bugs||}}{{Anchor|bugs||}}[[Image:Cc_alert.png|24px]] Bugs/Side-Effects/Unexpected Limitations==<br /> <br /> &lt;includeonly&gt;[[Category:Bugs_and_Errors]]&lt;/includeonly&gt;&lt;noinclude&gt;<br /> ==Usage==<br /> &lt;pre&gt;{{Bugs}}&lt;/pre&gt;<br /> Copy-paste the code above and use it to start a Bugs section on a page that describes a flag or feature that has one or more bugs, side-effects or unexpected limitations. This will create a standardized title with a warning icon. An invisible anchor named &quot;bugs&quot; (case insensitive) is included as an alternative title. Using this template also adds the page to [[:Category:Bugs and Errors]] automatically.<br /> &lt;/noinclude&gt;</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Template:Bugs&diff=28628 2025-06-23T19:30:56Z

<p>Crimsonum: Ported from ModEnc. Original author: DeathFish</p> <hr /> <div>{{Anchor|Bugs||}}{{Anchor|bugs||}}[[Image:Cc_alert.png|24px]] Bugs/Side-Effects/Unexpected Limitations&lt;includeonly&gt;[[Category:Bugs_and_Errors]]&lt;/includeonly&gt;&lt;noinclude&gt;<br /> ==Usage==<br /> &lt;pre&gt;{{Bugs}}&lt;/pre&gt;<br /> Copy-paste the code above and use it to start a Bugs section on a page that describes a flag or feature that has one or more bugs, side-effects or unexpected limitations. This will create a standardized title with a warning icon. An invisible anchor named &quot;bugs&quot; (case insensitive) is included as an alternative to the title. Using this template also adds the page to [[:Category:Bugs and Errors]] automatically.<br /> ----<br /> This template was updated on {{co|20:04, 1 May 2025|purple}} and '''no longer automatically assigns heading levels''', to prevent the counterintuitive behavior where clicking &quot;edit&quot; on that paragraph would modify the content of this page instead of the corresponding section on the original page. If you want it to be a heading level like before, please use the following notation:<br /> &lt;pre&gt;== {{Bugs}} ==&lt;/pre&gt;<br /> == {{Bugs}} ==<br /> This also brings an advantage: now you can conveniently and freely define the heading levels it uses, '''no longer limited to just level 2 headings'''.<br /> &lt;/noinclude&gt;</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=StartStandFrame&diff=28627 2025-06-23T19:23:49Z

<p>Crimsonum: Ported from ModEnc. Original author: DeathFish</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=art}}<br /> |values={{values|integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies the starting frame index of this unit's standing animation sequence. Only applies to [[SHP]]-based units.<br /> <br /> =={{Bugs}}==<br /> Unfortunately, this doesn't work. When not moving, the unit actually continues to use the walk sequence frames, only the rate changes from {{f|WalkRate}} to {{f|IdleRate}}.<br /> <br /> == See Also ==<br /> * {{f|StartWalkFrame|link}}<br /> * {{f|StartFiringFrame|link}}<br /> * {{f|StandingFrames|link}}<br /> * {{f|IdleRate|link}}</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=StartWalkFrame&diff=28626 2025-06-23T19:23:30Z

<p>Crimsonum: Ported from ModEnc. Original author: DeathFish</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=art}}<br /> |values={{values|integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies the starting frame index of this unit's firing and standing animation sequence. Only applies to [[SHP]]-based units.<br /> <br /> == See Also ==<br /> * {{f|StartStandFrame|link}}<br /> * {{f|StartFiringFrame|link}}<br /> * {{f|WalkFrames|link}}<br /> * {{f|WalkRate|link}}</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=StartFiringFrame&diff=28625 2025-06-23T19:20:23Z

<p>Crimsonum: Ported from ModEnc. Original author: DeathFish</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=art}}<br /> |values={{values|integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies the starting frame index of this unit's firing animation sequence. Only applies to [[SHP]]-based units.<br /> <br /> == See Also ==<br /> * {{f|StartWalkFrame|link}}<br /> * {{f|StartStandFrame|link}}<br /> * {{f|FiringFrames|link}}<br /> *{{fso}}{{f|FiringSyncFrame1|link}}<br /> *{{fso}}{{f|FiringSyncFrame2|link}}</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=FiringSyncFrame1&diff=28624 2025-06-23T19:18:55Z

<p>Crimsonum: Created page with &quot;{{Flag |name={{PAGENAME}} |files={{Categ|art(md).ini}} |values={{values|unsigned integer}} |types={{Categ|VehicleTypes}} |fs=yes }} Specifies the time frame, 0-based index, in this unit&#039;s firing sequence to fire the weapon at. Only applies if the unit has {{f|FiringFrames|link}} defined. == Notes == *Shape-based vehicle units&#039; firing sequences are played in reverse relative to the normal frame order, i.e. from the highest firing f...&quot;</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|art(md).ini}}<br /> |values={{values|unsigned integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |fs=yes<br /> }}<br /> <br /> Specifies the [[frame|time frame]], 0-based index, in this unit's [[FiringFrames|firing sequence]] to fire the [[weapon]] at. Only applies if the unit has {{f|FiringFrames|link}} defined.<br /> <br /> == Notes ==<br /> *[[SHP|Shape-based]] vehicle units' firing sequences are played in reverse relative to the normal frame order, i.e. from the highest firing frame index to lowest firing frame index. However, this flag is calculated in the ''opposite'' (normal) direction, from lowest frame index to highest frame index. In other words, higher values mean the weapon is fired sooner.<br /> <br /> *Every firing frame lasts for ''two'' time frames.<br /> <br /> *If the unit has a weapon with multiple [[Burst|bursts]], you '''must''' define {{f|FiringSyncFrame2|link}} else the weapon will ignore any [[ROF|cooldown]].<br /> <br /> == Example ==<br /> <br /> Suppose that a unit has a firing sequence that consists of eight frames ({{f|FiringFrames|8}}). If you want the unit to fire its weapon right away, you would use {{f|FiringSyncFrame1|15}}. If you want the unit to fire its weapon at the end of the firing sequence, you would use {{f|FiringSyncFrame1|0}}.<br /> <br /> =={{bugs}}==<br /> Specifying this flag has the peculiar side-effect of allowing the unit to fire both its [[Primary]] and [[Secondary]] weapons simultaneously.<br /> <br /> == See Also ==<br /> * [[FiringSyncFrame2]]<br /> * [[FiringFrames]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=FiringSyncFrame2&diff=28623 2025-06-23T19:18:35Z

<p>Crimsonum: Created page with &quot;{{Flag |name={{PAGENAME}} |files={{Categ|art(md).ini}} |values={{values|unsigned integer}} |types={{Categ|VehicleTypes}} |fs=yes }} Specifies the time frame, 0-based index, in this unit&#039;s firing sequence to fire remaining weapon burst(s) at. The first burst is fired at the time frame defined in {{f|FiringSyncFrame1|link}}, or if the flag is not defined, at the beginning of the firing sequence. Only applies if the unit has {{f|Firing...&quot;</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|art(md).ini}}<br /> |values={{values|unsigned integer}}<br /> |types={{Categ|VehicleTypes}}<br /> |fs=yes<br /> }}<br /> <br /> Specifies the [[frame|time frame]], 0-based index, in this unit's [[FiringFrames|firing sequence]] to fire remaining weapon [[Burst|burst(s)]] at. The first burst is fired at the time frame defined in {{f|FiringSyncFrame1|link}}, or if the flag is not defined, at the beginning of the firing sequence.<br /> <br /> Only applies if the unit has {{f|FiringFrames|link}} defined and {{f|Burst|2|link}} or higher.<br /> <br /> == Notes ==<br /> *[[SHP|Shape-based]] [[VehicleTypes|vehicle units]]' firing sequences are played in reverse relative to the normal frame order, i.e. from the highest firing frame index to lowest firing frame index. However, this flag is calculated in the ''opposite'' (normal) direction, from lowest frame index to highest frame index. In other words, higher values mean the weapon is fired sooner.<br /> *Vehicle units' firing frames lasts for ''two'' time frames.<br /> *{{f|FiringSyncFrame2}} '''must''' be set to a value equal to or lower than {{f|FiringSyncFrame1}}, else the system will break and the unit will fire rapidly as if ignoring any [[ROF|cooldown]].<br /> <br /> == Example ==<br /> <br /> Suppose that a unit has {{f|Burst|2}} and a firing sequence that consists of eight frames ({{f|FiringFrames|8}}). If you want the unit to fire its second burst right away, you would use {{f|FiringSyncFrame2|15}}. If you want the unit to fire its its second burst at the end of the firing sequence, you would use {{f|FiringSyncFrame2|0}}.<br /> <br /> == See Also ==<br /> * [[FiringSyncFrame1]]<br /> * [[FiringFrames]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Floater&diff=28622 2025-06-23T13:27:22Z

<p>Crimsonum: Created page with &quot;{{Flag |files={{Categ|Rules(md).ini}} |values={{Values|bool}} |default=no |types={{Categ|Projectiles}} |ts=yes |fs=yes |ra2=yes |yr=yes }} If enabled, decreases the effect of gravity on this projectile by 50%. This makes the projectile fly slower, like a frisbee. Only applicable on arcing/freefalling projectiles.&quot;</p> <hr /> <div>{{Flag<br /> |files={{Categ|Rules(md).ini}}<br /> |values={{Values|bool}}<br /> |default=no<br /> |types={{Categ|Projectiles}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> If enabled, decreases the effect of [[gravity]] on this projectile by 50%. This makes the projectile fly slower, like a frisbee. Only applicable on [[arcing]]/freefalling projectiles.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=AIAlternateProductionCreditCutoff&diff=28618 2025-06-16T14:35:21Z

<p>Crimsonum: More precise wording</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=rules}}<br /> |types={{Categ|General}}<br /> |values={{values|unsigned integers}}<br /> |default=0<br /> |ts=yes<br /> |fs=yes<br /> |ets=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |rp=yes<br /> }}<br /> Specifies the credits threshold for the AI to start spending money more conservatively. When the AI has less money than this, it will alternate between constructing buildings and producing units instead of producing both at the same time like normal.<br /> <br /> In this alternate production mode, the AI prioritises building construction: If the AI is missing either an infantry or vehicle [[Factory|factory]], or has low [[power]], it will construct the necessary buildings first. If these conditions are satisfied, it will somewhat randomly alternate between producing buildings and units.<br /> <br /> At any point, if the AI gains more money than this threshold, it will return to normal, unrestrained production.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=AIAlternateProductionCreditCutoff&diff=28617 2025-06-16T14:13:24Z

<p>Crimsonum: Updated</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=rules}}<br /> |types={{Categ|General}}<br /> |values={{values|unsigned integers}}<br /> |default=0<br /> |ts=yes<br /> |fs=yes<br /> |ets=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |rp=yes<br /> }}<br /> Specifies the credits threshold for the AI to start spending money more conservatively. When the AI has less money than this, it will alternate between constructing buildings and producing units instead of producing both at the same time like normal.<br /> <br /> In this alternate production mode, the AI prioritises building construction. Once it determines that it needs no more buildings (it has both infantry and vehicle [[Factory|factories]] as well as enough [[power]]), it will switch to producing units. After producing a unit (that isn't a [[Harvester]]), there's a 50% chance it will then switch back to constructing buildings, restarting the loop.<br /> <br /> At any point, if the AI gains more money than this threshold, it will return to normal, unrestrained production.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=WallTower&diff=28616 2025-06-16T11:57:04Z

<p>Crimsonum: Updated</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=rules}}<br /> |values={{Values|string|BuildingTypes}}<br /> |types={{Categ|BuildingTypes}}<br /> |default=none<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies a special defensive [[BuildingTypes|building]] for GDI/Allies. Originally used for the GDI Component Tower in {{ts}}, an unarmed building that can be upgraded with a weapon. Unused in vanilla {{ra2}}/{{yr}}.<br /> <br /> This flag has at least two functions:<br /> # Connecting with walls. Like [[GDIGateOne|gates]], the wall tower can be placed directly on a [[wall]]. Any adjacent wall sections will also visibly connect to the tower.<br /> # Whenever the [[AI]] builds a wall tower, it will look up its next [[base nodes|base node]] that has {{f|IsBaseDefense|yes|link}} and try and place that node on top of the tower. This node should be one of the upgrades that can be placed on the tower. If the AI finds such a node but fails to place it on the tower (because the node is not actually an upgrade for the tower), it will skip placing down the node altogether.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=MissileROTVar&diff=28600 2025-06-05T13:45:46Z

<p>Crimsonum: </p> <hr /> <div>{{Flag<br /> |values={{Values|percentage}}<br /> |files={{ini|rules}}<br /> |types={{Categ|General}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies the rate of turn (ROT) fluctuation percentage of guided missiles ([[projectiles]] with {{f|ROT|link}} greater than 0). As the missile travels, its ROT is recalculated every [[frame]] based on this variable: the larger the value, the higher the variation in the missile's ROT.<br /> <br /> Note that on regular missiles the effect is barely noticable, even with extreme {{f|MissileROTVar}} values, as the ROT never falls below what's stated on the projectile's rules. The lower the projectile's default ROT, the more noticable the effect is. For example, projectiles with {{f|ROT|1|link}} and a high enough variance (e.g. 2.0) causes the projectiles to randomly scatter around the target instead of hitting it perfectly.<br /> <br /> == Pseudocode ==<br /> <br /> Simplified [[pseudocode]]:<br /> <br /> currentROT = (sin(((frame % 15) / 3) * 2 * π) * {{f|MissileROTVar}} + {{f|MissileROTVar}} + 1) * {{f|ROT|link}}<br /> <br /> == See Also ==<br /> [[MissileSpeedVar]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=MissileSpeedVar&diff=28599 2025-06-05T11:07:32Z

<p>Crimsonum: Reverted edits by Crimsonum (talk) to last revision by MarkJFox</p> <hr /> <div>{{Flag<br /> |values={{Values|float}}<br /> |files={{ini|rules}}<br /> |types={{Categ|General}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> |tsobsolete=yes<br /> }}<br /> <br /> According to the {{ini|rules}} comment, this flag would've defined the speed fluctuation percentage of guided missiles ([[projectiles]] with [[ROT]] greater than 1). It's read but not used.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=MissileROTVar&diff=28598 2025-06-05T10:31:58Z

<p>Crimsonum: Not obsolete, just barely noticable with expected values</p> <hr /> <div>{{Flag<br /> |values={{Values|percentage}}<br /> |files={{ini|rules}}<br /> |types={{Categ|General}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies the rate of turn fluctuation percentage of guided missiles ([[projectiles]] with [[ROT]] greater than 1). Increasing this value increases the maximum amplitude of the randomly fluctuating sine wave that the missiles follow, causing them to wobble as they travel.<br /> <br /> Although this flag is valid, the effect is very minuscule – even with large values like {{tt|2000}}, the flight trajectory fluctuation is barely noticable.<br /> <br /> == See Also ==<br /> [[MissileSpeedVar]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=MissileSpeedVar&diff=28597 2025-06-05T10:10:20Z

<p>Crimsonum: </p> <hr /> <div>{{Flag<br /> |values={{Values|percent}}<br /> |files={{ini|rules}}<br /> |types={{Categ|General}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies the speed fluctuation percentage of guided missiles ([[projectiles]] with [[ROT]] greater than 1).<br /> <br /> Although this flag is valid, the effect is very minuscule – even with large values like {{tt|2000}}, the speed fluctuation is barely noticable.<br /> <br /> == See Also ==<br /> [[MissileROTVar]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=MissileSpeedVar&diff=28596 2025-06-05T10:09:49Z

<p>Crimsonum: Not obsolete, just barely noticable with expected values</p> <hr /> <div>{{Flag<br /> |values={{Values|percent}}<br /> |files={{ini|rules}}<br /> |types={{Categ|General}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies the speed fluctuation percentage of guided missiles ([[projectiles]] with [[ROT]] greater than 1).<br /> <br /> Although this flag is valid, the effect is very minuscule – even with large values like {{tt|2000}}, the speed fluctuation is barely noticable.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=ScriptTypes/ScriptActions&diff=28594 2025-06-01T19:14:26Z

<p>Crimsonum: Note on Do This mission types.</p> <hr /> <div>'''Script actions''' are the steps that determine what each [[script]] ''actually'' does, in the same vein as [[Actions (maps)|actions]] determine what a [[trigger]] does.<br /> <br /> The following action types are available:<br /> <br /> {|class=&quot;wikitable&quot;<br /> !colspan=&quot;2&quot;|Parameters<br /> !rowspan=&quot;2&quot;|Description<br /> |-<br /> !P1 (Script&amp;nbsp;Action)<br /> !P2 (Argument)<br /> |-<br /> |style=&quot;text-align: center;&quot;|0<br /> |style=&quot;text-align: center;&quot;|Quarry Type#{{fnl|1}}{{fnl|2}}<br /> |'''Attack Quarry Type'''<br /> This instructs the team to approach and attack a target that fits the [[QuarryTypes|quarry type]] (target category){{fnl|1}} specified by the second parameter. Target selection from this category is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes|technotype]] override of [[TargetDistanceCoefficient]].<br /> <br /> These attack missions are inherently self-repeating. For example, when executing script action {{tt|0,2}} (&quot;attack building&quot;), the task force will attack the next [[BuildingTypes|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack (either destroyed or inaccessible), the script action is complete and the task force moves on to execute the next script action, if any.<br /> <br /> Note that the completion of this script action can get cut short in case the task force gets destroyed or runs out of ammo.<br /> <br /> The following are the quarry type values which can be used:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Quarry Type<br /> !Description<br /> |-<br /> |0<br /> |N/A<br /> |Cancel attack mission<br /> |-<br /> |1<br /> |Anything<br /> |Enemy [[TechnoTypes|vehicle, aircraft, infantry or building]]. Target selection works the same as in the &quot;Hunt&quot; mission (see action {{tt|11}} below). However, unlike in Hunt, if the team is attacked, it will retaliate and pursue the attackers, provided that the team has {{f|Suicide|no|link}}.<br /> |-<br /> |2<br /> |Structures<br /> |Enemy [[BuildingTypes|building]]<br /> |-<br /> |3<br /> |Harvesters, Refineries, and Silos /&lt;br/&gt;Ore Miners<br /> |Enemy vehicle with {{f|Harvester|yes|link}} set.&lt;br/&gt;In Tiberian Sun, this quarry also includes enemy Tiberium Refineries and Silos.<br /> |-<br /> |4<br /> |Infantry<br /> |Enemy [[InfantryTypes|infantry]]<br /> |-<br /> |5<br /> |Vehicles<br /> |Enemy [[VehicleTypes|vehicle]]<br /> |-<br /> |6<br /> |Factories<br /> |Enemy building with {{f|Factory|link}} set<br /> |-<br /> |7<br /> |Base Defenses<br /> |Enemy building with {{f|IsBaseDefense|yes|link}} set<br /> |-<br /> |8<br /> |Base Threats<br /> |Enemy [[UnitTypes|unit]] approaching (or already in) its base and which are in an attack mission<br /> |-<br /> |9<br /> |Power Plants<br /> |Enemy building with a positive {{f|Power|link}} value set<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} additions<br /> |-<br /> |10<br /> |Occupiable<br /> |Building with {{f|CanBeOccupied|yes|link}} set (usually neutral structures)<br /> |-<br /> |11<br /> |Tech Buildings<br /> |Building with {{f|NeedsEngineer|yes|link}} set (usually [[NeutralTechBuildings|neutral tech buildings]])<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|1<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Attack Waypoint'''<br /> This instructs the team to use the task force to attack the waypoint number specified by the second parameter. If any members have {{f|Infiltrate|yes|link}} set they will enter the structure at the waypoint. Members with {{f|Engineer|yes|link}} set will capture the structure provided it does not have {{f|Capturable|no|link}} set or if it has {{f|NeedsEngineer|yes|link}} set. Members with {{f|Agent|yes|link}} set will spy on the structure if it has {{f|Spyable|yes|link}} set. Members that do not have {{f|Assaulter|no|link}} set will garrison the structure if it has {{f|CanBeOccupied|yes|link}} set. Members with {{f|C4|yes|link}} set will blow up the structure if does not have {{f|CanC4|no|link}} set. If there is no building at the specified waypoint, the task force will attack the ground when reaching in range of the waypoint. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|2<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Go Berzerk'''<br /> {{obsolete|{{ts}} to {{yr}}|Go Berzerk}}<br /> Would have caused [[cyborg]] infantry in the team to go [[BerzerkAllowed|berserk]]. This action is obsolete, so the team simply moves on to the next action in the script, if present.<br /> |-<br /> |style=&quot;text-align: center;&quot;|3<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Move To Waypoint'''<br /> This instructs the team to use the task force to move to the waypoint number specified by the second parameter. Refer [[Waypoints]] for details on waypoint.<br /> <br /> '''Tip:''' You can use this action to get a team to move to waypoint no. 99 (just about every map has this defined as the center point) - that will mean it will always strive to get to the center of the map, providing a good vantage point from which to perform further actions and giving the impression that the computer is scouting for enemies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|4<br /> |style=&quot;text-align: center;&quot;|Cell#{{fnl|2}}<br /> |'''Move Into Specific Cell'''<br /> This instructs the team to use the task force to move into the Cell specified by the second parameter. Cell number in the second parameter uses formula of (Y * 128) + X. With modulus operator being used to compute the X value from the given parameter, even if the X values used in the formula is 128 or higher, the resultant X value is limited to between 0 and 127. This action can be used when you want the team to trigger a specific [[Actions_(maps)|action]] (when the game tests for the cell tag being entered). Cell tags are attached to cells and are used to trigger events and thus fire actions when that cell is entered by a unit (or any unit from the task force). Refer [[CellTags]] for details on cell tags.<br /> |-<br /> |style=&quot;text-align: center;&quot;|5<br /> |style=&quot;text-align: center;&quot;|Time{{fnl|3}}<br /> |'''Guard Area'''<br /> This instructs the team to put the task force into Guard mode for the amount of time specified. The team members will attack enemy units that fall within their weapon range, but they will not pursue enemies even when provoked. After guarding for the amount of time specified, the team will move on to execute its next script action.<br /> |-<br /> |style=&quot;text-align: center;&quot;|6<br /> |style=&quot;text-align: center;&quot;|Line#{{fnl|2}}<br /> |'''Jump To Line #'''<br /> This is used to repeat script actions within the script. The second parameter is the action ''line number'' of the [[ScriptTypes|script type]] that you want to jump to.&lt;br/&gt;'''Note''': Script action index starts at 0 whereas the line number starts at 1. So, to jump to the first script action whose index is 0, use {{tt|n=6,1}} for this script. Jump to line number could be specified to any of the preceding line numbers, not just to the first script action to create a loop of actions.<br /> |-<br /> |style=&quot;text-align: center;&quot;|7<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Player Win'''<br /> Forces a game win condition for the owner of the team (they win the game).<br /> |-<br /> |style=&quot;text-align: center;&quot;|8<br /> |style=&quot;text-align: center;&quot;|Unload Behaviour#{{fnl|2}}<br /> |'''Unload'''<br /> If the task force contains a unit or units that have a valid {{f|Passengers|link}} value set, and those units contain passengers, this command will make the units inside the transport(s) disembark. Note that once the passengers have disembarked, the transport itself is suspended until given a new mission and is therefore no longer considered a part of this task force - this means that you cannot, for example, get units to disembark, do something, then get back into the transport in the same script. The second parameter can be used to control what happens to the transport after it 'deploys' its cargo:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Description<br /> |-<br /> |0<br /> |Keep transports and units - all remain in the team and execute the remainder of the script<br /> |-<br /> |1<br /> |Keep transport and lose the units - only the transport will execute the remainder of the script<br /> |-<br /> |2<br /> |Lose transport and keep units - only the units will execute the remainder of the script<br /> |-<br /> |3<br /> |Lose transports and lose units - nothing executes the remainder of the script<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|9<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Deploy'''<br /> If the task force contains a unit or units that are able to deploy (for example a unit which {{f|DeploysInto|link}} a [BuildingType] or has any of {{f|Deployer|yes|link}}, {{f|DeployFire|yes|link}}, {{f|DeployToFire|yes|link}} set) then this action causes them to deploy at the current cell they are occupying (same effect as selecting a unit and pressing the Deploy key as defined in KEYBOARD.INI or clicking the relevant button on the Advanced Command Bar).<br /> |-<br /> |style=&quot;text-align: center;&quot;|10<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Follow Friendlies'''<br /> This command causes the task force to follow the nearest friendly unit when it moves although it will not function as if it is 'guarding' the unit. The following is not permanent, when the task force is assigned another mission it abandons the following.<br /> <br /> '''Tip''': If the secondary (support) team has this as the first line in its [[ScriptTypes|script]], then it will escort the primary team.<br /> |-<br /> |style=&quot;text-align: center;&quot;|11<br /> |style=&quot;text-align: center;&quot;|Mission#{{fnl|2}}<br /> |'''Assign New Mission'''<br /> The objects in the task force are assigned the [[Mission Control|mission]] defined by the second parameter.<br /> <br /> Not all of the available mission types are applicable to teams; those that are, such as {{tt|Sleep}}, {{tt|Sticky}}, {{tt|Guard}}, {{tt|Area Guard}}, {{tt|Hunt}}, are perpetual by nature so once assigned to a team, the units in the team will remain in that mission until those units are destroyed, the team is dissolved, or the units are recruited into another team and given a different mission. Because the missions are never-ending, this script action can't finish and move to the next script action. Thus, this script action is best given as the last script action in the script.<br /> <br /> Note that unlike some of the other team missions, teams in these missions do not respond to attacks in a coordinated manner. That is, if one member of the team is attacked by an enemy, it will not provoke the other members of the team to respond unless they themselves are attacked.<br /> <br /> The following are valid settings for the second parameter:<br /> {|class=&quot;wikitable&quot;<br /> |-<br /> !Value<br /> !Name<br /> !Description<br /> |-<br /> !colspan=&quot;3&quot;|{{ts}} and {{fs}}<br /> |-<br /> |0<br /> |Sleep<br /> |object sits around and plays dead, will not acquire targets<br /> |-<br /> |1<br /> |Attack<br /> |special attack mission used by AI team types (utilizes threat rating logic)<br /> |-<br /> |2<br /> |Move<br /> |simply moving to destination<br /> |-<br /> |3<br /> |QMove<br /> |special move to destination after other queued moves occur<br /> |-<br /> |4<br /> |Retreat<br /> |object runs away (may even leave the map)<br /> |-<br /> |5<br /> |Guard<br /> |object sits around and will engage and pursue an enemy that falls within its weapon range or attacks it<br /> |-<br /> |6<br /> |Sticky<br /> |just like guard mode, except the object will engage enemies but not pursue them<br /> |-<br /> |7<br /> |Enter<br /> |enter building or transport<br /> |-<br /> |8<br /> |Capture<br /> |engineer entry logic used by {{f|MultiEngineer|link}}<br /> |-<br /> |9<br /> |Harvest<br /> |the loop controlling harvesting of tiberium and dumping at a Refinery<br /> |-<br /> |10<br /> |Area Guard<br /> |guard the general area where the object starts at<br /> |-<br /> |11<br /> |Return<br /> |return to co-ordinating object (e.g. spawned object returns to the spawner)<br /> |-<br /> |12<br /> |Stop<br /> |stop moving or firing at the first available opportunity<br /> |-<br /> |13<br /> |Ambush<br /> |force fire (units with Infiltrate=yes will enter target if possible)<br /> |-<br /> |14<br /> |Hunt<br /> |scan for and attack enemies wherever they may be on the map. Chooses the target based on threat or first built. See [[TargetDistanceCoefficientDefault]] for more information. Will not retaliate if attacked.<br /> |-<br /> |15<br /> |Unload<br /> |while dropping off cargo<br /> |-<br /> |16<br /> |Sabotage<br /> |unit runs to place C4 on a building<br /> |-<br /> |17<br /> |Construction<br /> |structures use this when building up after initial placement<br /> |-<br /> |18<br /> |Selling<br /> |structures use this for deconstruction after being sold<br /> |-<br /> |19<br /> |Repair<br /> |used when repairing an object (e.g. Service Depot)<br /> |-<br /> |20<br /> |Rescue<br /> |special team over-ride mission<br /> |-<br /> |21<br /> |Missile<br /> |nuke Silo special launch missile mission<br /> |-<br /> |22<br /> |Harmless<br /> |object doesn't fire and is not considered in any threat scan<br /> |-<br /> |23<br /> |Open<br /> |while opening or closing a gate to allow passage<br /> |-<br /> |24<br /> |Patrol<br /> |patrol a series of waypoints<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} and {{Yr}}<br /> |-<br /> |0<br /> |Sleep<br /> |object sits around and plays dead, will not acquire targets<br /> |-<br /> |1<br /> |Attack<br /> |special attack mission used by AI team types (utilizes threat rating logic)<br /> |-<br /> |2<br /> |Move<br /> |simply moving to destination<br /> |-<br /> |3<br /> |QMove<br /> |special move to destination after other queued moves occur<br /> |-<br /> |4<br /> |Retreat<br /> |object runs away (may even leave the map)<br /> |-<br /> |5<br /> |Guard<br /> |object sits around and will engage an enemy that falls within its weapon range<br /> |-<br /> |6<br /> |Sticky<br /> |just like guard mode, except the object will engage enemies but not pursue them<br /> |-<br /> |7<br /> |Enter<br /> |enter building or transport<br /> |-<br /> |8<br /> |Capture<br /> |engineer entry logic used by {{f|MultiEngineer|link}}<br /> |-<br /> |9<br /> |Eaten<br /> |unit enters a [[Grinding|grinder]]<br /> |-<br /> |10<br /> |Harvest<br /> |the loop controlling harvesting of Ore and dumping at a Refinery<br /> |-<br /> |11<br /> |Area Guard<br /> |guard the general area where the object starts at<br /> |-<br /> |12<br /> |Return<br /> |return to co-ordinating object (e.g. spawned object returns to the spawner)<br /> |-<br /> |13<br /> |Stop<br /> |stop moving or firing at the first available opportunity<br /> |-<br /> |14<br /> |Ambush<br /> |force fire (units with {{f|Infiltrate|yes|link}} will enter target if possible)<br /> |-<br /> |15<br /> |Hunt<br /> |scan for and attack enemies wherever they may be on the map<br /> |-<br /> |16<br /> |Unload<br /> |while dropping off cargo (e.g. Landing Craft unloading passengers)<br /> |-<br /> |17<br /> |Sabotage<br /> |unit runs to place C4 on a building or Ivan goes to place bomb on object<br /> |-<br /> |18<br /> |Construction<br /> |structures use this when building up after initial placement<br /> |-<br /> |19<br /> |Selling<br /> |structures use this for deconstruction after being sold<br /> |-<br /> |20<br /> |Repair<br /> |used when repairing an object (e.g. Service Depot)<br /> |-<br /> |21<br /> |Rescue<br /> |special team over-ride mission<br /> |-<br /> |22<br /> |Missile<br /> |nuke silo special launch missile mission<br /> |-<br /> |23<br /> |Harmless<br /> |object doesn't fire and is not considered in any threat scan<br /> |-<br /> |24<br /> |Open<br /> |while opening or closing a gate to allow passage<br /> |-<br /> |25<br /> |Patrol<br /> |patrol a series of waypoints<br /> |-<br /> |26<br /> |Paradrop Approach<br /> |object is approaching the paradrop site<br /> |-<br /> |27<br /> |Paradrop Overfly<br /> |object is flying over the paradrop site (i.e. dropping the paratroopers)<br /> |-<br /> |28<br /> |Wait<br /> |paused and awaiting next mission<br /> |-<br /> |29<br /> |Attack (again)<br /> |(special duplicate) used when units are deployed to fire (e.g. weapons with an area fire effect)<br /> |-<br /> !colspan=&quot;3&quot;|{{Yr}} additions<br /> |-<br /> |30<br /> |Spyplane Approach<br /> |object is flying towards target<br /> |-<br /> |31<br /> |Spyplane Overfly<br /> |object is flying over the target<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|12<br /> |style=&quot;text-align: center;&quot;|Global Variable#{{fnl|2}}<br /> |'''Set Global Variable'''<br /> The [[VariableNames|global variable]] number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only. This is part of the boolean logic employed by the global variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|13<br /> |style=&quot;text-align: center;&quot;|Sequence#{{fnl|2}}<br /> |'''Play Idle Anim Sequence'''<br /> If the task force contains a unit or units that use SHP graphics (i.e. infantry) then the relevant idle SHP sequence is displayed as defined by the frame numbering system in ART.INI. Parameter 0 for Idle1 and 1 for Idle2.<br /> |-<br /> |style=&quot;text-align: center;&quot;|14<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Load Onto Transport'''<br /> If the task force contains a unit or units that have a valid {{f|Passengers|link}} value set, and units whose {{f|Size|link}} and {{f|PhysicalSize|link}} settings allow them to be carried by that transport, this command will make the units enter the transport.<br /> |-<br /> |style=&quot;text-align: center;&quot;|15<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Spy On Structure At Waypoint'''<br /> Should be used only for units with {{f|Infiltrate|yes|link}} and {{f|Agent|yes|link}} set. This instructs the task force to enter the structure at the waypoint number specified by the second parameter and spy on the structure if it has {{f|Spyable|yes|link}} set. If there is no building at the specified waypoint, the task force may not activate correctly and will just remain in their last mission. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|16<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Patrol To Waypoint'''<br /> This is similar to Move to waypoint. This instructs the team to use the task force to move to the waypoint number specified by the second parameter. The difference is that the units in the task force will move out of their patrol route to actively go and engage any enemy objects that are within their {{f|Sight|link}} as they move to the waypoint.<br /> <br /> '''Note''': This patrol mission eats up processor time, because the task force will scan for enemy objects with each movement. If you have a lot of task forces (or lots of units in them) engaged in this mission, you will experience slowdown in the game - this is one reason why the single player missions are comparatively slow, they use this mission a lot. The rate at which the scanning for targets whilst in this mission is controlled by the {{f|PatrolScan|link}} statement in the [AI]section of RULES.INI. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|17<br /> |style=&quot;text-align: center;&quot;|Script#{{fnl|2}}<br /> |'''Change Script'''<br /> {{obsolete|{{ts}}|Change Script}}<br /> Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes|script type]] to execute as listed in the {{tt|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).<br /> <br /> Appears not to work, at least in Tiberian Sun.<br /> |-<br /> |style=&quot;text-align: center;&quot;|18<br /> |style=&quot;text-align: center;&quot;|Team#{{fnl|2}}<br /> |'''Change Team'''<br /> This instructs the task force to switch to another team. The second parameter specifies the number of the [[TeamTypes|team type]] to switch to as listed in the {{tt|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).<br /> <br /> {{W}} '''Note:''' The game loads team types from {{ini|ai}} first, then [[aifs.ini]] second ([[RequiredAddOn|if applicable]]), and the current map last. Because this action refers to a team by its index, it's prone to break as the index will change whenever you add or remove teams from any of the AI [[INIs]]. Therefore it is ''not'' recommended to use this action. A much more reliable method is to use [[Actions_(maps)|trigger actions]] to recruit the units to a new team, as triggers refer to teams by their names, not indexes.<br /> |-<br /> |style=&quot;text-align: center;&quot;|19<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Panic'''<br /> If the task force contains a unit or units that have {{f|Fraidycat|yes|link}} set then they will run around aimlessly, using the {{f|Panic}} animation from their sequence as defined in ART.INI. Normally used for the civilian units. Units that do not fulfil this criteria lie down and act as if prone.<br /> |-<br /> |style=&quot;text-align: center;&quot;|20<br /> |style=&quot;text-align: center;&quot;|House#{{fnl|2}}<br /> |'''Change House Ownership'''<br /> Used in single player missions on specific map files only, this changes ownership of the entire team to the house number specified by the second parameter.<br /> |-<br /> |style=&quot;text-align: center;&quot;|21<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Scatter'''<br /> This instructs the task force to scatter (same effect as selecting a group of units and pressing the Scatter key as defined in [[Keyboard.ini|KEYBOARD.INI]]).<br /> |-<br /> |style=&quot;text-align: center;&quot;|22<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Afraid &amp;amp; Run To Shroud'''<br /> This instructs the task force to behave in a scared manner and it will run to the nearest shrouded cell. The task force will not actively engage in combat, will not acquire targets and will not retaliate (it will scatter instead if attacked).<br /> |-<br /> |style=&quot;text-align: center;&quot;|23<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Player Loss'''<br /> Forces a game loss condition for the owner of the team (they lose the game).<br /> |-<br /> |style=&quot;text-align: center;&quot;|24<br /> |style=&quot;text-align: center;&quot;|Speech#{{fnl|2}}<br /> |'''Play Speech'''<br /> This instructs the task force to play one of the Sofia or EVA voices (depending upon the {{f|ParentCountry|link}} or the owner of this task force). The second parameter is the number of the sound to be played from the [DialogList] in the [[Eva.ini|EVA.INI]] (note that you should consider this list as being numbered from 0 instead of 1 to get the correct numbering convention).<br /> |-<br /> |style=&quot;text-align: center;&quot;|25<br /> |style=&quot;text-align: center;&quot;|Sound#{{fnl|2}}<br /> |'''Play Sound'''<br /> This instructs the task force to play one of the generic in game sounds from the {{sl|SoundList}} in the [[Sounds.ini|SOUNDS.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|26<br /> |style=&quot;text-align: center;&quot;|Movie#{{fnl|2}}<br /> |'''Play Movie'''<br /> This instructs the task force to play one of the movies from the {{sl|Movies}} list in the [[Art.ini|ART.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|27<br /> |style=&quot;text-align: center;&quot;|Theme#{{fnl|2}}<br /> |'''Play Theme'''<br /> This instructs the task force to play one of the game soundtracks from the {{sl|Themes}} list in the [[Theme.ini|Theme.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|28<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Reduce Tiberium/Ore'''<br /> Reduces the amount of Tiberium/Ore in the cell that the team is occupying. Used by the special 'weapon' that is inherent with Harvesters/Ore Miners.<br /> |-<br /> |style=&quot;text-align: center;&quot;|29<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Begin Production'''<br /> Forces the owner of the team to begin the auto-production process (the AI's behaviour in skirmish games). Should only be used on AI controlled houses.<br /> |-<br /> |style=&quot;text-align: center;&quot;|30<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Sale'''<br /> Forces the 'fire sale' of all remaining structures owned by the [[house]] to which the team belongs.<br /> |-<br /> |style=&quot;text-align: center;&quot;|31<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Suicide'''<br /> This instructs the task force to destroy itself. In effect it commits suicide, usually accompanied by an explosion.<br /> |-<br /> |style=&quot;text-align: center;&quot;|32<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Start Storm In...'''<br /> Initiates an Ion Storm (TS) or Weather Storm (RA2) after the time specified. In {{Ra2}}, this initiates the Weather Storm intro effect (when the screen goes dark prior to the clouds appearing). The effect is set to be delayed by the number of seconds specified by parameter 2.<br /> |-<br /> |style=&quot;text-align: center;&quot;|33<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''End Storm'''<br /> This forces an end to the active Ion Storm or Weather Storm.<br /> |-<br /> |style=&quot;text-align: center;&quot;|34<br /> |style=&quot;text-align: center;&quot;|Speed#{{fnl|2}}<br /> |'''Center Map On Team'''<br /> This will center the screen on the team. The same effect as hitting the Home key as defined in [[Keyboard.ini|KEYBOARD.INI]] when the screen centers on your MCV (or the unit defined by the {{f|BaseUnit|link}} statement in RULES.INI). The second parameter determines the speed at which the 'camera' switches view to the task force with 0 being slow to 4 being fast.<br /> |-<br /> |style=&quot;text-align: center;&quot;|35<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Shroud Map For Time Interval'''<br /> This action will shroud the entire map except for the area revealed by the player's own and/or friendly units. The second parameter determines the number of [[frames]] for which the map should remain shrouded after which the explored areas are revealed again.<br /> |-<br /> |style=&quot;text-align: center;&quot;|36<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Reveal Map For Time Interval'''<br /> This action will reveal the entire map. The second parameter determines the number of [[frames]] for which the map should remain revealed after which the map is shrouded again.<br /> |-<br /> |style=&quot;text-align: center;&quot;|37<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Delete Team Members'''<br /> Deletes members of this task force from the map.<br /> |-<br /> |style=&quot;text-align: center;&quot;|38<br /> |style=&quot;text-align: center;&quot;|Global Variable#{{fnl|2}}<br /> |'''Clear Global Variable'''<br /> The [[VariableNames|global variable]] number specified in the second parameter is defined as being 'clear' (it is allocated a value of '0' or 'false'). This should be employed in specific map files only in which the global variable has been defined. This is part of the boolean logic employed by the global variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|39<br /> |style=&quot;text-align: center;&quot;|Local Variable#{{fnl|2}}<br /> |'''Set Local Variable'''<br /> The [[VariableNames|local variable]] number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only in which the local variable has been defined. This is part of the boolean logic employed by the local variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|40<br /> |style=&quot;text-align: center;&quot;|Local Variable#{{fnl|2}}<br /> |'''Clear Local Variable'''<br /> The [[VariableNames|local variable]] number specified in the second parameter is defined as being 'cleared' (it is allocated a value of '0' or 'false'). This should be employed in specific map files only in which the local variable has been defined. This is part of the boolean logic employed by the local variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|41<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Unpanic'''<br /> If the task force contains a unit or units that have {{f|Fraidycat|yes|link}} set which are currently assigned the {{f|Panic}}= sequence then this action nullifies that effect and the unit(s) adopt their default behaviour.<br /> |-<br /> |style=&quot;text-align: center;&quot;|42<br /> |style=&quot;text-align: center;&quot;|Direction#{{fnl|2}}<br /> |'''Change Facing'''<br /> This instructs the task force to turn and face the new direction specified by the second parameter. The facings are as follows:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Direction Type{{fnl|5}}<br /> !Direction<br /> |-<br /> |0<br /> |North<br /> |Top-Right<br /> |-<br /> |1<br /> |North-East<br /> |Right<br /> |-<br /> |2<br /> |East<br /> |Bottom-Right<br /> |-<br /> |3<br /> |South-East<br /> |Bottom<br /> |-<br /> |4<br /> |South<br /> |Bottom-Left<br /> |-<br /> |5<br /> |South-West<br /> |Left<br /> |-<br /> |6<br /> |West<br /> |Top-Left<br /> |-<br /> |7<br /> |North-West<br /> |Top<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|43<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Wait Until Fully Loaded'''<br /> This is always used after members of the task force have entered a transport in the same task force and serves two purposes. The effect of this is that the transport will be used to carry out any subsequent movement or deploy actions but after that it is no longer considered a part of this task force and as such is available to be recruited into new teams. It is this action which enables use of the {{f|TransportsReturnOnUnload|yes|link}} statement in the corresponding team type entry. The second purpose is to flag the transport as being 'loaded' with passengers and thus is considered in the AI's targeting logic as a potential threat (see the {{f|ContentScan|link}} entry in the RULES.INI). This action also orders the transport to wait until it is fully loaded before executing any subsequent script actions.<br /> |-<br /> |style=&quot;text-align: center;&quot;|44<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Unload Truck (TRUCKB to TRUCKA)'''<br /> Used purely for a graphical effect and applicable uniquely to the [TRUCKB] unit, this has the effect of converting [TRUCKB] into [TRUCKA] to give the impression that the unit has unloaded its cargo.<br /> '''Note''': May not work correctly in Red Alert 2 since [TRUCKA] refers to the Demo Truck image which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic.<br /> |-<br /> |style=&quot;text-align: center;&quot;|45<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Load Truck (TRUCKA to TRUCKB)'''<br /> Used purely for a graphical effect and applicable uniquely to the [TRUCKA] unit, this has the effect of converting [TRUCKA] into [TRUCKB] to give the impression that the unit has been loaded with cargo.<br /> '''Note''': May not work correctly in Red Alert 2 since [TRUCKA] refers to the Demo Truck image which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic.<br /> |-<br /> |style=&quot;text-align: center;&quot;|46<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Attack Enemy Structure'''<br /> Members of this task force attack the enemy structure specified by the second parameter. This action depends upon the type of units in the task force and if certain members have {{f|Infiltrate|yes|link}} set. Members with {{f|Engineer|yes|link}} set will capture the structure provided it does not have {{f|Capturable|no|link}} set or if it has {{f|NeedsEngineer|yes|link}} set. Members with {{f|Agent|yes|link}} set will spy on the structure if it has {{f|Spyable|yes|link}} set. Members that do not have {{f|Assaulter|no|link}} set will garrison the structure if it has {{f|CanBeOccupied|yes|link}} set. Members with {{f|C4|yes|link}} set will blow up the structure if does not have {{f|CanC4|no|link}} set.<br /> |-<br /> |style=&quot;text-align: center;&quot;|47<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Move To Enemy Structure'''<br /> Members of this task force move and stay adjacent to the enemy structure specified by the second parameter.<br /> |-<br /> |style=&quot;text-align: center;&quot;|48<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Scout'''<br /> Causes members of this task force to move to a pre-determined point on the map in an attempt to scout an area. The effect is that the task force will move in one randomly chosen direction until it is no longer able to do so which can make it very useful or a waste of time depending on the direction chosen. If you want to continually scout the map, you should loop this script action.<br /> |-<br /> |style=&quot;text-align: center;&quot;|49<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Register Success'''<br /> Executing this script action even once in a script by its task force is considered as a success. A script not containing this script action is a fail for its task force. A script containing this script action but the task force being unable to reach and execute this action even once is a fail. These success and failure are used to adjust the current weight defined in AITriggers. Refer [[AITriggerTypes#Weights|AITriggerType's weights]].<br /> |-<br /> |style=&quot;text-align: center;&quot;|50<br /> |style=&quot;text-align: center;&quot;|Time Frames<br /> |'''Flash'''<br /> This causes all members of the task force to 'flash', the visual effect you get on an object when you order something to attack it. The second parameter is the number of time [[frames]] to flash the unit 'white'.<br /> |-<br /> |style=&quot;text-align: center;&quot;|51<br /> |style=&quot;text-align: center;&quot;|Animation#{{fnl|2}}<br /> |'''Play Animation'''<br /> This instructs the task force to play one of the animations from the {{sl|Animations}} list.<br /> |-<br /> !colspan=&quot;3&quot;|{{fs}} addition<br /> |-<br /> |style=&quot;text-align: center;&quot;|52<br /> |style=&quot;text-align: center;&quot;|Talk Bubble#{{fnl|2}}<br /> |'''Display Talk Bubble'''<br /> Should be used for single-unit task forces only, this causes a 'talk bubble' to appear above the unit. The second parameter determines which type of talk bubble to display. By default, the game has only three talk bubbles, though it's possible to add more and change what the bubbles represent:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Bubble<br /> |-<br /> |1<br /> |* (generic speech)<br /> |-<br /> |2<br /> |? (question, confusion)<br /> |-<br /> |3<br /> |! (alert, attention, shout)<br /> |}<br /> <br /> '''Note''': The length of time for which the talk bubble is displayed is controlled through the {{f|TalkBubbleTime|link}} statement in RULES.INI. Refer to the RULES.INI Guide for details of this and the steps to take to enable its inclusion in Red Alert 2.<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} additions<br /> |-<br /> |style=&quot;text-align: center;&quot;|53<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Gather (At Enemy Base)'''<br /> This causes the task force to gather together (sometimes used when members of the task force move at different speeds and you want the faster ones to stop while the slower ones catch up) after the previous script action has been executed. If the task force is in an attack mission and moving towards an enemy base, this command is usually executed when the first member of the task force reaches the distance from that base defined by the {{f|AISafeDistance|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|54<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Regroup (At Friendly Base)'''<br /> This causes the task force to regroup, if for example any of its members have become engaged in a base defense mission or strayed away whilst in guard mode, or even the team itself has been suspended for whatever reason. The members regroup directly next to each other leaving no 'gaps' at the nearest available point with sufficient space, and is used, for example, prior to activating the Iron Curtain so that all applicable members are affected (i.e. they fall within its range of effect).<br /> |-<br /> |style=&quot;text-align: center;&quot;|55<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Activate Iron Curtain On Task Force'''<br /> If the owner of the task force to which this script is attached also has the Iron Curtain fully charged then it will be fired at this task force. Note that the use of the Iron Curtain in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|56<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Chronoshift Task Force to a building'''<br /> If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to the enemy structure specified by the second parameter, before moving on to the next script action. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|57<br /> |style=&quot;text-align: center;&quot;|Quarry Type#{{fnl|2}}<br /> |'''Chronoshift Task Force to a target type'''<br /> If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to a target that fits the [[QuarryTypes|quarry type]] (target category) specified by the second parameter, before moving on to the next script action. Target selection is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes|technotype]] override of [[TargetDistanceCoefficient]]. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|58<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Move To Friendly Structure'''<br /> Members of this task force move and stay adjacent to the friendly structure specified by the second parameter. The structure can be one owned by the owner of the task force or any of its allies.<br /> |-<br /> !colspan=&quot;3&quot;|{{Yr}} additions<br /> |-<br /> |style=&quot;text-align: center;&quot;|59<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Attack Structure At Waypoint'''<br /> Members of this task force attack the structure at the waypoint specified by the second parameter. This script action is very similar to script action no. {{tt|43}} although this action does not test for ownership of the structure itself - thus the inclusion of this action allows, for example, InfantryTypes with {{f|Engineer|yes|link}} set to enter structures owned by the same side for the purposes of repair. This would be the most appropriate action to use to get the AI to repair bridges. Use of this also means that the task force will attack the structure with one of its weapons meaning, for example, that units with {{f|C4|yes|link}} set will not C4 the building but shoot at it instead. This is useful if you want to get a task force to destroy a nearby occupiable structure instead of entering it in a bid to prevent the enemy getting hold of it - a tactic used in the Yuri's Revenge AI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|60<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Enter Grinder'''<br /> Members of this task force will enter the nearest structure with {{f|Grinding|yes|link}} set if it is owned by the owner of the task force or any of its allies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|61<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Occupy Tank Bunker'''<br /> Any VehicleType members of this task force which do not have {{f|Bunkerable|no|link}} set will enter the nearest vacant structure with {{f|Bunker|yes|link}} set if it is owned by the owner of the task force or any of its allies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|62<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Enter Bio Reactor'''<br /> Any InfantryType members of this task force will enter the nearest structure with {{f|InfantryAbsorb|yes|link}} set if it is owned by the owner of the task force or any of its allies and has space available.<br /> |-<br /> |style=&quot;text-align: center;&quot;|63<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Occupy Battle Bunker'''<br /> Any InfantryType members of this task force with {{f|Occupier|yes|link}} set will enter the nearest structure (which they own) with {{f|CanOccupyFire|yes|link}} set.<br /> |-<br /> |style=&quot;text-align: center;&quot;|64<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Garrison Structure'''<br /> Any InfantryType members of this task force with {{f|Occupier|yes|link}} set will enter the nearest (neutral) structure with {{f|CanOccupyFire|yes|link}} set. This script action is used specifically for this purpose due to action no. {{tt|59}} (see above) since the logic in Yuri's Revenge has changed so that the unit's weapon is transferred to the structure. Use of this action also allows the computer to repair those structures by sending an InfantryType with {{f|Engineer|yes|link}} set into them and also allows the AI to differentiate between attacking such a structure and entering it, which is useful if you want the AI to use infantry to destroy an occupiable structure thus preventing its enemy from using it.<br /> |}<br /> <br /> {{fn|1|[https://en.wiktionary.org/wiki/quarry#Etymology_2 Quarry] as in the sense of prey or target, not mine.}}<br /> {{fn|2|For convenience, the &quot;#&quot; symbol refers to a number/index of the object type. For example, &quot;Waypoint#&quot; refers to the index number of the Waypoint in the [[Waypoints]] list.}}<br /> {{fn|3|Time to guard area. In {{ts}}, the time is measured in seconds at default game speed (15 FPS). In {{ra2}} and {{yr}}, the time is measured in tenths of a minute (multiples of 6 seconds) at normal game speed.}}<br /> {{fn|4|'''B'''uilding '''w'''ith '''P'''roperty is the computed value of the building's index in [[BuildingTypes]] and the AI's choice for target selection. See the [[#Notes|notes]] below for more information.}}<br /> {{fn|5|Note that the internal &quot;compass&quot; is tilted due to the game's dimetric projection, i.e. internal North is top-right, North-East is right, etc.}}<br /> <br /> ==Notes==<br /> <br /> '''Building with Property (BwP) number'''<br /> <br /> This number allows the AI to target a specific instance of a building based on threat or distance when there are multiple instances of the specified building. When there is only one instance of a specified building then there is only one building to select, so the outcome based on options of threat or distance is the same. The computation of this building number is as follows: &lt;br/&gt;<br /> <br /> {|class=&quot;wikitable&quot;<br /> !Computed Value<br /> !Description<br /> |-<br /> |0 (Hex {{tt|0x0}}) + Building Index<br /> |Select the instance of the building with least threat<br /> |-<br /> |65536 (Hex {{tt|0x10000}}) + Building Index<br /> |Select the instance of the building with highest threat<br /> |-<br /> |131072 (Hex {{tt|0x20000}}) + Building Index<br /> |Select the instance of the building which is nearest<br /> |-<br /> |196608 (Hex {{tt|0x30000}}) + Building Index<br /> |Select the instance of the building which is farthest<br /> |}<br /> <br /> Reference to a building number exceeding the buildings in the [[BuildingTypes]] list or using number 262144 or higher, results in a do-nothing script action and the team will move on to execute its next script action.<br /> <br /> Threat posed by any number of instances of the same building will all be the same. So, to determine which instance of a building has higher or lower threat, its cumulative threat value is used. For example, if there are some units near a building, its threat rating becomes higher with the additional threat values of the nearby units.<br /> <br /> In cases where multiple instances of the specified building have equal threat or are equidistant, AI will choose the one which was constructed first by the target side. If the first was destroyed/sold etc., then the next constructed building becomes target. Friendlies don't pose threat, so it becomes a case of equal threat.<br /> <br /> '''Example of BwP number computation:''' to make the AI team members select their nearest enemy Allied War Factory, look for the 0-based index of the GAWEAP in the [[BuildingTypes]] list (7), add 131072, and use the resulting structure number as the script action parameter: 7 + 131072 = '''131079'''.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Stray&diff=28593 2025-06-01T19:06:37Z

<p>Crimsonum: </p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=rules}}<br /> |types={{Categ|General}}<br /> |values={{values|float}}<br /> |ra=yes<br /> |cs=yes<br /> |am=yes<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Radius, in [[cells]], that AI-controlled [[team]] [[TaskForces|members]] can stray from their position without causing them to regroup. This stops the AI teams from breaking up too much which would render their collective purpose useless.<br /> <br /> == Use Cases ==<br /> In practice, this flag seems to apply only in the following cases:<br /> === Guard ===<br /> When a team is set to the [[ScriptActions|{{tt|Guard}}]] mission, if any of the team members stray from the group more than this distance to pursue an enemy (because the enemy either attacked them or entered their weapon range), the remaining units in the team will follow suit. Note that the followers will not automatically engage the enemy unless they themselves are provoked.<br /> <br /> === Distance to Target ===<br /> {{tt|Stray}} also determines the minimum distance between a team's origin and its destination for the team to actually move there. If the distance is this or less, then the team will assume it's already in its destination and will not move further.<br /> <br /> In other words, if you create or reinforce a team at a [[waypoint]], and in the team's [[script]] you have that team move to another waypoint or target that's within this many cells from the team's origin waypoint, then the team thinks it's already reached its destination and will proceed to the next [[team missions|mission]] in the script.<br /> <br /> == See Also ==<br /> * [[CloseEnough]]<br /> <br /> [[Category:Map Information]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=GuardSlower&diff=28592 2025-06-01T19:04:57Z

<p>Crimsonum: I tested this thoroughly in TS, with various task forces and team missions. I could not observe any effect.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=ai}}, {{Categ|maps}}<br /> |values={{Values|boolean}}<br /> |types={{Categ|TeamTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> |tsobsolete=yes<br /> }}<br /> {{RevEng}}<br /> <br /> Specifies whether or not this team should stick close to one of its special members (hence the flag name, &quot;guard [the] slower [unit]&quot;). Assumes that the [[TaskForce|task force]] contains a specific kind of unit: the unit must be unarmed, [[TechLevel|unbuildable]], ''or'' [[DeploysInto|deployable]]. The rest of the team will then stick close to it (their [[stray]] distance is divided by 3).<br /> <br /> However, this doesn't appear to work, at least in {{ts}}.<br /> <br /> ==See Also==<br /> * [[Stray]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Annoyance&diff=28591 2025-06-01T18:17:21Z

<p>Crimsonum: I tested this thoroughly in TS, with various task forces and team missions. I could not observe any effect.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=ai}}, {{Categ|maps}}<br /> |values={{Values|boolean}}<br /> |types={{Categ|TeamTypes}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> |tsobsolete=yes<br /> }}<br /> {{RevEng}}<br /> This flag should make the team retreat and regroup when attacked. However, it doesn't appear to work, at least in {{ts}}.<br /> <br /> ==See also==<br /> * [[Aggressive]]<br /> * [[Suicide]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=ScriptTypes/ScriptActions&diff=28590 2025-05-31T19:47:04Z

<p>Crimsonum: Note on various guard missions</p> <hr /> <div>'''Script actions''' are the steps that determine what each [[script]] ''actually'' does, in the same vein as [[Actions (maps)|actions]] determine what a [[trigger]] does.<br /> <br /> The following action types are available:<br /> <br /> {|class=&quot;wikitable&quot;<br /> !colspan=&quot;2&quot;|Parameters<br /> !rowspan=&quot;2&quot;|Description<br /> |-<br /> !P1 (Script&amp;nbsp;Action)<br /> !P2 (Argument)<br /> |-<br /> |style=&quot;text-align: center;&quot;|0<br /> |style=&quot;text-align: center;&quot;|Quarry Type#{{fnl|1}}{{fnl|2}}<br /> |'''Attack Quarry Type'''<br /> This instructs the team to approach and attack a target that fits the [[QuarryTypes|quarry type]] (target category){{fnl|1}} specified by the second parameter. Target selection from this category is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes|technotype]] override of [[TargetDistanceCoefficient]].<br /> <br /> These attack missions are inherently self-repeating. For example, when executing script action {{tt|0,2}} (&quot;attack building&quot;), the task force will attack the next [[BuildingTypes|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack (either destroyed or inaccessible), the script action is complete and the task force moves on to execute the next script action, if any.<br /> <br /> Note that the completion of this script action can get cut short in case the task force gets destroyed or runs out of ammo.<br /> <br /> The following are the quarry type values which can be used:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Quarry Type<br /> !Description<br /> |-<br /> |0<br /> |N/A<br /> |Cancel attack mission<br /> |-<br /> |1<br /> |Anything<br /> |Enemy [[TechnoTypes|vehicle, aircraft, infantry or building]]. Target selection works the same as in the &quot;Hunt&quot; mission (see action {{tt|11}} below). However, unlike in Hunt, if the team is attacked, it will retaliate and pursue the attackers, provided that the team has {{f|Suicide|no|link}}.<br /> |-<br /> |2<br /> |Structures<br /> |Enemy [[BuildingTypes|building]]<br /> |-<br /> |3<br /> |Harvesters, Refineries, and Silos /&lt;br/&gt;Ore Miners<br /> |Enemy vehicle with {{f|Harvester|yes|link}} set.&lt;br/&gt;In Tiberian Sun, this quarry also includes enemy Tiberium Refineries and Silos.<br /> |-<br /> |4<br /> |Infantry<br /> |Enemy [[InfantryTypes|infantry]]<br /> |-<br /> |5<br /> |Vehicles<br /> |Enemy [[VehicleTypes|vehicle]]<br /> |-<br /> |6<br /> |Factories<br /> |Enemy building with {{f|Factory|link}} set<br /> |-<br /> |7<br /> |Base Defenses<br /> |Enemy building with {{f|IsBaseDefense|yes|link}} set<br /> |-<br /> |8<br /> |Base Threats<br /> |Enemy [[UnitTypes|unit]] approaching (or already in) its base and which are in an attack mission<br /> |-<br /> |9<br /> |Power Plants<br /> |Enemy building with a positive {{f|Power|link}} value set<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} additions<br /> |-<br /> |10<br /> |Occupiable<br /> |Building with {{f|CanBeOccupied|yes|link}} set (usually neutral structures)<br /> |-<br /> |11<br /> |Tech Buildings<br /> |Building with {{f|NeedsEngineer|yes|link}} set (usually [[NeutralTechBuildings|neutral tech buildings]])<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|1<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Attack Waypoint'''<br /> This instructs the team to use the task force to attack the waypoint number specified by the second parameter. If any members have {{f|Infiltrate|yes|link}} set they will enter the structure at the waypoint. Members with {{f|Engineer|yes|link}} set will capture the structure provided it does not have {{f|Capturable|no|link}} set or if it has {{f|NeedsEngineer|yes|link}} set. Members with {{f|Agent|yes|link}} set will spy on the structure if it has {{f|Spyable|yes|link}} set. Members that do not have {{f|Assaulter|no|link}} set will garrison the structure if it has {{f|CanBeOccupied|yes|link}} set. Members with {{f|C4|yes|link}} set will blow up the structure if does not have {{f|CanC4|no|link}} set. If there is no building at the specified waypoint, the task force will attack the ground when reaching in range of the waypoint. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|2<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Go Berzerk'''<br /> {{obsolete|{{ts}} to {{yr}}|Go Berzerk}}<br /> Would have caused [[cyborg]] infantry in the team to go [[BerzerkAllowed|berserk]]. This action is obsolete, so the team simply moves on to the next action in the script, if present.<br /> |-<br /> |style=&quot;text-align: center;&quot;|3<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Move To Waypoint'''<br /> This instructs the team to use the task force to move to the waypoint number specified by the second parameter. Refer [[Waypoints]] for details on waypoint.<br /> <br /> '''Tip:''' You can use this action to get a team to move to waypoint no. 99 (just about every map has this defined as the center point) - that will mean it will always strive to get to the center of the map, providing a good vantage point from which to perform further actions and giving the impression that the computer is scouting for enemies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|4<br /> |style=&quot;text-align: center;&quot;|Cell#{{fnl|2}}<br /> |'''Move Into Specific Cell'''<br /> This instructs the team to use the task force to move into the Cell specified by the second parameter. Cell number in the second parameter uses formula of (Y * 128) + X. With modulus operator being used to compute the X value from the given parameter, even if the X values used in the formula is 128 or higher, the resultant X value is limited to between 0 and 127. This action can be used when you want the team to trigger a specific [[Actions_(maps)|action]] (when the game tests for the cell tag being entered). Cell tags are attached to cells and are used to trigger events and thus fire actions when that cell is entered by a unit (or any unit from the task force). Refer [[CellTags]] for details on cell tags.<br /> |-<br /> |style=&quot;text-align: center;&quot;|5<br /> |style=&quot;text-align: center;&quot;|Time{{fnl|3}}<br /> |'''Guard Area'''<br /> This instructs the team to put the task force into Guard mode for the amount of time specified. The team members will attack enemy units that fall within their weapon range, but they will not pursue enemies even when provoked. After guarding for the amount of time specified, the team will move on to execute its next script action.<br /> |-<br /> |style=&quot;text-align: center;&quot;|6<br /> |style=&quot;text-align: center;&quot;|Line#{{fnl|2}}<br /> |'''Jump To Line #'''<br /> This is used to repeat script actions within the script. The second parameter is the action ''line number'' of the [[ScriptTypes|script type]] that you want to jump to.&lt;br/&gt;'''Note''': Script action index starts at 0 whereas the line number starts at 1. So, to jump to the first script action whose index is 0, use {{tt|n=6,1}} for this script. Jump to line number could be specified to any of the preceding line numbers, not just to the first script action to create a loop of actions.<br /> |-<br /> |style=&quot;text-align: center;&quot;|7<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Player Win'''<br /> Forces a game win condition for the owner of the team (they win the game).<br /> |-<br /> |style=&quot;text-align: center;&quot;|8<br /> |style=&quot;text-align: center;&quot;|Unload Behaviour#{{fnl|2}}<br /> |'''Unload'''<br /> If the task force contains a unit or units that have a valid {{f|Passengers|link}} value set, and those units contain passengers, this command will make the units inside the transport(s) disembark. Note that once the passengers have disembarked, the transport itself is suspended until given a new mission and is therefore no longer considered a part of this task force - this means that you cannot, for example, get units to disembark, do something, then get back into the transport in the same script. The second parameter can be used to control what happens to the transport after it 'deploys' its cargo:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Description<br /> |-<br /> |0<br /> |Keep transports and units - all remain in the team and execute the remainder of the script<br /> |-<br /> |1<br /> |Keep transport and lose the units - only the transport will execute the remainder of the script<br /> |-<br /> |2<br /> |Lose transport and keep units - only the units will execute the remainder of the script<br /> |-<br /> |3<br /> |Lose transports and lose units - nothing executes the remainder of the script<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|9<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Deploy'''<br /> If the task force contains a unit or units that are able to deploy (for example a unit which {{f|DeploysInto|link}} a [BuildingType] or has any of {{f|Deployer|yes|link}}, {{f|DeployFire|yes|link}}, {{f|DeployToFire|yes|link}} set) then this action causes them to deploy at the current cell they are occupying (same effect as selecting a unit and pressing the Deploy key as defined in KEYBOARD.INI or clicking the relevant button on the Advanced Command Bar).<br /> |-<br /> |style=&quot;text-align: center;&quot;|10<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Follow Friendlies'''<br /> This command causes the task force to follow the nearest friendly unit when it moves although it will not function as if it is 'guarding' the unit. The following is not permanent, when the task force is assigned another mission it abandons the following.<br /> <br /> '''Tip''': If the secondary (support) team has this as the first line in its [[ScriptTypes|script]], then it will escort the primary team.<br /> |-<br /> |style=&quot;text-align: center;&quot;|11<br /> |style=&quot;text-align: center;&quot;|Mission#{{fnl|2}}<br /> |'''Assign New Mission'''<br /> The objects in the task force are assigned the [[Mission Control|mission]] defined by the second parameter.<br /> <br /> Not all of the available mission types are applicable to teams; those that are, such as {{tt|Sleep}}, {{tt|Sticky}}, {{tt|Guard}}, {{tt|Area Guard}}, {{tt|Hunt}}, are perpetual by nature so once assigned to a team, the units in the team will remain in that mission until those units are destroyed, the team is dissolved, or the units are recruited into another team and given a different mission. Because the missions are never-ending, this script action can't finish and move to the next script action. Thus, this script action is best given as the last script action in the script.<br /> <br /> The following are valid settings for the second parameter:<br /> {|class=&quot;wikitable&quot;<br /> |-<br /> !Value<br /> !Name<br /> !Description<br /> |-<br /> !colspan=&quot;3&quot;|{{ts}} and {{fs}}<br /> |-<br /> |0<br /> |Sleep<br /> |object sits around and plays dead, will not acquire targets<br /> |-<br /> |1<br /> |Attack<br /> |special attack mission used by AI team types (utilizes threat rating logic)<br /> |-<br /> |2<br /> |Move<br /> |simply moving to destination<br /> |-<br /> |3<br /> |QMove<br /> |special move to destination after other queued moves occur<br /> |-<br /> |4<br /> |Retreat<br /> |object runs away (may even leave the map)<br /> |-<br /> |5<br /> |Guard<br /> |object sits around and will engage and pursue an enemy that falls within its weapon range or attacks it<br /> |-<br /> |6<br /> |Sticky<br /> |just like guard mode, except the object will engage enemies but not pursue them<br /> |-<br /> |7<br /> |Enter<br /> |enter building or transport<br /> |-<br /> |8<br /> |Capture<br /> |engineer entry logic used by {{f|MultiEngineer|link}}<br /> |-<br /> |9<br /> |Harvest<br /> |the loop controlling harvesting of tiberium and dumping at a Refinery<br /> |-<br /> |10<br /> |Area Guard<br /> |guard the general area where the object starts at<br /> |-<br /> |11<br /> |Return<br /> |return to co-ordinating object (e.g. spawned object returns to the spawner)<br /> |-<br /> |12<br /> |Stop<br /> |stop moving or firing at the first available opportunity<br /> |-<br /> |13<br /> |Ambush<br /> |force fire (units with Infiltrate=yes will enter target if possible)<br /> |-<br /> |14<br /> |Hunt<br /> |scan for and attack enemies wherever they may be on the map. Chooses the target based on threat or first built. See [[TargetDistanceCoefficientDefault]] for more information. Will not retaliate if attacked.<br /> |-<br /> |15<br /> |Unload<br /> |while dropping off cargo<br /> |-<br /> |16<br /> |Sabotage<br /> |unit runs to place C4 on a building<br /> |-<br /> |17<br /> |Construction<br /> |structures use this when building up after initial placement<br /> |-<br /> |18<br /> |Selling<br /> |structures use this for deconstruction after being sold<br /> |-<br /> |19<br /> |Repair<br /> |used when repairing an object (e.g. Service Depot)<br /> |-<br /> |20<br /> |Rescue<br /> |special team over-ride mission<br /> |-<br /> |21<br /> |Missile<br /> |nuke Silo special launch missile mission<br /> |-<br /> |22<br /> |Harmless<br /> |object doesn't fire and is not considered in any threat scan<br /> |-<br /> |23<br /> |Open<br /> |while opening or closing a gate to allow passage<br /> |-<br /> |24<br /> |Patrol<br /> |patrol a series of waypoints<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} and {{Yr}}<br /> |-<br /> |0<br /> |Sleep<br /> |object sits around and plays dead, will not acquire targets<br /> |-<br /> |1<br /> |Attack<br /> |special attack mission used by AI team types (utilizes threat rating logic)<br /> |-<br /> |2<br /> |Move<br /> |simply moving to destination<br /> |-<br /> |3<br /> |QMove<br /> |special move to destination after other queued moves occur<br /> |-<br /> |4<br /> |Retreat<br /> |object runs away (may even leave the map)<br /> |-<br /> |5<br /> |Guard<br /> |object sits around and will engage an enemy that falls within its weapon range<br /> |-<br /> |6<br /> |Sticky<br /> |just like guard mode, except the object will engage enemies but not pursue them<br /> |-<br /> |7<br /> |Enter<br /> |enter building or transport<br /> |-<br /> |8<br /> |Capture<br /> |engineer entry logic used by {{f|MultiEngineer|link}}<br /> |-<br /> |9<br /> |Eaten<br /> |unit enters a [[Grinding|grinder]]<br /> |-<br /> |10<br /> |Harvest<br /> |the loop controlling harvesting of Ore and dumping at a Refinery<br /> |-<br /> |11<br /> |Area Guard<br /> |guard the general area where the object starts at<br /> |-<br /> |12<br /> |Return<br /> |return to co-ordinating object (e.g. spawned object returns to the spawner)<br /> |-<br /> |13<br /> |Stop<br /> |stop moving or firing at the first available opportunity<br /> |-<br /> |14<br /> |Ambush<br /> |force fire (units with {{f|Infiltrate|yes|link}} will enter target if possible)<br /> |-<br /> |15<br /> |Hunt<br /> |scan for and attack enemies wherever they may be on the map<br /> |-<br /> |16<br /> |Unload<br /> |while dropping off cargo (e.g. Landing Craft unloading passengers)<br /> |-<br /> |17<br /> |Sabotage<br /> |unit runs to place C4 on a building or Ivan goes to place bomb on object<br /> |-<br /> |18<br /> |Construction<br /> |structures use this when building up after initial placement<br /> |-<br /> |19<br /> |Selling<br /> |structures use this for deconstruction after being sold<br /> |-<br /> |20<br /> |Repair<br /> |used when repairing an object (e.g. Service Depot)<br /> |-<br /> |21<br /> |Rescue<br /> |special team over-ride mission<br /> |-<br /> |22<br /> |Missile<br /> |nuke silo special launch missile mission<br /> |-<br /> |23<br /> |Harmless<br /> |object doesn't fire and is not considered in any threat scan<br /> |-<br /> |24<br /> |Open<br /> |while opening or closing a gate to allow passage<br /> |-<br /> |25<br /> |Patrol<br /> |patrol a series of waypoints<br /> |-<br /> |26<br /> |Paradrop Approach<br /> |object is approaching the paradrop site<br /> |-<br /> |27<br /> |Paradrop Overfly<br /> |object is flying over the paradrop site (i.e. dropping the paratroopers)<br /> |-<br /> |28<br /> |Wait<br /> |paused and awaiting next mission<br /> |-<br /> |29<br /> |Attack (again)<br /> |(special duplicate) used when units are deployed to fire (e.g. weapons with an area fire effect)<br /> |-<br /> !colspan=&quot;3&quot;|{{Yr}} additions<br /> |-<br /> |30<br /> |Spyplane Approach<br /> |object is flying towards target<br /> |-<br /> |31<br /> |Spyplane Overfly<br /> |object is flying over the target<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|12<br /> |style=&quot;text-align: center;&quot;|Global Variable#{{fnl|2}}<br /> |'''Set Global Variable'''<br /> The [[VariableNames|global variable]] number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only. This is part of the boolean logic employed by the global variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|13<br /> |style=&quot;text-align: center;&quot;|Sequence#{{fnl|2}}<br /> |'''Play Idle Anim Sequence'''<br /> If the task force contains a unit or units that use SHP graphics (i.e. infantry) then the relevant idle SHP sequence is displayed as defined by the frame numbering system in ART.INI. Parameter 0 for Idle1 and 1 for Idle2.<br /> |-<br /> |style=&quot;text-align: center;&quot;|14<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Load Onto Transport'''<br /> If the task force contains a unit or units that have a valid {{f|Passengers|link}} value set, and units whose {{f|Size|link}} and {{f|PhysicalSize|link}} settings allow them to be carried by that transport, this command will make the units enter the transport.<br /> |-<br /> |style=&quot;text-align: center;&quot;|15<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Spy On Structure At Waypoint'''<br /> Should be used only for units with {{f|Infiltrate|yes|link}} and {{f|Agent|yes|link}} set. This instructs the task force to enter the structure at the waypoint number specified by the second parameter and spy on the structure if it has {{f|Spyable|yes|link}} set. If there is no building at the specified waypoint, the task force may not activate correctly and will just remain in their last mission. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|16<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Patrol To Waypoint'''<br /> This is similar to Move to waypoint. This instructs the team to use the task force to move to the waypoint number specified by the second parameter. The difference is that the units in the task force will move out of their patrol route to actively go and engage any enemy objects that are within their {{f|Sight|link}} as they move to the waypoint.<br /> <br /> '''Note''': This patrol mission eats up processor time, because the task force will scan for enemy objects with each movement. If you have a lot of task forces (or lots of units in them) engaged in this mission, you will experience slowdown in the game - this is one reason why the single player missions are comparatively slow, they use this mission a lot. The rate at which the scanning for targets whilst in this mission is controlled by the {{f|PatrolScan|link}} statement in the [AI]section of RULES.INI. Refer [[Waypoints]] for details on waypoint.<br /> |-<br /> |style=&quot;text-align: center;&quot;|17<br /> |style=&quot;text-align: center;&quot;|Script#{{fnl|2}}<br /> |'''Change Script'''<br /> {{obsolete|{{ts}}|Change Script}}<br /> Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes|script type]] to execute as listed in the {{tt|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).<br /> <br /> Appears not to work, at least in Tiberian Sun.<br /> |-<br /> |style=&quot;text-align: center;&quot;|18<br /> |style=&quot;text-align: center;&quot;|Team#{{fnl|2}}<br /> |'''Change Team'''<br /> This instructs the task force to switch to another team. The second parameter specifies the number of the [[TeamTypes|team type]] to switch to as listed in the {{tt|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).<br /> <br /> {{W}} '''Note:''' The game loads team types from {{ini|ai}} first, then [[aifs.ini]] second ([[RequiredAddOn|if applicable]]), and the current map last. Because this action refers to a team by its index, it's prone to break as the index will change whenever you add or remove teams from any of the AI [[INIs]]. Therefore it is ''not'' recommended to use this action. A much more reliable method is to use [[Actions_(maps)|trigger actions]] to recruit the units to a new team, as triggers refer to teams by their names, not indexes.<br /> |-<br /> |style=&quot;text-align: center;&quot;|19<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Panic'''<br /> If the task force contains a unit or units that have {{f|Fraidycat|yes|link}} set then they will run around aimlessly, using the {{f|Panic}} animation from their sequence as defined in ART.INI. Normally used for the civilian units. Units that do not fulfil this criteria lie down and act as if prone.<br /> |-<br /> |style=&quot;text-align: center;&quot;|20<br /> |style=&quot;text-align: center;&quot;|House#{{fnl|2}}<br /> |'''Change House Ownership'''<br /> Used in single player missions on specific map files only, this changes ownership of the entire team to the house number specified by the second parameter.<br /> |-<br /> |style=&quot;text-align: center;&quot;|21<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Scatter'''<br /> This instructs the task force to scatter (same effect as selecting a group of units and pressing the Scatter key as defined in [[Keyboard.ini|KEYBOARD.INI]]).<br /> |-<br /> |style=&quot;text-align: center;&quot;|22<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Afraid &amp;amp; Run To Shroud'''<br /> This instructs the task force to behave in a scared manner and it will run to the nearest shrouded cell. The task force will not actively engage in combat, will not acquire targets and will not retaliate (it will scatter instead if attacked).<br /> |-<br /> |style=&quot;text-align: center;&quot;|23<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Player Loss'''<br /> Forces a game loss condition for the owner of the team (they lose the game).<br /> |-<br /> |style=&quot;text-align: center;&quot;|24<br /> |style=&quot;text-align: center;&quot;|Speech#{{fnl|2}}<br /> |'''Play Speech'''<br /> This instructs the task force to play one of the Sofia or EVA voices (depending upon the {{f|ParentCountry|link}} or the owner of this task force). The second parameter is the number of the sound to be played from the [DialogList] in the [[Eva.ini|EVA.INI]] (note that you should consider this list as being numbered from 0 instead of 1 to get the correct numbering convention).<br /> |-<br /> |style=&quot;text-align: center;&quot;|25<br /> |style=&quot;text-align: center;&quot;|Sound#{{fnl|2}}<br /> |'''Play Sound'''<br /> This instructs the task force to play one of the generic in game sounds from the {{sl|SoundList}} in the [[Sounds.ini|SOUNDS.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|26<br /> |style=&quot;text-align: center;&quot;|Movie#{{fnl|2}}<br /> |'''Play Movie'''<br /> This instructs the task force to play one of the movies from the {{sl|Movies}} list in the [[Art.ini|ART.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|27<br /> |style=&quot;text-align: center;&quot;|Theme#{{fnl|2}}<br /> |'''Play Theme'''<br /> This instructs the task force to play one of the game soundtracks from the {{sl|Themes}} list in the [[Theme.ini|Theme.INI]] file.<br /> |-<br /> |style=&quot;text-align: center;&quot;|28<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Reduce Tiberium/Ore'''<br /> Reduces the amount of Tiberium/Ore in the cell that the team is occupying. Used by the special 'weapon' that is inherent with Harvesters/Ore Miners.<br /> |-<br /> |style=&quot;text-align: center;&quot;|29<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Begin Production'''<br /> Forces the owner of the team to begin the auto-production process (the AI's behaviour in skirmish games). Should only be used on AI controlled houses.<br /> |-<br /> |style=&quot;text-align: center;&quot;|30<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Force Sale'''<br /> Forces the 'fire sale' of all remaining structures owned by the [[house]] to which the team belongs.<br /> |-<br /> |style=&quot;text-align: center;&quot;|31<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Suicide'''<br /> This instructs the task force to destroy itself. In effect it commits suicide, usually accompanied by an explosion.<br /> |-<br /> |style=&quot;text-align: center;&quot;|32<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Start Storm In...'''<br /> Initiates an Ion Storm (TS) or Weather Storm (RA2) after the time specified. In {{Ra2}}, this initiates the Weather Storm intro effect (when the screen goes dark prior to the clouds appearing). The effect is set to be delayed by the number of seconds specified by parameter 2.<br /> |-<br /> |style=&quot;text-align: center;&quot;|33<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''End Storm'''<br /> This forces an end to the active Ion Storm or Weather Storm.<br /> |-<br /> |style=&quot;text-align: center;&quot;|34<br /> |style=&quot;text-align: center;&quot;|Speed#{{fnl|2}}<br /> |'''Center Map On Team'''<br /> This will center the screen on the team. The same effect as hitting the Home key as defined in [[Keyboard.ini|KEYBOARD.INI]] when the screen centers on your MCV (or the unit defined by the {{f|BaseUnit|link}} statement in RULES.INI). The second parameter determines the speed at which the 'camera' switches view to the task force with 0 being slow to 4 being fast.<br /> |-<br /> |style=&quot;text-align: center;&quot;|35<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Shroud Map For Time Interval'''<br /> This action will shroud the entire map except for the area revealed by the player's own and/or friendly units. The second parameter determines the number of [[frames]] for which the map should remain shrouded after which the explored areas are revealed again.<br /> |-<br /> |style=&quot;text-align: center;&quot;|36<br /> |style=&quot;text-align: center;&quot;|Time#{{fnl|2}}<br /> |'''Reveal Map For Time Interval'''<br /> This action will reveal the entire map. The second parameter determines the number of [[frames]] for which the map should remain revealed after which the map is shrouded again.<br /> |-<br /> |style=&quot;text-align: center;&quot;|37<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Delete Team Members'''<br /> Deletes members of this task force from the map.<br /> |-<br /> |style=&quot;text-align: center;&quot;|38<br /> |style=&quot;text-align: center;&quot;|Global Variable#{{fnl|2}}<br /> |'''Clear Global Variable'''<br /> The [[VariableNames|global variable]] number specified in the second parameter is defined as being 'clear' (it is allocated a value of '0' or 'false'). This should be employed in specific map files only in which the global variable has been defined. This is part of the boolean logic employed by the global variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|39<br /> |style=&quot;text-align: center;&quot;|Local Variable#{{fnl|2}}<br /> |'''Set Local Variable'''<br /> The [[VariableNames|local variable]] number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only in which the local variable has been defined. This is part of the boolean logic employed by the local variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|40<br /> |style=&quot;text-align: center;&quot;|Local Variable#{{fnl|2}}<br /> |'''Clear Local Variable'''<br /> The [[VariableNames|local variable]] number specified in the second parameter is defined as being 'cleared' (it is allocated a value of '0' or 'false'). This should be employed in specific map files only in which the local variable has been defined. This is part of the boolean logic employed by the local variables system in the game engine.<br /> |-<br /> |style=&quot;text-align: center;&quot;|41<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Unpanic'''<br /> If the task force contains a unit or units that have {{f|Fraidycat|yes|link}} set which are currently assigned the {{f|Panic}}= sequence then this action nullifies that effect and the unit(s) adopt their default behaviour.<br /> |-<br /> |style=&quot;text-align: center;&quot;|42<br /> |style=&quot;text-align: center;&quot;|Direction#{{fnl|2}}<br /> |'''Change Facing'''<br /> This instructs the task force to turn and face the new direction specified by the second parameter. The facings are as follows:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Direction Type{{fnl|5}}<br /> !Direction<br /> |-<br /> |0<br /> |North<br /> |Top-Right<br /> |-<br /> |1<br /> |North-East<br /> |Right<br /> |-<br /> |2<br /> |East<br /> |Bottom-Right<br /> |-<br /> |3<br /> |South-East<br /> |Bottom<br /> |-<br /> |4<br /> |South<br /> |Bottom-Left<br /> |-<br /> |5<br /> |South-West<br /> |Left<br /> |-<br /> |6<br /> |West<br /> |Top-Left<br /> |-<br /> |7<br /> |North-West<br /> |Top<br /> |}<br /> |-<br /> |style=&quot;text-align: center;&quot;|43<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Wait Until Fully Loaded'''<br /> This is always used after members of the task force have entered a transport in the same task force and serves two purposes. The effect of this is that the transport will be used to carry out any subsequent movement or deploy actions but after that it is no longer considered a part of this task force and as such is available to be recruited into new teams. It is this action which enables use of the {{f|TransportsReturnOnUnload|yes|link}} statement in the corresponding team type entry. The second purpose is to flag the transport as being 'loaded' with passengers and thus is considered in the AI's targeting logic as a potential threat (see the {{f|ContentScan|link}} entry in the RULES.INI). This action also orders the transport to wait until it is fully loaded before executing any subsequent script actions.<br /> |-<br /> |style=&quot;text-align: center;&quot;|44<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Unload Truck (TRUCKB to TRUCKA)'''<br /> Used purely for a graphical effect and applicable uniquely to the [TRUCKB] unit, this has the effect of converting [TRUCKB] into [TRUCKA] to give the impression that the unit has unloaded its cargo.<br /> '''Note''': May not work correctly in Red Alert 2 since [TRUCKA] refers to the Demo Truck image which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic.<br /> |-<br /> |style=&quot;text-align: center;&quot;|45<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Load Truck (TRUCKA to TRUCKB)'''<br /> Used purely for a graphical effect and applicable uniquely to the [TRUCKA] unit, this has the effect of converting [TRUCKA] into [TRUCKB] to give the impression that the unit has been loaded with cargo.<br /> '''Note''': May not work correctly in Red Alert 2 since [TRUCKA] refers to the Demo Truck image which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic.<br /> |-<br /> |style=&quot;text-align: center;&quot;|46<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Attack Enemy Structure'''<br /> Members of this task force attack the enemy structure specified by the second parameter. This action depends upon the type of units in the task force and if certain members have {{f|Infiltrate|yes|link}} set. Members with {{f|Engineer|yes|link}} set will capture the structure provided it does not have {{f|Capturable|no|link}} set or if it has {{f|NeedsEngineer|yes|link}} set. Members with {{f|Agent|yes|link}} set will spy on the structure if it has {{f|Spyable|yes|link}} set. Members that do not have {{f|Assaulter|no|link}} set will garrison the structure if it has {{f|CanBeOccupied|yes|link}} set. Members with {{f|C4|yes|link}} set will blow up the structure if does not have {{f|CanC4|no|link}} set.<br /> |-<br /> |style=&quot;text-align: center;&quot;|47<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Move To Enemy Structure'''<br /> Members of this task force move and stay adjacent to the enemy structure specified by the second parameter.<br /> |-<br /> |style=&quot;text-align: center;&quot;|48<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Scout'''<br /> Causes members of this task force to move to a pre-determined point on the map in an attempt to scout an area. The effect is that the task force will move in one randomly chosen direction until it is no longer able to do so which can make it very useful or a waste of time depending on the direction chosen. If you want to continually scout the map, you should loop this script action.<br /> |-<br /> |style=&quot;text-align: center;&quot;|49<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Register Success'''<br /> Executing this script action even once in a script by its task force is considered as a success. A script not containing this script action is a fail for its task force. A script containing this script action but the task force being unable to reach and execute this action even once is a fail. These success and failure are used to adjust the current weight defined in AITriggers. Refer [[AITriggerTypes#Weights|AITriggerType's weights]].<br /> |-<br /> |style=&quot;text-align: center;&quot;|50<br /> |style=&quot;text-align: center;&quot;|Time Frames<br /> |'''Flash'''<br /> This causes all members of the task force to 'flash', the visual effect you get on an object when you order something to attack it. The second parameter is the number of time [[frames]] to flash the unit 'white'.<br /> |-<br /> |style=&quot;text-align: center;&quot;|51<br /> |style=&quot;text-align: center;&quot;|Animation#{{fnl|2}}<br /> |'''Play Animation'''<br /> This instructs the task force to play one of the animations from the {{sl|Animations}} list.<br /> |-<br /> !colspan=&quot;3&quot;|{{fs}} addition<br /> |-<br /> |style=&quot;text-align: center;&quot;|52<br /> |style=&quot;text-align: center;&quot;|Talk Bubble#{{fnl|2}}<br /> |'''Display Talk Bubble'''<br /> Should be used for single-unit task forces only, this causes a 'talk bubble' to appear above the unit. The second parameter determines which type of talk bubble to display. By default, the game has only three talk bubbles, though it's possible to add more and change what the bubbles represent:<br /> {|class=&quot;wikitable&quot;<br /> !Value<br /> !Bubble<br /> |-<br /> |1<br /> |* (generic speech)<br /> |-<br /> |2<br /> |? (question, confusion)<br /> |-<br /> |3<br /> |! (alert, attention, shout)<br /> |}<br /> <br /> '''Note''': The length of time for which the talk bubble is displayed is controlled through the {{f|TalkBubbleTime|link}} statement in RULES.INI. Refer to the RULES.INI Guide for details of this and the steps to take to enable its inclusion in Red Alert 2.<br /> |-<br /> !colspan=&quot;3&quot;|{{Ra2}} additions<br /> |-<br /> |style=&quot;text-align: center;&quot;|53<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Gather (At Enemy Base)'''<br /> This causes the task force to gather together (sometimes used when members of the task force move at different speeds and you want the faster ones to stop while the slower ones catch up) after the previous script action has been executed. If the task force is in an attack mission and moving towards an enemy base, this command is usually executed when the first member of the task force reaches the distance from that base defined by the {{f|AISafeDistance|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|54<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Regroup (At Friendly Base)'''<br /> This causes the task force to regroup, if for example any of its members have become engaged in a base defense mission or strayed away whilst in guard mode, or even the team itself has been suspended for whatever reason. The members regroup directly next to each other leaving no 'gaps' at the nearest available point with sufficient space, and is used, for example, prior to activating the Iron Curtain so that all applicable members are affected (i.e. they fall within its range of effect).<br /> |-<br /> |style=&quot;text-align: center;&quot;|55<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Activate Iron Curtain On Task Force'''<br /> If the owner of the task force to which this script is attached also has the Iron Curtain fully charged then it will be fired at this task force. Note that the use of the Iron Curtain in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|56<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Chronoshift Task Force to a building'''<br /> If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to the enemy structure specified by the second parameter, before moving on to the next script action. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|57<br /> |style=&quot;text-align: center;&quot;|Quarry Type#{{fnl|2}}<br /> |'''Chronoshift Task Force to a target type'''<br /> If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to a target that fits the [[QuarryTypes|quarry type]] (target category) specified by the second parameter, before moving on to the next script action. Target selection is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes|technotype]] override of [[TargetDistanceCoefficient]]. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f|AIMinorSuperReadyPercent|link}} statement in RULES.INI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|58<br /> |style=&quot;text-align: center;&quot;|BwP{{fnl|4}}<br /> |'''Move To Friendly Structure'''<br /> Members of this task force move and stay adjacent to the friendly structure specified by the second parameter. The structure can be one owned by the owner of the task force or any of its allies.<br /> |-<br /> !colspan=&quot;3&quot;|{{Yr}} additions<br /> |-<br /> |style=&quot;text-align: center;&quot;|59<br /> |style=&quot;text-align: center;&quot;|Waypoint#{{fnl|2}}<br /> |'''Attack Structure At Waypoint'''<br /> Members of this task force attack the structure at the waypoint specified by the second parameter. This script action is very similar to script action no. {{tt|43}} although this action does not test for ownership of the structure itself - thus the inclusion of this action allows, for example, InfantryTypes with {{f|Engineer|yes|link}} set to enter structures owned by the same side for the purposes of repair. This would be the most appropriate action to use to get the AI to repair bridges. Use of this also means that the task force will attack the structure with one of its weapons meaning, for example, that units with {{f|C4|yes|link}} set will not C4 the building but shoot at it instead. This is useful if you want to get a task force to destroy a nearby occupiable structure instead of entering it in a bid to prevent the enemy getting hold of it - a tactic used in the Yuri's Revenge AI.<br /> |-<br /> |style=&quot;text-align: center;&quot;|60<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Enter Grinder'''<br /> Members of this task force will enter the nearest structure with {{f|Grinding|yes|link}} set if it is owned by the owner of the task force or any of its allies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|61<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Occupy Tank Bunker'''<br /> Any VehicleType members of this task force which do not have {{f|Bunkerable|no|link}} set will enter the nearest vacant structure with {{f|Bunker|yes|link}} set if it is owned by the owner of the task force or any of its allies.<br /> |-<br /> |style=&quot;text-align: center;&quot;|62<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Enter Bio Reactor'''<br /> Any InfantryType members of this task force will enter the nearest structure with {{f|InfantryAbsorb|yes|link}} set if it is owned by the owner of the task force or any of its allies and has space available.<br /> |-<br /> |style=&quot;text-align: center;&quot;|63<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Occupy Battle Bunker'''<br /> Any InfantryType members of this task force with {{f|Occupier|yes|link}} set will enter the nearest structure (which they own) with {{f|CanOccupyFire|yes|link}} set.<br /> |-<br /> |style=&quot;text-align: center;&quot;|64<br /> |style=&quot;text-align: center;&quot;|0<br /> |'''Garrison Structure'''<br /> Any InfantryType members of this task force with {{f|Occupier|yes|link}} set will enter the nearest (neutral) structure with {{f|CanOccupyFire|yes|link}} set. This script action is used specifically for this purpose due to action no. {{tt|59}} (see above) since the logic in Yuri's Revenge has changed so that the unit's weapon is transferred to the structure. Use of this action also allows the computer to repair those structures by sending an InfantryType with {{f|Engineer|yes|link}} set into them and also allows the AI to differentiate between attacking such a structure and entering it, which is useful if you want the AI to use infantry to destroy an occupiable structure thus preventing its enemy from using it.<br /> |}<br /> <br /> {{fn|1|[https://en.wiktionary.org/wiki/quarry#Etymology_2 Quarry] as in the sense of prey or target, not mine.}}<br /> {{fn|2|For convenience, the &quot;#&quot; symbol refers to a number/index of the object type. For example, &quot;Waypoint#&quot; refers to the index number of the Waypoint in the [[Waypoints]] list.}}<br /> {{fn|3|Time to guard area. In {{ts}}, the time is measured in seconds at default game speed (15 FPS). In {{ra2}} and {{yr}}, the time is measured in tenths of a minute (multiples of 6 seconds) at normal game speed.}}<br /> {{fn|4|'''B'''uilding '''w'''ith '''P'''roperty is the computed value of the building's index in [[BuildingTypes]] and the AI's choice for target selection. See the [[#Notes|notes]] below for more information.}}<br /> {{fn|5|Note that the internal &quot;compass&quot; is tilted due to the game's dimetric projection, i.e. internal North is top-right, North-East is right, etc.}}<br /> <br /> ==Notes==<br /> <br /> '''Building with Property (BwP) number'''<br /> <br /> This number allows the AI to target a specific instance of a building based on threat or distance when there are multiple instances of the specified building. When there is only one instance of a specified building then there is only one building to select, so the outcome based on options of threat or distance is the same. The computation of this building number is as follows: &lt;br/&gt;<br /> <br /> {|class=&quot;wikitable&quot;<br /> !Computed Value<br /> !Description<br /> |-<br /> |0 (Hex {{tt|0x0}}) + Building Index<br /> |Select the instance of the building with least threat<br /> |-<br /> |65536 (Hex {{tt|0x10000}}) + Building Index<br /> |Select the instance of the building with highest threat<br /> |-<br /> |131072 (Hex {{tt|0x20000}}) + Building Index<br /> |Select the instance of the building which is nearest<br /> |-<br /> |196608 (Hex {{tt|0x30000}}) + Building Index<br /> |Select the instance of the building which is farthest<br /> |}<br /> <br /> Reference to a building number exceeding the buildings in the [[BuildingTypes]] list or using number 262144 or higher, results in a do-nothing script action and the team will move on to execute its next script action.<br /> <br /> Threat posed by any number of instances of the same building will all be the same. So, to determine which instance of a building has higher or lower threat, its cumulative threat value is used. For example, if there are some units near a building, its threat rating becomes higher with the additional threat values of the nearby units.<br /> <br /> In cases where multiple instances of the specified building have equal threat or are equidistant, AI will choose the one which was constructed first by the target side. If the first was destroyed/sold etc., then the next constructed building becomes target. Friendlies don't pose threat, so it becomes a case of equal threat.<br /> <br /> '''Example of BwP number computation:''' to make the AI team members select their nearest enemy Allied War Factory, look for the 0-based index of the GAWEAP in the [[BuildingTypes]] list (7), add 131072, and use the resulting structure number as the script action parameter: 7 + 131072 = '''131079'''.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Stray&diff=28589 2025-05-31T19:26:57Z

<p>Crimsonum: Known use cases</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|ini=rules}}<br /> |types={{Categ|General}}<br /> |values={{values|float}}<br /> |ra=yes<br /> |cs=yes<br /> |am=yes<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Radius, in [[cells]], that AI-controlled [[team]] [[TaskForces|members]] can stray from their position without causing them to regroup. This stops the AI teams from breaking up too much which would render their collective purpose useless.<br /> <br /> == Use Cases ==<br /> In practice, this flag seems to apply only in the following cases:<br /> === Guard ===<br /> When a team is set to the [[ScriptActions|{{tt|Guard}}]] mission, if any of the team members stray from the group more than this distance to pursue an enemy (because the enemy either attacked them or entered their weapon range), the remaining units in the team will follow suit. Note that the followers will not automatically aggro the enemy unless they themselves are provoked.<br /> <br /> === Distance to Target ===<br /> {{tt|Stray}} also determines the minimum distance between a team's origin and its destination for the team to actually move there. If the distance is this or less, then the team will assume it's already in its destination and will not move further.<br /> <br /> In other words, if you create or reinforce a team at a [[waypoint]], and in the team's [[script]] you have that team move to another waypoint or target that's within this many cells from the team's origin waypoint, then the team thinks it's already reached its destination and will proceed to the next [[team missions|mission]] in the script.<br /> <br /> == See Also ==<br /> * [[CloseEnough]]<br /> <br /> [[Category:Map Information]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Internal_Error&diff=28588 2025-05-27T20:49:14Z

<p>Crimsonum: Add TS EIP 004CB997</p> <hr /> <div>[[Image:Ts_ie.png|thumb|150px|right|Tiberian Sun's Internal Error]]<br /> [[Image:Ra2_ie.png|thumb|150px|right|Red Alert 2's Internal Error]]<br /> [[Image:Yr_ie.png|thumb|150px|right|Yuri Revenge's Internal Error]]<br /> [[Image:Rp_ie.png|thumb|150px|right|RockPatch's Internal Error]]<br /> The '''Internal Error''' (often just written short-hand as '''IE''') is a general error returned by the [[Tiberian Sun]] [[engine]] and its derivates. The message itself gives no information about what the error actually was or what went wrong, thus leaving it to the modder to know what could have caused the error and to find the cause in their mod's changes.<br /> <br /> If you experience an Internal Error, you should:<br /> # Check if the EIP reported in your except.txt file matches an EIP for which the IE cause is known (see below).<br /> # Think about whether a distinctive event immediately preceeded the error (e.g. a unit being built, a weapon being fired, etc.). If this was the case then take a look at the changes you applied to that unit/weapon/whatever and see if there are any mistakes.&lt;br&gt;<br /> # Carefully check your latest modifications, with the help of a diff between the current rules set and the previous, working rules if possible (for this reason, and in case you mess up your code beyond repair, you should always keep recent backups of working code).<br /> Remember that the more code you add at the same time, the more likely it is to introduce multiple bugs and IE causes (and just because you found one mistake in your code, that doesn't mean there can't be another).<br /> <br /> ==Except.txt==<br /> If your game crashes because of an Internal Error, a file named except.txt is generated in your game folder. This file is a dump of certain runtime-data from the game at the moment the error occurred and could potentially tell you exactly what went wrong ''if'' you knew the engine code. &lt;br&gt;<br /> Due to his research into the game's binary and his efforts to develop the RockPatch, pd has occasionally been able to indicate the area of the engine where the error occurred (for example, an error occurring in the voxel-loading routines may indicate a problem with a custom voxel).<br /> However, pd has other commitments and should not be treated as the go-to guy for any IEs you may have. Further more, pd may not neccessarily be able to help - without the source code or a comprehensive understanding of the game's binary the file is of little use. (cp. [[SYNCx.txt]])<br /> <br /> According to an early version of [[Except.txt]] (which now redirects here), this file includes the full structure and a stack dump of a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/context_str.asp CONTEXT] element.<br /> <br /> IEs that share the same cause also share the same &lt;tt&gt;EIP:&lt;/tt&gt; value in except.txt, so knowing that value might help you determine the cause of your IE (see the list of known IE causes (below) which also includes the corresponding EIP). However, it should be noted that some shared IE causes in INI code can yield one of several different EIP values (depending on the circumstance), and that some rare IE causes can actually yield totally random EIP values. As such, if you do have an unexplained IE, you should check all of the known causes.<br /> <br /> == Known causes of Internal Errors and their EIPs ==<br /> Since &quot;Internal Error&quot; is the game's response to almost any fatal error, its causes are diverse. Most common are causes related to weapons and warheads, with a missing warhead probably being the most commonly reported cause.&lt;br&gt;Note that some IE causes may be prevented (or at least have certain limits extended (e.g. CellSpread)) by the [[RockPatch]], which in turn has opened up potential for new IE causes ([[RockPatch]]-specific IEs are not listed here).<br /> <br /> <br /> === Some useful tips ===<br /> If an integer between {{Tt|0x00812000}} and {{Tt|0x00B78300}} appears in the stack, subtract {{Tt|0x00400000}} from it and look at the resulting address in {{Tt|gamemd.exe}} with a hex editor. If you find some INI flag, you can be almost sure this flag was the one being read when the problem happened and as such its values (or absence thereof) is the problem.<br /> &lt;!-- Someone consider writing a tool to process this --&gt;<br /> <br /> <br /> === Specific game versions ===<br /> <br /> ==== Yuri's Revenge 1.001 ====<br /> <br /> {{:Internal_Error/YR}}<br /> <br /> ==== Tiberian Sun 2.03 ====<br /> <br /> {| cellpadding=&quot;4&quot; border=&quot;1&quot; class=&quot;table_descrowdesccol anchorcontainer&quot;<br /> ! EIP<br /> ! Cause<br /> |-<br /> ! {{Anchor|00415698|eip}} <br /> | You used a [[TrailerAnim]] on an animation but forgot to set a [[TrailerSeperation]].<br /> |-<br /> ! {{Anchor|0042A061|eip}} <br /> | Wall=yes on a normal building.<br /> |-<br /> ! {{Anchor|0043541C|eip}} <br /> | Building turret animation has an invalid pointer to an [[AnimTypeClass]] when charging up. See Nod Obelisk of Light for example.<br /> |-<br /> ! {{Anchor|00446E61|eip}}&lt;br /&gt;{{Anchor|00446F68|eip}}<br /> | Airburst weapon bullet was null. If you have {{f|Airburst|yes|link}} or {{f|Splits|yes|link}} on a [[projectile]], you must also define {{f|AirburstWeapon|link}}.<br /> |-<br /> ! {{Anchor|00451C16|eip}}<br /> | {{f|CellAnim|link}} has invalid {{f|Image|link}}.<br /> |-<br /> ! {{Anchor|0046C7E2|eip}} <br /> | Fog of War was enabled and crashed the game.<br /> |-<br /> ! {{Anchor|004BAEF8|eip}} <br /> | [AI] BuildRefinery= -&gt; one of your factions is missing an entry here, which will cause a crash when the AI tries to use this faction. Will not trigger a crash for human players.<br /> |-<br /> ! {{Anchor|004BAF12|eip}} <br /> | [General] HarvesterUnit -&gt; one of the objects in this list is incorrect OR this list has exceeded 127 characters. Commonly triggered when adding new MCV and harvester object codes here when expanding the playable faction list in the TSC 6.00+ builds.<br /> |-<br /> ! {{Anchor|004C1680|eip}}<br /> | A house has no buildable {{f|HarvesterUnit|link}}. This crash is typically caused by a [[house]] with an incorrect {{f|ActsLike|link}} setting in a [[map]] when using [https://github.com/CnCNet/ts-patches/blob/9a6440cc921c0941da19e2b1691c45f8d701109d/src/buildconst_harvesterunit_baseunit.asm this patch]. In this case, {{f|ActsLike}} must always point to a house that owns at least one unit listed in {{f|HarvesterUnit}}. Also, make sure all houses listed in the map's {{tt|[Houses]}} list have a valid section. e.g. {{tt|[GDI]}}, defined in the map.<br /> |-<br /> ! {{Anchor|004C445E|eip}} <br /> | A unit's Secondary weapon doesn't exist. Check the spelling and cases.<br /> |-<br /> ! {{Anchor|004C6428|eip}} <br /> | AI does not have any buildings available for it to build. Check {{f|BuildConst|link}}=, {{f|BuildPower|link}}= etc.<br /> |-<br /> ! {{Anchor|004CB997|eip}}<br /> | [[TeamTypes|Team]]'s owner house is invalid. Check if there's a map trigger creating a team whose {{f|House|link}} is invalid or undefined (the house must be one of the houses listed in the map).<br /> |-<br /> ! {{Anchor|004D2451|eip}}<br /> | An infantry was about to take damage from a source with no valid [[Warhead]]= set.<br /> |-<br /> ! {{Anchor|004D6626|eip}}&lt;br/&gt;{{Anchor|004D8BF3|eip}}<br /> | Infantry with missing image in rules.ini (same as missing sequence in art.ini).<br /> |-<br /> !{{Anchor|004F886D|eip}}<br /> | Trying to access colors in header while building radar image; related to the Radar High/Low Colors for terrain tiles.<br /> |-<br /> !{{Anchor|004F8EDD|eip}}<br /> |The number of [[VehicleTypes]] in the [[BaseUnit]] section is incomplete.<br /> |-<br /> ! {{Anchor|005A4814|eip}} <br /> | Railgun with wrong particle keys.<br /> |-<br /> ! {{Anchor|005A59B4|eip}}<br /> | {{tt|[GasCloudSys]}} with a limited {{f|Lifetime|link}}. This system has hardcoded properties and must exist throughout the game, ergo you must set {{f|Lifetime|-1}} or leave it undefined (it defaults to -1).<br /> |-<br /> ! {{Anchor|005A5A83|eip}}<br /> | Invalid {{f|Image|link}} on an [[animation]] attempting to [[SpawnsParticle|spawn particles]] ([[Vinifera]] only). The image must be an existing [[shape]].<br /> |-<br /> ! {{Anchor|005A5EB6|eip}} <br /> | {{f|ParticleCap|1|link}} on a {{f|BehavesLike|Spark|link}} particle system.<br /> |-<br /> ! {{Anchor|005A640F|eip}}<br /> | {{f|NextParticle|link}} defined on a particle spawned by a {{f|BehavesLike|Smoke|link}} particle system.<br /> |-<br /> ! {{Anchor|0062E6F6|eip}} <br /> | It was attempted to use a normal colored house on a multiplayer map.<br /> |-<br /> ! {{Anchor|00649563|eip}} <br /> | A [[trigger]] failed to spring. Look for a trigger with invalid parameters, for example a misspelled or undefined [[house]].<br /> |-<br /> ! {{Anchor|006703D4|eip}} <br /> | WaveClass Sonic exception, normally triggered by a unit with a weapon that has IsSonic=yes set, firing to the south of the screen and the user scrolling up. No certain fix for this as we know, although [http://ppmsite.com/forum/viewtopic.php?t=31604 HyperPatch] has been confirmed to fix it at least on some systems. Another fix is disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll], although the fix doesn't work on Windows OS's newer than XP.<br /> |-<br /> ! {{Anchor|0067159B|eip}} <br /> | WaveClass Sonic exception. Not sure if this is code related, could be end user.<br /> |-<br /> ! {{Anchor|006717CB|eip}} <br /> | WaveClass laser exception. This can be fixed by setting DetailLevel= to 1 or 0 in SUN.ini. In addition, disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll] fixes it, but this fix only works on Windows operating systems older than Vista.<br /> |-<br /> ! {{Anchor|0067159B|eip}} <br /> | | You have set {{sl|AudioVisual|ShakeScreen}} to zero.<br /> |-<br /> ! {{Anchor|00681363|eip}} <br /> | Missing weedguy hack. (second stage Cluster weapons need to be assigned to a unit, to work)<br /> |-<br /> ! {{Anchor|006A877A|eip}} <br /> | LightSize&gt;94 was set on a particlesystem.<br /> |-<br /> ! {{Anchor|006B6AE6|eip}} <br /> | Multiple reasons, depending on the stack dump in the except:<br /> * If {{Tt|0066F44F}} appears near the top of the stack dump - A [[Warhead]] whose {{f|Verses|link}} could not be processed. {{Tt|EBP}} value says how many values remained to be parsed when an error occurred - (5 - {{Tt|EBP}}) is the 0-based index of the problematic value.<br /> |-<br /> ! {{Anchor|006BB69C|eip}} <br /> | conyard construction as building was canceled in the sidebar.<br /> |-<br /> ! {{Anchor|90900004|eip}} <br /> | Generic exception.<br /> |}<br /> <br /> ==== Unverified / lacking information ====<br /> <br /> {| cellpadding=&quot;4&quot; border=&quot;1&quot; class=&quot;table_descrowdesccol anchorcontainer&quot;<br /> ! EIP<br /> ! Cause<br /> |-<br /> ! {{Anchor|00494BCD|eip}} <br /> | (Ares 3.0) A corrupted SHP image was drawn. Check mix files for any .shp files marked by XCC Mixer as 'unknown' under &quot;type&quot;.<br /> |-<br /> |-<br /> ! {{Anchor|1118A7A5|eip}} <br /> | Probably caused by trying to destroy a tag, but supplying the tag and not a trigger (FA2 offers Triggers, but I hand-typed a tag (among other things). Occams razor suggests this is the culprit.<br /> |-<br /> ! {{Anchor|655B4A9C|eip}} <br /> |(Ares 0.E) Setting a [ParticlePart] with 2 BehavesLike= simutaneously (for example , 'both Like=railgun' and 'Like=smoke' exist) may cause an EIP as above . Remove BehavesLike=railgun , and keep Like=smoke here in a [RailgunPart] to avoid this EIP and still gets a railgun with specific SHP-animation rail.<br /> &lt;br&gt;''(Two BehavesLike in Ares 0.D is still available , but 0.E not .)''<br /> |-<br /> ! {{Anchor|?|eip}} <br /> | Removing a building from the PrerequisitePower= list, while it exists in one of the (GDI/NODRegular/Third)PowerPlant= lists will cause an IE the moment any of your Power buildings get destroyed or sold as long as you own a Construction Yard. YR mods that remove Yuri's side from the game, should not remove YAPOWR from PrerequisitePower=.<br /> &lt;br&gt;''(Could not be reproduced thus far.)''<br /> |-<br /> ! {{Anchor|?|eip}} <br /> | Calling for an animation that is not listed under {{tt|[[Animations|[Animations]]]}} might trigger an IE.<br /> &lt;br&gt;''(That can be caused by multiple issues at various EIPs.)''<br /> |-<br /> ! {{Anchor|?|eip}} <br /> | Building a unit in-game whose VXL/SHP was inserted in an original game MIX instead of an expansion MIX.<br /> &lt;br&gt;''(Does this really happen? Sounds more like the mix editor crapping up than simply &quot;game should blow up because you changed stock files&quot;.)''<br /> &lt;br&gt;''Further more, why would anyone eschew the normal method of ''expand''ing the game''. I don't see anyone testing/replicating this so I propose removing it from the list. //Marshall''<br /> |-<br /> ! {{Anchor|006F3481|eip}}<br /> | The (elite) secondary weapon (or its warhead) of the object you just selected could not be found (see [[#Broken-reference_Causes|broken-reference causes]], below).<br /> &lt;br&gt;''(Marshall retested this and found that the EIP for a missing secondary weapon is actually 006F352E (see above). Not sure what is meant by &quot;you just selected&quot; as the IE will occur the instant the unit is created/promoted. Please can someone else confim that EIP 006F3481 is incorrect and remove this entry if so. Although, it begs the question of where this EIP came from? - it was added by DCoder on 2008-03-04 (id 14195))''<br /> :I'm sorry, I made a mistake analyzing that one. I saw it at [http://www.cannis.net/forum/index.php?s=&amp;showtopic=8560&amp;view=findpost&amp;p=170096 C-GEN] and analyzed it. But in fact it was caused by the ''ElitePrimary'' being wrong, not EliteSecondary. (Though 006F352E in your comment has &quot;ElitePrimary&quot; as the cause as well, I assume you meant 004D5108.) Just cause a certain EIP causes an IE, doesn't mean another EIP cannot cause an IE for the same reason - there are quite a lot of code paths in the game, and under certain circumstances the first EIP doesn't get hit. &lt;br&gt;I just reanalyzed the function which both these EIPs fall under, and I can say this: 006F3481 IEs if (Elite)Secondary is broken, 006F352E - if (Elite)Primary is. The function is responsible for selecting which weapon a unit should use against a certain target in idle mode, the EIP you reported above for (Elite)Secondary (004D5108) is correct, but is only hit if the unit is in Guard mode scanning for targets when promotion happens. [maybe this part should go off to a talk page?] ''//[[User:DCoder|DCoder]]''<br /> ''(Just tested this a bit more and got several new EIPs for when the unit was promoted (added in this revision), can't seem to get any consistent results - will need to test this further. //Marshall''<br /> |-<br /> ! {{Anchor|?|eip}}<br /> | Setting {{f|CarryOverCap|0|link}}. Default value is -1, positive values do not cause an IE.<br /> &lt;br&gt;''I have tested this and couldn't get an IE to occur. Are there any specific circumstances that are required to trigger an IE on a map with CarryOverCap=0? Note that, in FA2YR, CarryOverCap defaults to zero so I would expect this IE to have been seen more often if it was really a problem. //Marshall'' <br /> : This setting applies when you progress from one campaign map to another. However, I now see that the default campaigns use 0, so there must be something else amiss. A quick investigation shows that this value is not divided by, so there shouldn't be an exception at all... Will contact Apollo who submitted this as the cause. ''//[[User:DCoder|DCoder]]''<br /> |-<br /> ! {{Anchor|?|eip}}<br /> | Warheads that are not listed under {{tt|[[Warheads|[Warheads]]]}} have been reported to cause an IE, although the exact details are not established. It is not neccessary for every warhead to be listed (for example, removing the Grand Cannon warhead from the list appears to have no effect on the game), however there is no reason not to list every warhead. '''Validity questionable - if someone can replicate this then please provide an except.txt.'''<br /> ''Simply thinking about this, putting warheads on the list should guarantee their position in the internal array, so if there is anywhere that references warheads by internal array position then this is important. However, even if you change an existing weapon's warhead to a non-parsed one in a game mode file, you ''still'' won't get an IE because default warhead values will be used. Because of this, I'm starting to wonder if the reports of un-listed warheads causing an IE are erroneous. If someone can replicate this then please provide an except.txt //Marshall''<br /> : Verified under a debugger - if a weapon exists and links to a warhead that does not, this will not cause an IE, warhead stats will simply remain defaulted. (In other cases, warheads should also remain defaulted but functional. I have not verified every warhead loading location now, but my applicable ini flags tables should indicate whether or not uninited objects cause issues.) ''//[[User:DCoder|DCoder]] 12:44, 11 May 2008 (UTC)''<br /> |-<br /> ! {{Anchor|?|eip}}<br /> | If a falling paratrooper (who has nearly reached the ground) is killed by an area-effect mutation weapon. Point based mutations seem to be okay (the falling paratrooper explodes) and the [[Super weapon:Genetic Mutator|Genetic Mutator]] seems incapable of killing falling paratroopers. If you have an area-effect mutation weapon, you should ensure that all paratroopers are immune to it (this also means that you can't have a buildable paradrop plane and an area-effect mutation weapon in the same mod).<br /> |-<br /> ! {{Anchor|00000000|eip}}<br /> | Placing two buildings on a map in the map editor so that they overlap, and then destroying or garrisoning one of them in-game. Note that this error is intermittent so may not immediately be noticeable. Use [[FinalAlert]]'s {{tt|Options}} {{arr|r}} {{tt|Show Building Outline}} feature to see the actual areas taken up by buildings, since there are some buildings whose foundation is different from their visual size, and make sure you don't have any buildings that overlap.<br /> Given the unusual EIP value (all zeroes) that has been gathered from testing, it may be a corrupt EIP and not a true indication of the source of the error. Note that this EIP has also been gathered from other 'random-EIP' causes.<br /> :Indeed it is not a true indication, EIP 00000000 can be acquired in several ways. If you can provide an except, I will be able to provide more specific details to look for, like in the case of 0045EC90 . ''//[[User:DCoder|DCoder]]'' <br /> |-<br /> ! {{Anchor|004A2684|eip}}<br /> | Starting a game on any map concludes in a &quot;unable to read scenario&quot; error while loading. The cause of this is an empty uimd.ini file or possibly another empty ini file without any content.<br /> ''//[[User:RaVaGe|RaVaGe]]''<br /> |-<br /> ! {{Anchor|007564BD|eip}}<br /> | Internal error when starting a game, possibly caused by attempting to load graphics from a corrupt mix file.<br /> ''//[[User:RaVaGe|RaVaGe]]''<br /> |-<br /> ! {{Anchor|404E0000|eip}} <br /> | Selectable=no on spawned [[AircraftTypes]].<br /> ''// [[User:Bbglas007|Bbglas007]]''<br /> <br /> This error also occurs if there are overlapping structures and/or overlapping rubble on the map and units try to pathfind over them or one of the buildings is destroyed. Keep in mind that an existing building with Image=none (like for example a nuclear silo) still remains its Bib as it is read from art.ini. So if you give a [NUKE] Image=none it still remains its 3x3 Bib, which counts as an overlapping building. In general don't have overlapping buildings on your map.<br /> <br /> ''// [[User:DoctorEvil|DoctorEvil]]'' and ~ [[User:RAZER|RAZER]]<br /> |-<br /> ! {{Anchor|006E2449|eip}} <br /> | This error occurs when you fire a trigger action 42 (Do explosion at...) at an undefined waypoint.<br /> ''// [[User:DoctorEvil|DoctorEvil]]''<br /> |}<br /> <br /> ===Broken-reference Causes===<br /> *Most of the flags that point to an object type do not verify that the object type exists and will try to invoke it anyway. This includes pointers to weapons, projectiles, warheads, particles, particle systems and infantry/unit/aircraft/building types, among other things.<br /> *All object types must be parsed in order for them to be invoked successfully. For example, a weapon must be parsed by being referenced by a unit in the main rules (weapons used in a game mode that aren't referenced in the main rules will not have been parsed, nor will shrapnel weapons that haven't been referenced by a dummy unit).<br /> *Note that all weapons have to specify a {{f|Warhead|link}} tag and the tag must not be blank otherwise an IE will occur. However if the specified {{f|Warhead|link}} does not exist then that will not cause an IE, as the game will use default warhead settings.<br /> *Your object type may not be 'missing' as such, you may just have mis-spelled its ID (e.g. &quot;MagenticBeam&quot; as opposed to &quot;MagneticBeam&quot;). Always check your typing carefully to make sure you don't &lt;!-- irony intended --&gt; any words out.<br /> <br /> ===Tank Bunker / Sell Unit IEs===<br /> *There are two IEs that can occur after using a 'Sell Unit' superweapon on a tank-bunkered unit. Both of these IEs can yield seemingly random EIP values (due to the fact that, when the unit is sold, the building's &quot;BunkeredUnit&quot; pointer isn't cleared and so points to garbage memory. Attempts to dereference it will be met with varying levels of failure).<br /> *An IE may occur the instant you sell the unit.<br /> *If an IE does not occur the instant you sell the unit, then the Tank Bunker will have been rendered unusable as the walls are still up. If the 'broken' Tank Bunker is sold or destroyed then an IE will occur (this IE ''does'' always happen). This IE frequently yields EIP 004593BB, although has been known to yield seemingly random EIP values (for the reason stated above).<br /> *The only way to prevent these IEs is to make sure a player never has access to both the Sell Unit superweapon and the Tank Bunker at the same time. &lt;small&gt;(To achieve this, the building that provides the superweapon must be uncapturable and immune to mind-control as must the Tank Bunker. Further more, unless both buildings are country specials, you will need to remove MCVs from crates and make Construction Yards uncapturable and immune to mind-control too.)&lt;/small&gt;<br /> <br /> ==Software used to find Internal Errors==<br /> *[http://dc.strategy-x.com/checker INI Checker] (can check your rules, art and sound files for syntactic errors like typos and missing references)<br /> *[[ExceptChecker]] (primarily for RockPatch-related IEs, it analyzes except.txt, tries to find references to code added by the patch or known routines, and ''might'' then be able give a direction)<br /> *[[Debugger]] (if you know assembler)<br /> <br /> ==Note==<br /> *After observing [[IE]] for several times, I found that ''' &quot;EIP &quot; ''' that occurs are expressed in categories such as unit errors, image errors, sound errors, configuration + settings errors, etc.<br /> <br /> == See also ==<br /> *[[Reconnection Error]]<br /> *[http://forums.renegadeprojects.com/showthread.php?pid=2034#pid2034 Confirmation the Infantry Linking IE also applies to modifications done by maps]<br /> <br /> [[Category:Bugs_and_Errors]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=FillSilos&diff=28580 2025-05-08T15:59:55Z

<p>Crimsonum: Updated</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Maps}}<br /> |types={{Categ|Basic}}<br /> |values={{Values|boolean}}<br /> |default=no<br /> |ra=yes<br /> |cs=yes<br /> |am=yes<br /> |ts=yes<br /> |fs=yes<br /> |ets=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> <br /> Specifies whether or not all silos and refineries in this [[map]] should be pre-filled with [[Tiberiums|ore/Tiberium]]. This applies to all preplaced structures with a positive {{f|Storage|link}}. The amount of ore/Tiberium stored in the structures is the [[house]]'s starting [[credits|credit amount]] substracted with the [[value]] of the first [[Tiberiums|ore/Tiberium type]]. <br /> <br /> In [[pseudocode]]:<br /> <br /> StoredCredits = House.Credits - Tiberiums[0].Value<br /> <br /> If this amount exceeds the amount of available storage, any excess ore/Tiberium is not stored. Conversely, if a house has zero starting credits, {{f|FillSilos|yes}} will have no effect on the house, even if it owns silos and refineries.<br /> <br /> == Example ==<br /> If a house has 10,000 initial credits, an extra 10,000 credits worth of ore/Tiberium Riparius, minus 25 (the default value of ore/Riparius) will be stored in the house's silos/refineries on map start, provided that the house owns enough silos/refineries to store that amount. Thus the house starts with a total of 10,000 + 10,000 - 25 = 19,975 credits.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Basic&diff=28579 2025-05-08T13:42:40Z

<p>Crimsonum: InitTime is obsolete.</p> <hr /> <div>{{Sectionheader<br /> |files={{Categ|Maps}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> This section defines the 'basic' map properties, such as its name, the map data format, player count, etc, and extra data for singleplayer missions. <br /> <br /> The full list of tags, the value types for them, and a description are below:<br /> {| class=&quot;wikitable&quot;<br /> ! Flag || Value Type || Description<br /> |-<br /> | &lt;tt&gt;Name&lt;/tt&gt; || string || The map name shown in multiplayer map selection<br /> |-<br /> | &lt;tt&gt;Official&lt;/tt&gt; || boolean || Is this a map that shipped with the game, or does it need transferring? (MP)<br /> |-<br /> | &lt;tt&gt;[[NewINIFormat]]&lt;/tt&gt; || int || Version of the map data format used, and which coordinate system is used.<br /> |-<br /> | &lt;tt&gt;[[RequiredAddOn]]&lt;/tt&gt; || boolean || Does this map require an expansion pack? (FS only)<br /> |-<br /> | &lt;tt&gt;FreeRadar&lt;/tt&gt; || boolean || Will the mini-map work without the player owning a [[radar]]?<br /> |-<br /> | &lt;tt&gt;SpeechSide&lt;/tt&gt; || House || Which [[Sides|side's]] EVA are we using today?<br /> |-<br /> | &lt;tt&gt;[[NextScenario]]&lt;/tt&gt; || Map || The next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[AltNextScenario]]&lt;/tt&gt; || Map || The conditional next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[EndOfGame]]&lt;/tt&gt; || boolean || Is this the last mission of the campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipScore]]&lt;/tt&gt; || boolean || Should we display the score screen, or go straight to the debrief?<br /> |-<br /> | &lt;tt&gt;[[OneTimeOnly]]&lt;/tt&gt; || boolean || Is this mission singular, or part of a larger campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipMapSelect]]&lt;/tt&gt; || boolean || Should we display the next campaign screen, or go straight to the mission?<br /> |-<br /> | &lt;tt&gt;[[IgnoreGlobalAITriggers]]&lt;/tt&gt; || boolean || Do we ignore the {{ini|ai}} and only use the map AI?<br /> |-<br /> | &lt;tt&gt;TruckCrate&lt;/tt&gt; || boolean || Does a pre-placed TRUCKB drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;TrainCrate&lt;/tt&gt; || boolean || Does a train with &lt;tt&gt;CarriesCrate=yes&lt;/tt&gt; drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;[[StartingDropships]]&lt;/tt&gt; || int || How many Dropships to load in [[Dropship Loadout]]?<br /> |-<br /> | &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; || list (strings) || A list of units and infantry the player can load onto Dropships in Dropship Loadout.<br /> |-<br /> | &lt;tt&gt;[[AllowableUnitMaximums]]&lt;/tt&gt; || list (ints) || A list of maximum quantities of &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; the player can load onto Dropships.<br /> |-<br /> | &lt;tt&gt;[[Player]]&lt;/tt&gt; || House || Which House/Country does the player belong to?<br /> |-<br /> | &lt;tt&gt;Briefing&lt;/tt&gt; || CSF label || The mission description string.<br /> |-<br /> | &lt;tt&gt;[[TimerInherit]]&lt;/tt&gt; || boolean || Does the mission timer carry over from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[InitTime]]&lt;/tt&gt; || int || (Obsolete)<br /> |-<br /> | &lt;tt&gt;Intro&lt;/tt&gt; || Movie || The name of the movie to play when starting a campaign.<br /> |-<br /> | &lt;tt&gt;Brief&lt;/tt&gt; || Movie || The name of the campaign movie to play before mission selection.<br /> |-<br /> | &lt;tt&gt;Action&lt;/tt&gt; || Movie || The name of the campaign movie to play just before beginning this mission.<br /> |-<br /> | &lt;tt&gt;Win&lt;/tt&gt; || Movie || The name of the campaign movie to play after winning this mission.<br /> |-<br /> | &lt;tt&gt;Lose&lt;/tt&gt; || Movie || The name of the campaign movie to play after losing this mission.<br /> |-<br /> | &lt;tt&gt;PostScore&lt;/tt&gt; || Movie || The name of the campaign movie to play after the campaign.<br /> |-<br /> | &lt;tt&gt;[[PreMapSelect]]&lt;/tt&gt; || Movie || The name of the animation for selecting the next mission. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Theme]]&lt;/tt&gt; || string || The name of the soundtrack from [[Themes]] to play during the mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverMoney]]&lt;/tt&gt; || float|| Percentage of credits carried over from the previous mission. (1.0=100%)<br /> |-<br /> | &lt;tt&gt;[[Percent]]&lt;/tt&gt; || float || (Obsolete)<br /> |-<br /> | &lt;tt&gt;[[CarryOverCap]]&lt;/tt&gt; || int || The maximum credits can we retain from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[FillSilos]]&lt;/tt&gt; || boolean || Do the carry-over credits come in silos that can be lost, or virtual?<br /> |-<br /> | &lt;tt&gt;[[HomeCell]]&lt;/tt&gt; || int || The player starting position [[Waypoints|Waypoint]] in a mission.<br /> |-<br /> | &lt;tt&gt;[[AltHomeCell]]&lt;/tt&gt; || int || Alternate conditional player starting position in a mission.<br /> |-<br /> | &lt;tt&gt;[[CivEvac]]&lt;/tt&gt; || boolean || Should civilian transport units flee the map once loaded with passengers?<br /> |-<br /> | &lt;tt&gt;[[MultiplayerOnly]]&lt;/tt&gt; || boolean || Is this a multiplayer map? (Not definitive!)<br /> |-<br /> | &lt;tt&gt;[[TiberiumGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium fields grow (TS) / does Ore increase in density (RA2)?<br /> |-<br /> | &lt;tt&gt;[[VeinGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium veins spread? (TS only)<br /> |-<br /> | &lt;tt&gt;[[IceGrowthEnabled]]&lt;/tt&gt; || boolean || Do special ice-forming tiles grow to adjacent cells on the map? (TS only)<br /> |-<br /> | &lt;tt&gt;[[TiberiumDeathToVisceroid]]&lt;/tt&gt; || boolean || Do infantry dying of Tiberium exposure become Visceroids? (TS only)<br /> |-<br /> |}<br /> <br /> ==See Also==<br /> [[:Category:{{PAGENAME}} Flags]]<br /> <br /> [[Campaign Progression]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Percent&diff=28578 2025-05-08T13:39:00Z

<p>Crimsonum: This flag has nothing to do with credit carryover.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Maps}}<br /> |types={{Categ|Basic}}<br /> |values={{Values|int|0–100}}<br /> |default=no<br /> |ra=yes<br /> |cs=yes<br /> |am=yes<br /> |ts=yes<br /> |fs=yes<br /> |ets=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |tsobsolete=yes<br /> }}<br /> Specifies the the percent that the computer-controlled base is to be built up to at single-player [[scenario]] start.<br /> <br /> ==See Also==<br /> * [[PercentBuilt]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=InitTime&diff=28577 2025-05-08T13:16:22Z

<p>Crimsonum: Obsolete in all three games. Also, defaults to 10000</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Maps}}<br /> |types={{Categ|Basic}}<br /> |values={{Values|integer}}<br /> |default=10000<br /> |ts=yes<br /> |fs=yes<br /> |ets=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |tsobsolete=yes<br /> }}<br /> Obsolete, doesn't do anything. Was possibly intended to set the mission timer's default value. However, in the released games the timer must be initialized with the [[Actions_(maps)|map trigger action #27]].</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Basic&diff=28567 2025-05-06T07:25:00Z

<p>Crimsonum: Yet more minor tweaks</p> <hr /> <div>{{Sectionheader<br /> |files={{Categ|Maps}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> This section defines the 'basic' map properties, such as its name, the map data format, player count, etc, and extra data for singleplayer missions. <br /> <br /> The full list of tags, the value types for them, and a description are below:<br /> {| class=&quot;wikitable&quot;<br /> ! Flag || Value Type || Description<br /> |-<br /> | &lt;tt&gt;Name&lt;/tt&gt; || string || The map name shown in multiplayer map selection<br /> |-<br /> | &lt;tt&gt;Official&lt;/tt&gt; || boolean || Is this a map that shipped with the game, or does it need transferring? (MP)<br /> |-<br /> | &lt;tt&gt;[[NewINIFormat]]&lt;/tt&gt; || int || Which map data format is used, and which coordinate system is used? <br /> |-<br /> | &lt;tt&gt;[[RequiredAddOn]]&lt;/tt&gt; || boolean || Does this map require an expansion pack? (FS only)<br /> |-<br /> | &lt;tt&gt;FreeRadar&lt;/tt&gt; || boolean || Will the mini-map work without the player owning a [[radar]]?<br /> |-<br /> | &lt;tt&gt;SpeechSide&lt;/tt&gt; || House || Which [[Sides|side's]] EVA are we using today?<br /> |-<br /> | &lt;tt&gt;[[NextScenario]]&lt;/tt&gt; || Map || The next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[AltNextScenario]]&lt;/tt&gt; || Map || The conditional next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[EndOfGame]]&lt;/tt&gt; || boolean || Is this the last mission of the campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipScore]]&lt;/tt&gt; || boolean || Should we display the score screen, or go straight to the debrief?<br /> |-<br /> | &lt;tt&gt;[[OneTimeOnly]]&lt;/tt&gt; || boolean || Is this mission singular, or part of a larger campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipMapSelect]]&lt;/tt&gt; || boolean || Should we display the next campaign screen, or go straight to the mission?<br /> |-<br /> | &lt;tt&gt;[[IgnoreGlobalAITriggers]]&lt;/tt&gt; || boolean || Do we ignore the {{ini|ai}} and only use the map AI?<br /> |-<br /> | &lt;tt&gt;TruckCrate&lt;/tt&gt; || boolean || Does a pre-placed TRUCKB drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;TrainCrate&lt;/tt&gt; || boolean || Does a train with &lt;tt&gt;CarriesCrate=yes&lt;/tt&gt; drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;[[StartingDropships]]&lt;/tt&gt; || int || How many Dropships to load in [[Dropship Loadout]]?<br /> |-<br /> | &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; || list (strings) || A list of units and infantry the player can load onto Dropships in Dropship Loadout.<br /> |-<br /> | &lt;tt&gt;[[AllowableUnitMaximums]]&lt;/tt&gt; || list (ints) || A list of maximum quantities of &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; the player can load onto Dropships.<br /> |-<br /> | &lt;tt&gt;[[Player]]&lt;/tt&gt; || House || Which House/Country does the player belong to?<br /> |-<br /> | &lt;tt&gt;Briefing&lt;/tt&gt; || CSF label || The mission description string.<br /> |-<br /> | &lt;tt&gt;[[TimerInherit]]&lt;/tt&gt; || boolean || Does the mission timer carry over from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[InitTime]]&lt;/tt&gt; || int || Set the starting time on the mission timer.<br /> |-<br /> | &lt;tt&gt;Intro&lt;/tt&gt; || Movie || The name of the movie to play when starting a campaign.<br /> |-<br /> | &lt;tt&gt;Brief&lt;/tt&gt; || Movie || The name of the campaign movie to play before mission selection.<br /> |-<br /> | &lt;tt&gt;Action&lt;/tt&gt; || Movie || The name of the campaign movie to play just before beginning this mission.<br /> |-<br /> | &lt;tt&gt;Win&lt;/tt&gt; || Movie || The name of the campaign movie to play after winning this mission.<br /> |-<br /> | &lt;tt&gt;Lose&lt;/tt&gt; || Movie || The name of the campaign movie to play after losing this mission.<br /> |-<br /> | &lt;tt&gt;PostScore&lt;/tt&gt; || Movie || The name of the campaign movie to play after the campaign.<br /> |-<br /> | &lt;tt&gt;[[PreMapSelect]]&lt;/tt&gt; || Movie || The name of the animation for selecting the next mission. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Theme]]&lt;/tt&gt; || string || The name of the soundtrack from [[Themes]] to play during the mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverMoney]]&lt;/tt&gt; || boolean || Should we carry-over credits from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[Percent]]&lt;/tt&gt; || float || Percentage of credits carried over from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverCap]]&lt;/tt&gt; || int || The maximum credits can we retain from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[FillSilos]]&lt;/tt&gt; || boolean || Do the carry-over credits come in silos that can be lost, or virtual?<br /> |-<br /> | &lt;tt&gt;[[HomeCell]]&lt;/tt&gt; || int || The player starting position [[Waypoints|Waypoint]] in a mission.<br /> |-<br /> | &lt;tt&gt;[[AltHomeCell]]&lt;/tt&gt; || int || Alternate conditional player starting position in a mission.<br /> |-<br /> | &lt;tt&gt;[[CivEvac]]&lt;/tt&gt; || boolean || Should civilian transport units flee the map once loaded with passengers?<br /> |-<br /> | &lt;tt&gt;[[MultiplayerOnly]]&lt;/tt&gt; || boolean || Is this a multiplayer map? (Not definitive!)<br /> |-<br /> | &lt;tt&gt;[[TiberiumGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium fields grow (TS) / does Ore increase in density (RA2)?<br /> |-<br /> | &lt;tt&gt;[[VeinGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium veins spread? (TS only)<br /> |-<br /> | &lt;tt&gt;[[IceGrowthEnabled]]&lt;/tt&gt; || boolean || Do special ice-forming tiles grow to adjacent cells on the map? (TS only)<br /> |-<br /> | &lt;tt&gt;[[TiberiumDeathToVisceroid]]&lt;/tt&gt; || boolean || Do infantry dying of Tiberium exposure become Visceroids? (TS only)<br /> |-<br /> |}<br /> <br /> ==See Also==<br /> [[:Category:{{PAGENAME}} Flags]]<br /> <br /> [[Campaign Progression]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Basic&diff=28566 2025-05-06T07:19:05Z

<p>Crimsonum: Some minor tweaks</p> <hr /> <div>{{Sectionheader<br /> |files={{Categ|Maps}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> This section defines the 'basic' map properties, such as its name, the map data format, player count, etc, and extra data for singleplayer missions. <br /> <br /> The full list of tags, the value types for them, and a description are below:<br /> {| class=&quot;wikitable&quot;<br /> ! Flag || Value Type || Description<br /> |-<br /> | &lt;tt&gt;Name&lt;/tt&gt; || string || The map name shown in multiplayer map selection<br /> |-<br /> | &lt;tt&gt;Official&lt;/tt&gt; || boolean || Is this a map that shipped with the game, or does it need transferring? (MP)<br /> |-<br /> | &lt;tt&gt;[[NewINIFormat]]&lt;/tt&gt; || int || Which map data format is used, and which coordinate system is used? <br /> |-<br /> | &lt;tt&gt;[[RequiredAddOn]]&lt;/tt&gt; || boolean || Does this map require an expansion/mod? (MP)<br /> |-<br /> | &lt;tt&gt;FreeRadar&lt;/tt&gt; || boolean || Will the mini-map work without the player owning a Radar?<br /> |-<br /> | &lt;tt&gt;SpeechSide&lt;/tt&gt; || House || Which [[Sides]] EVA are we using today?<br /> |-<br /> | &lt;tt&gt;[[NextScenario]]&lt;/tt&gt; || Map || The next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[AltNextScenario]]&lt;/tt&gt; || Map || The conditional next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[EndOfGame]]&lt;/tt&gt; || boolean || Is this the last mission of the campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipScore]]&lt;/tt&gt; || boolean || Should we display the score screen, or go straight to the debrief?<br /> |-<br /> | &lt;tt&gt;[[OneTimeOnly]]&lt;/tt&gt; || boolean || Is this mission singular, or part of a larger campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipMapSelect]]&lt;/tt&gt; || boolean || Should we display the next campaign screen, or go straight to the mission?<br /> |-<br /> | &lt;tt&gt;[[IgnoreGlobalAITriggers]]&lt;/tt&gt; || boolean || Do we ignore the {{ini|ai}} and only use the map AI?<br /> |-<br /> | &lt;tt&gt;TruckCrate&lt;/tt&gt; || boolean || Does a pre-placed TRUCKB drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;TrainCrate&lt;/tt&gt; || boolean || Does a train with &lt;tt&gt;CarriesCrate=yes&lt;/tt&gt; drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;[[StartingDropships]]&lt;/tt&gt; || int || How many Dropships to load in [[Dropship Loadout]]?<br /> |-<br /> | &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; || list (strings) || A list of units and infantry the player can load onto Dropships in Dropship Loadout.<br /> |-<br /> | &lt;tt&gt;[[AllowableUnitMaximums]]&lt;/tt&gt; || list (ints) || A list of maximum quantities of &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; the player can load onto Dropships.<br /> |-<br /> | &lt;tt&gt;[[Player]]&lt;/tt&gt; || House || Which House/Country does the player belong to?<br /> |-<br /> | &lt;tt&gt;Briefing&lt;/tt&gt; || CSF label || The mission description string.<br /> |-<br /> | &lt;tt&gt;[[TimerInherit]]&lt;/tt&gt; || boolean || Does the mission timer carry over from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[InitTime]]&lt;/tt&gt; || int || Set the starting time on the mission timer.<br /> |-<br /> | &lt;tt&gt;Intro&lt;/tt&gt; || Movie || The name of the movie to play when starting a campaign.<br /> |-<br /> | &lt;tt&gt;Brief&lt;/tt&gt; || Movie || The name of the campaign movie to play before mission selection.<br /> |-<br /> | &lt;tt&gt;Action&lt;/tt&gt; || Movie || The name of the campaign movie to play just before beginning this mission.<br /> |-<br /> | &lt;tt&gt;Win&lt;/tt&gt; || Movie || The name of the campaign movie to play after winning this mission.<br /> |-<br /> | &lt;tt&gt;Lose&lt;/tt&gt; || Movie || The name of the campaign movie to play after losing this mission.<br /> |-<br /> | &lt;tt&gt;PostScore&lt;/tt&gt; || Movie || The name of the campaign movie to play after the campaign.<br /> |-<br /> | &lt;tt&gt;[[PreMapSelect]]&lt;/tt&gt; || Movie || The name of the animation for selecting the next mission. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Theme]]&lt;/tt&gt; || string || The name of the soundtrack from [[Themes]] to play during the mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverMoney]]&lt;/tt&gt; || boolean || Should we carry-over credits from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[Percent]]&lt;/tt&gt; || float || Percentage of credits carried over from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverCap]]&lt;/tt&gt; || int || The maximum credits can we retain from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[FillSilos]]&lt;/tt&gt; || boolean || Do the carry-over credits come in silos that can be lost, or virtual?<br /> |-<br /> | &lt;tt&gt;[[HomeCell]]&lt;/tt&gt; || int || The player starting position [[Waypoints|Waypoint]] in a mission.<br /> |-<br /> | &lt;tt&gt;[[AltHomeCell]]&lt;/tt&gt; || int || Alternate conditional player starting position in a mission.<br /> |-<br /> | &lt;tt&gt;[[CivEvac]]&lt;/tt&gt; || boolean || Should civilian transport units flee the map once loaded with passengers?<br /> |-<br /> | &lt;tt&gt;[[MultiplayerOnly]]&lt;/tt&gt; || boolean || Is this a multiplayer map? (Not definitive!)<br /> |-<br /> | &lt;tt&gt;[[TiberiumGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium fields grow (TS) / does Ore increase in density (RA2)?<br /> |-<br /> | &lt;tt&gt;[[VeinGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium veins spread? (TS only)<br /> |-<br /> | &lt;tt&gt;[[IceGrowthEnabled]]&lt;/tt&gt; || boolean || Do special ice-forming tiles grow to adjacent cells on the map? (TS only)<br /> |-<br /> | &lt;tt&gt;[[TiberiumDeathToVisceroid]]&lt;/tt&gt; || boolean || Do infantry dying of Tiberium exposure become Visceroids? (TS only)<br /> |-<br /> |}<br /> <br /> ==See Also==<br /> [[:Category:{{PAGENAME}} Flags]]<br /> <br /> [[Campaign Progression]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Dropship_loadout&diff=28565 2025-05-06T07:12:23Z

<p>Crimsonum: Crimsonum moved page Dropship loadout to Dropship Loadout: Misspelled title</p> <hr /> <div>#REDIRECT [[Dropship Loadout]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Dropship_Loadout&diff=28564 2025-05-06T07:12:23Z

<p>Crimsonum: Crimsonum moved page Dropship loadout to Dropship Loadout: Misspelled title</p> <hr /> <div>[[File:Dropship_loadout.jpg|right|frame|Example of what the Dropship loadout looks like in {{ts}}.]]<br /> The dropship loadout is a feature that was cut from Tiberian Sun late in its development and presists in a somewhat buggy form in RA2 and YR. In TS, the feature was to present the player with a screen where he could purchase units that would be delivered to him as a scripted reinforcement during the mission that followed. The feature can be made to work ''almost'' perfectly for single player missions. Note the bugs section below.<br /> <br /> The loadout feature can also be set on multiplayer maps, causing all players to get the chance to select units, irrespective of their side actually having a suitable reinforcement [[trigger]] or not. Note that the game will time-out if any player is delayed at the screen.<br /> <br /> ==Using The Loadout Screen==<br /> To access the loadout screen prior to a mission, the map file must have {{sl|Basic|StartingDropships}} specified. The value for the flag must be either 1, 2 or 3 and specifies how many dropships the player will be able to specify the contents of. To actually recieve the reinforcements, there must be a reinforcement [[trigger]] that creates a [[TeamTypes|team]] with only a [[IsDropship|Dropship]] unit in the [[TaskForces|taskforce]]. The transport will automatically be filled with the units ordered.<br /> <br /> The player can be limited in several ways as to what they can buy. First of all, they are limited to units that have the player house/country set in the units' {{f|Owner|link}} entry. In RA2, the loadout ignores {{f|RequiredHouses|link}}, {{f|ForbiddenHouses|link}}, and {{f|RequiresStolenXTech|link}}. There are controls available that can adjust what the player can and cannot purchase as a reinforcement however, as well as how many of each unit. Both of these controls are specified in a map's {{sl|Basic}} section as well. {{f|AllowableUnits|link}} specifies what units are available to purchase using a comma-separated list and is based on the unit section names from {{ini|rules}}. {{f|AllowableUnitMaximums|link}} is another comma-separated list that has the same number of entries as {{f|AllowableUnits}} and sets the number of each unit that is allowed to be purchased (-1 gives unlimited). The [[TechLevel|tech level]] of the player house/country will also limit what can be purchased unless overriden with {{f|AllowableUnits}}. The amount of credit available to buy units is the amount set to be available for the player house, if no credit is available it seems to give an IE when you exit the screen (in RA2 at least).<br /> <br /> {{bugs}}<br /> === Bugs in all applicable games ===<br /> * The mouse cursor is invisible, making it difficult to select units. An easy fix for this in TS is to place mouse.shp file in cache.mix. <br /> * The screen doesn't make it clear that to progress from it, the player needs to press the space key.<br /> * Bugs related to {{f|AllowableUnitMaximums|link}}, see the flag page for more information.<br /> === Bugs in RA2 and YR only ===<br /> * The screen uses the wrong character set for describing the units before purchase.<br /> * The box draw around icons when they are highlighted is the wrong size, due to changes in the icon size used by RA2.<br /> * The artwork for the screen obviously does not fit vanilla RA2.<br /> **<br /> **<br /> **<br /> **<br /> **<br /> === Although the interface of this feature can still be used in RA2 and YR, it only has screen effects. ===<br /> === [[DropShip does not carry the units selected by the player on the preload interface.]] ===<br /> This bug has been fixed in '''[[RockPatch]]''', including its successors [[NPatch]], NPEXT, NPSE2.0, etc., which can ensure the normal operation of this logic.<br /> <br /> However, this fix is not available in the original RA2 and YR, as well as in the more frequent and widely used [[Ares]] and [[Phobos]] series of patch that are now in use.<br /> <br /> _(:з」∠)_<br /> <br /> [[Category: General Editing Information]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Basic&diff=28563 2025-05-06T07:10:14Z

<p>Crimsonum: Dropship loadout is functional in RA2/YR, albeit glitchy</p> <hr /> <div>{{Sectionheader<br /> |files={{Categ|Maps}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> This section defines the 'basic' map properties, such as its name, the map data format, player count, etc, and extra data for singleplayer missions. <br /> <br /> The full list of tags, the value types for them, and a description are below:<br /> {| class=&quot;wikitable&quot;<br /> ! Flag || Value Type || Description<br /> |-<br /> | &lt;tt&gt;Name&lt;/tt&gt; || string || The map name shown in multiplayer map selection<br /> |-<br /> | &lt;tt&gt;Official&lt;/tt&gt; || boolean || Is this a map that shipped with the game, or does it need transferring? (MP)<br /> |-<br /> | &lt;tt&gt;[[NewINIFormat]]&lt;/tt&gt; || int || Which map data format is used, and which coordinate system is used? <br /> |-<br /> | &lt;tt&gt;[[RequiredAddOn]]&lt;/tt&gt; || boolean || Does this map require an expansion/mod? (MP)<br /> |-<br /> | &lt;tt&gt;FreeRadar&lt;/tt&gt; || boolean || Will the mini-map work without the player owning a Radar?<br /> |-<br /> | &lt;tt&gt;SpeechSide&lt;/tt&gt; || House || Which [[Sides]] EVA are we using today?<br /> |-<br /> | &lt;tt&gt;[[NextScenario]]&lt;/tt&gt; || Map || The next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[AltNextScenario]]&lt;/tt&gt; || Map || The conditional next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[EndOfGame]]&lt;/tt&gt; || boolean || Is this the last mission of the campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipScore]]&lt;/tt&gt; || boolean || Should we display the score screen, or go straight to the debrief?<br /> |-<br /> | &lt;tt&gt;[[OneTimeOnly]]&lt;/tt&gt; || boolean || Is this mission singular, or part of a larger campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipMapSelect]]&lt;/tt&gt; || boolean || Should we display the next campaign screen, or go straight to the mission?<br /> |-<br /> | &lt;tt&gt;[[IgnoreGlobalAITriggers]]&lt;/tt&gt; || boolean || Do we ignore the {{ini|ai}} and only use the map AI?<br /> |-<br /> | &lt;tt&gt;TruckCrate&lt;/tt&gt; || boolean || Does a pre-placed TRUCKB drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;TrainCrate&lt;/tt&gt; || boolean || Does a train with &lt;tt&gt;CarriesCrate=yes&lt;/tt&gt; drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;[[StartingDropships]]&lt;/tt&gt; || int || Should we display the Dropship Loadout screen?<br /> |-<br /> | &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; || list (strings) || A list of units and infantry a player can load onto Dropships.<br /> |-<br /> | &lt;tt&gt;[[AllowableUnitMaximums]]&lt;/tt&gt; || list (ints) || A list of quantities of &lt;tt&gt;AllowablUnits&lt;/tt&gt; we can load only Dropships.<br /> |-<br /> | &lt;tt&gt;[[Player]]&lt;/tt&gt; || House || Which House/Country does the player belong to?<br /> |-<br /> | &lt;tt&gt;Briefing&lt;/tt&gt; || CSF label || The mission description string.<br /> |-<br /> | &lt;tt&gt;[[TimerInherit]]&lt;/tt&gt; || boolean || Does the mission timer carry over from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[InitTime]]&lt;/tt&gt; || int || Set the starting time on the mission timer.<br /> |-<br /> | &lt;tt&gt;Intro&lt;/tt&gt; || Movie || The name of the movie to play when starting a campaign.<br /> |-<br /> | &lt;tt&gt;Brief&lt;/tt&gt; || Movie || The name of the campaign movie to play before mission selection.<br /> |-<br /> | &lt;tt&gt;Action&lt;/tt&gt; || Movie || The name of the campaign movie to play just before beginning this mission.<br /> |-<br /> | &lt;tt&gt;Win&lt;/tt&gt; || Movie || The name of the campaign movie to play after winning this mission.<br /> |-<br /> | &lt;tt&gt;Lose&lt;/tt&gt; || Movie || The name of the campaign movie to play after losing this mission.<br /> |-<br /> | &lt;tt&gt;PostScore&lt;/tt&gt; || Movie || The name of the campaign movie to play after the campaign.<br /> |-<br /> | &lt;tt&gt;[[PreMapSelect]]&lt;/tt&gt; || Movie || The name of the animation for selecting the next mission. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Theme]]&lt;/tt&gt; || string || The name of the soundtrack from [[Themes]] to play during the mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverMoney]]&lt;/tt&gt; || boolean || Should we carry-over credits from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[Percent]]&lt;/tt&gt; || float || Percentage of credits carried over from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverCap]]&lt;/tt&gt; || int || The maximum credits can we retain from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[FillSilos]]&lt;/tt&gt; || boolean || Do the carry-over credits come in silos that can be lost, or virtual?<br /> |-<br /> | &lt;tt&gt;[[HomeCell]]&lt;/tt&gt; || int || The player starting position [[Waypoints|Waypoint]] in a mission.<br /> |-<br /> | &lt;tt&gt;[[AltHomeCell]]&lt;/tt&gt; || int || Alternate conditional player starting position in a mission.<br /> |-<br /> | &lt;tt&gt;[[CivEvac]]&lt;/tt&gt; || boolean || Should civilian transport units flee the map once loaded with passengers?<br /> |-<br /> | &lt;tt&gt;[[MultiplayerOnly]]&lt;/tt&gt; || boolean || Is this a multiplayer map? (Not definitive!)<br /> |-<br /> | &lt;tt&gt;[[TiberiumGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium fields grow (TS) / does Ore increase in density (RA2)?<br /> |-<br /> | &lt;tt&gt;[[VeinGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium veins spread? (TS only)<br /> |-<br /> | &lt;tt&gt;[[IceGrowthEnabled]]&lt;/tt&gt; || boolean || Do special ice-forming tiles grow to adjacent cells on the map? (TS only)<br /> |-<br /> | &lt;tt&gt;[[TiberiumDeathToVisceroid]]&lt;/tt&gt; || boolean || Do infantry dying of Tiberium exposure become Visceroids? (TS only)<br /> |-<br /> |}<br /> <br /> ==See Also==<br /> [[:Category:{{PAGENAME}} Flags]]<br /> <br /> [[Campaign Progression]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Basic&diff=28562 2025-05-06T07:06:54Z

<p>Crimsonum: Add table header</p> <hr /> <div>{{Sectionheader<br /> |files={{Categ|Maps}}<br /> |ts=yes<br /> |fs=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> This section defines the 'basic' map properties, such as its name, the map data format, player count, etc, and extra data for singleplayer missions. <br /> <br /> The full list of tags, the value types for them, and a description are below:<br /> {| class=&quot;wikitable&quot;<br /> ! Flag || Value Type || Description<br /> |-<br /> | &lt;tt&gt;Name&lt;/tt&gt; || string || The map name shown in multiplayer map selection<br /> |-<br /> | &lt;tt&gt;Official&lt;/tt&gt; || boolean || Is this a map that shipped with the game, or does it need transferring? (MP)<br /> |-<br /> | &lt;tt&gt;[[NewINIFormat]]&lt;/tt&gt; || int || Which map data format is used, and which coordinate system is used? <br /> |-<br /> | &lt;tt&gt;[[RequiredAddOn]]&lt;/tt&gt; || boolean || Does this map require an expansion/mod? (MP)<br /> |-<br /> | &lt;tt&gt;FreeRadar&lt;/tt&gt; || boolean || Will the mini-map work without the player owning a Radar?<br /> |-<br /> | &lt;tt&gt;SpeechSide&lt;/tt&gt; || House || Which [[Sides]] EVA are we using today?<br /> |-<br /> | &lt;tt&gt;[[NextScenario]]&lt;/tt&gt; || Map || The next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[AltNextScenario]]&lt;/tt&gt; || Map || The conditional next mission map in a singleplayer campaign.<br /> |-<br /> | &lt;tt&gt;[[EndOfGame]]&lt;/tt&gt; || boolean || Is this the last mission of the campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipScore]]&lt;/tt&gt; || boolean || Should we display the score screen, or go straight to the debrief?<br /> |-<br /> | &lt;tt&gt;[[OneTimeOnly]]&lt;/tt&gt; || boolean || Is this mission singular, or part of a larger campaign?<br /> |-<br /> | &lt;tt&gt;[[SkipMapSelect]]&lt;/tt&gt; || boolean || Should we display the next campaign screen, or go straight to the mission?<br /> |-<br /> | &lt;tt&gt;[[IgnoreGlobalAITriggers]]&lt;/tt&gt; || boolean || Do we ignore the {{ini|ai}} and only use the map AI?<br /> |-<br /> | &lt;tt&gt;TruckCrate&lt;/tt&gt; || boolean || Does a pre-placed TRUCKB drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;TrainCrate&lt;/tt&gt; || boolean || Does a train with &lt;tt&gt;CarriesCrate=yes&lt;/tt&gt; drop a Crate when destroyed?<br /> |-<br /> | &lt;tt&gt;[[StartingDropships]]&lt;/tt&gt; || int || Should we display the Dropship Loadout screen? (TS only)<br /> |-<br /> | &lt;tt&gt;[[AllowableUnits]]&lt;/tt&gt; || list (strings) || A list of units and infantry a player can load onto Dropships. (TS only)<br /> |-<br /> | &lt;tt&gt;[[AllowableUnitMaximums]]&lt;/tt&gt; || list (ints) || A list of quantities of &lt;tt&gt;AllowablUnits&lt;/tt&gt; we can load only Dropships. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Player]]&lt;/tt&gt; || House || Which House/Country does the player belong to?<br /> |-<br /> | &lt;tt&gt;Briefing&lt;/tt&gt; || CSF label || The mission description string.<br /> |-<br /> | &lt;tt&gt;[[TimerInherit]]&lt;/tt&gt; || boolean || Does the mission timer carry over from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[InitTime]]&lt;/tt&gt; || int || Set the starting time on the mission timer.<br /> |-<br /> | &lt;tt&gt;Intro&lt;/tt&gt; || Movie || The name of the movie to play when starting a campaign.<br /> |-<br /> | &lt;tt&gt;Brief&lt;/tt&gt; || Movie || The name of the campaign movie to play before mission selection.<br /> |-<br /> | &lt;tt&gt;Action&lt;/tt&gt; || Movie || The name of the campaign movie to play just before beginning this mission.<br /> |-<br /> | &lt;tt&gt;Win&lt;/tt&gt; || Movie || The name of the campaign movie to play after winning this mission.<br /> |-<br /> | &lt;tt&gt;Lose&lt;/tt&gt; || Movie || The name of the campaign movie to play after losing this mission.<br /> |-<br /> | &lt;tt&gt;PostScore&lt;/tt&gt; || Movie || The name of the campaign movie to play after the campaign.<br /> |-<br /> | &lt;tt&gt;[[PreMapSelect]]&lt;/tt&gt; || Movie || The name of the animation for selecting the next mission. (TS only)<br /> |-<br /> | &lt;tt&gt;[[Theme]]&lt;/tt&gt; || string || The name of the soundtrack from [[Themes]] to play during the mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverMoney]]&lt;/tt&gt; || boolean || Should we carry-over credits from the previous mission?<br /> |-<br /> | &lt;tt&gt;[[Percent]]&lt;/tt&gt; || float || Percentage of credits carried over from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[CarryOverCap]]&lt;/tt&gt; || int || The maximum credits can we retain from the previous mission.<br /> |-<br /> | &lt;tt&gt;[[FillSilos]]&lt;/tt&gt; || boolean || Do the carry-over credits come in silos that can be lost, or virtual?<br /> |-<br /> | &lt;tt&gt;[[HomeCell]]&lt;/tt&gt; || int || The player starting position [[Waypoints|Waypoint]] in a mission.<br /> |-<br /> | &lt;tt&gt;[[AltHomeCell]]&lt;/tt&gt; || int || Alternate conditional player starting position in a mission.<br /> |-<br /> | &lt;tt&gt;[[CivEvac]]&lt;/tt&gt; || boolean || Should civilian transport units flee the map once loaded with passengers?<br /> |-<br /> | &lt;tt&gt;[[MultiplayerOnly]]&lt;/tt&gt; || boolean || Is this a multiplayer map? (Not definitive!)<br /> |-<br /> | &lt;tt&gt;[[TiberiumGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium fields grow (TS) / does Ore increase in density (RA2)?<br /> |-<br /> | &lt;tt&gt;[[VeinGrowthEnabled]]&lt;/tt&gt; || boolean || Do Tiberium veins spread? (TS only)<br /> |-<br /> | &lt;tt&gt;[[IceGrowthEnabled]]&lt;/tt&gt; || boolean || Do special ice-forming tiles grow to adjacent cells on the map? (TS only)<br /> |-<br /> | &lt;tt&gt;[[TiberiumDeathToVisceroid]]&lt;/tt&gt; || boolean || Do infantry dying of Tiberium exposure become Visceroids? (TS only)<br /> |-<br /> |}<br /> <br /> ==See Also==<br /> [[:Category:{{PAGENAME}} Flags]]<br /> <br /> [[Campaign Progression]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Template:F&diff=28560 2025-05-02T19:14:35Z

<p>Crimsonum: Added a more legible primary font</p> <hr /> <div>&lt;includeonly&gt;&lt;span style=&quot;font-family: 'Lucida Console', monospace;&quot;&gt;{{#if: {{{3|}}} | [[{{{1|Template:F}}}|{{#explode:{{{1|'''ERROR''' no flag provided in Template:F.}}}|#|0}}={{{2|}}}]] | {{#ifeq: {{lc:{{{2|}}}}} | link | [[{{{1|Template:F}}}|{{#explode:{{{1|'''ERROR''' no flag provided in Template:F.}}}|#|0}}]] | {{{1|'''ERROR''' no flag provided in [[Template:F]].}}}{{#if: {{{2|}}} | ={{{2|}}} |}} }} }}&lt;/span&gt;&lt;/includeonly&gt;&lt;noinclude&gt;<br /> {{Doc}}&lt;/noinclude&gt;</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Template:F&diff=28559 2025-05-02T19:00:18Z

<p>Crimsonum: Restored missing font style.</p> <hr /> <div>&lt;includeonly&gt;&lt;span style=&quot;font-family: monospace;&quot;&gt;{{#if: {{{3|}}} | [[{{{1|Template:F}}}|{{#explode:{{{1|'''ERROR''' no flag provided in Template:F.}}}|#|0}}={{{2|}}}]] | {{#ifeq: {{lc:{{{2|}}}}} | link | [[{{{1|Template:F}}}|{{#explode:{{{1|'''ERROR''' no flag provided in Template:F.}}}|#|0}}]] | {{{1|'''ERROR''' no flag provided in [[Template:F]].}}}{{#if: {{{2|}}} | ={{{2|}}} |}} }} }}&lt;/span&gt;&lt;/includeonly&gt;&lt;noinclude&gt;<br /> {{Doc}}&lt;/noinclude&gt;</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Smoke&diff=28558 2025-05-02T18:57:29Z

<p>Crimsonum: This is obsolete in TS as well. Updated.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Rules(md).ini}}<br /> |values=Strings (names of [[Animations]])<br /> |special=none<br /> |default=none<br /> |types={{Categ|AudioVisual}}<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |tsobsolete=yes<br /> }}<br /> Although this flag is parsed, it doesn't do anything, therefore it is entirely obsolete.<br /> <br /> In {{ra}}, buildings have a chance of emitting smoke when destroyed. The logic is hardcoded to spawn the {{tt|SMOKE_M}} animation type. {{f|Smoke}} was added during {{ts}}'s development likely to unhardcode this logic, however the logic ended up scrapped.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Talk:Voxel&diff=28556 2025-04-29T14:30:33Z

<p>Crimsonum: Created page with &quot;==Wobble Bug== To-do: the voxel wobble bug needs to be documented. See [https://ppmforums.com/post-562075/the-most-annoying-ts-engine-bugs/#562075 this PPM post] for more info (requires login) as well as [https://github.com/Vinifera-Developers/Vinifera/issues/66 this Vinifera issue].&lt;br/&gt; – ~~~~&quot;</p> <hr /> <div>==Wobble Bug==<br /> To-do: the voxel wobble bug needs to be documented. See [https://ppmforums.com/post-562075/the-most-annoying-ts-engine-bugs/#562075 this PPM post] for more info (requires login) as well as [https://github.com/Vinifera-Developers/Vinifera/issues/66 this Vinifera issue].&lt;br/&gt;<br /> – [[User:Crimsonum|Crimsonum]] ([[User talk:Crimsonum|talk]]) 16:30, 29 April 2025 (CEST)</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Voxel&diff=28555 2025-04-29T14:25:35Z

<p>Crimsonum: Better wording.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|bool}}<br /> |default=no<br /> |types={{CatAllTypes}},[[Image]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> A voxel, or volumetric pixel, is a three-dimensional analogy of a pixel. The file extension for voxel files is {{tt|.VXL}}. Voxels may be virtually any colour (assuming the colour is utilised in the palette of the game or voxel editor)and can use surface normals. Voxels may also be animated with the use of an HVA file, but there are limits in the Tiberian Sun and Red Alert 2 engines as to what unit types may use certain types of animations. For example, in Tiberian Sun, an aircraft type may not utilise a turret animation.<br /> <br /> Voxels are usually used to render vehicles and turrets in the Tiberian Sun and Red Alert 2 engines, whereas SHP files are generally used for infantry units and buildings. This is due to hard-coded restrictions in the game engines, and also because SHPs are usually of a higher in-game quality than voxels. <br /> <br /> It is worth noting that units which are comprised of voxels will tilt while walking up a slope in the aforementioned engines, whereas an SHP unit, such as the Titan or Wolverine, will not. Voxels are generally used for the turrets of SHP buildings such as the Sentry Gun or Grand Cannon, because they allow 360 degree rotation of the turret, without the need for the facings that would be used in an SHP.<br /> <br /> *It's a surprising thing. For SHP file name &lt;u&gt;&lt;b&gt;&lt;font style=&quot;color:lightgreen&gt;&quot;place&quot;&lt;/font&gt;&lt;/b&gt;&lt;/u&gt; &lt;u&gt;&lt;b&gt;(SHP file for placing buildings)&lt;/b&gt;&lt;/u&gt;It can slope along sloped areas. Wrong with general SHP files!<br /> <br /> [[File:place.png]]<br /> <br /> *&lt;u&gt;&lt;b&gt;[[Animations]]&lt;/b&gt;&lt;/u&gt; that is defined in the section. The &lt;u&gt;&lt;b&gt;[[AnimList]]&lt;/b&gt;&lt;/u&gt; of weapons in &lt;u&gt;&lt;b&gt;[[AirburstWeapon]]&lt;/b&gt;&lt;/u&gt; can be tilted when It is played on a sloping surface.<br /> [[File:AnimationSlope.png]]<br /> <br /> ==Format==<br /> {{Stub}}<br /> [insert more info here, re: sections and stuff]&lt;br&gt;<br /> The individual voxels (in terms of volumetric pixels) are stored as a series of five values in WW's voxel format: The X, Y and Z position of the voxel, the color index, and the normal index.&lt;br&gt;<br /> The what color which the color index stands for depends on the palette the voxel is displayed with; what angle a normals value indicates depends on the normals generation and the normals array value for the index.<br /> <br /> Voxels cannot be larger than 255x255x255, and have severe graphical problems, such as artifacting and palette errors at such a length on any axis{{fnl|1}}. This could be a major setback for some types of voxel, such as especially long ships or aircraft, but not a big problem with most voxels which are generally no larger than 100 on the z axis.<br /> <br /> In addition to the .VXL file, all voxels must have a .HVA file, which defines the location the voxel occupies in 3 dimensional space relative to 0 on the X,Y,Z axes. THe HVA is also used to line up turrets and barrels vertically and change the point around which the voxels rotate, and to animate multi-sectioned voxels.<br /> Without an HVA, voxels cause an internal error.<br /> <br /> Multi-sectioned voxels are made up of a hierarchy of voxels within on .VXL This is most obvious in Tiberian Sun's Mammoth MK2, which was a singe .VXL file comprising the body, each upper and each lower leg, and each foot, for a total of 13 voxel objects in the file. This was paired with a more involved HVA that usual to give the unit a walking animation. The same process is used on a much smaller scale in the construction of helicopter units for RA2/YR, where the rotors are a separate section but not a separate file, making it easy to animate.<br /> There are no other examples in the vanilla games, but there have been a substantial number of multisectioned voxels released in the modding community.<br /> <br /> ==Rendering==<br /> <br /> ===Scale===<br /> <br /> {|<br /> |- style=&quot;vertical-align:top;&quot;<br /> |style=&quot;padding-left: 0;&quot;|When drawn parallel to the camera, or the player's point of view, the voxel-to-pixel ratio is exactly 1:1. For example, on default scale a voxel model that is 60 voxels long, when rotated to face sideways to the player PoV, will also appear as 60 pixels long.<br /> <br /> When rotated, voxels are transformed to appear isometric. In {{ts}}, a flat, square voxel model with length and width of 34 voxels will near perfectly fit within one cell. For {{ra2}}, this number is 43. Exact cell dimensions, in voxels, would be 33.94112 and 42.4264 for TS and RA2, respectively.<br /> <br /> One voxel equals approximately 6 (more specifically 6.03397) [[leptons]]. This is true for both TS and RA2, as leptons are relative to cell size.<br /> <br /> While the size of individual voxels cannot be altered, the voxel model's canvas can be changed using voxel/[[HVA]] bounds. This increases or decreases the space between the individual voxels, effectively exploding or shrinking the model. See [[voxel bounds]] for more information.<br /> |[[File:Voxel_test_1.png|thumb|Demonstrating {{ra2}} voxel scale with a voxel cube that fits as perfectly as possible in one [[cell]]. The model's dimensions are 43x43x43 voxels.]]<br /> |[[File:Voxel_test_2.png|thumb|The same cube, rotated to face the &quot;camera&quot;. Notice how the cube now appears exactly 43 pixels wide.]]<br /> |}<br /> <br /> ===Rotation===<br /> In-game, a voxel model has a total of 32,768 possible facings (32 facings per axis). Each facing is rendered only on demand, then cached for future use during the game session. This improves performance and conserves memory, a strategy needed especially at the time the games were made.<br /> <br /> ===Layering===<br /> {|<br /> |- style=&quot;vertical-align:top;&quot;<br /> |style=&quot;padding-left: 0;&quot;|On voxel models with multiple sections, the drawing order is determined by the size and position of the sections. The sections are drawn in the order of their ''canvas&lt;nowiki&gt;'&lt;/nowiki&gt;'' proximity &quot;to the screen&quot;, or the player's point of view, at any given angle, with the section closest to the player's view drawn on top. The [[HVA]] determines how voxel sections are positioned relative to one another.<br /> [[Turret|Turrets]] and barrels are layered in a more strict manner: The turret is always drawn above the body as if it were a regular tank. Similarly, if the unit has a barrel, the barrel is drawn above the turret, but only when the turret is facing towards the player's point of view.<br /> |[[File:TS_turret_barrel_configuration.gif|thumb|Demonstrating voxel turret/barrel drawing order.]]<br /> |}<br /> ==See also==<br /> *[[Normals]]<br /> *[[HVA]]<br /> *[[Voxel bounds]]<br /> *[[Voxel turret and barrel positioning]]<br /> *[http://www.sleipnirstuff.com/forum/viewtopic.php?f=11&amp;p=237785#237785 Brief explanation of how WW's voxel format looks like]<br /> *[http://www.sleipnirstuff.com/forum/viewtopic.php?t=8048 Perfect normals discovery thread]<br /> <br /> ==Footnotes==<br /> {{fn|1|Only conclusively tested in Tiberian Sun, but there is no reason to conclude that it is not a problem in RA2 - might require testing}}</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Voxel&diff=28554 2025-04-29T14:14:24Z

<p>Crimsonum: Previous info turned out to be wrong, very wrong.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|bool}}<br /> |default=no<br /> |types={{CatAllTypes}},[[Image]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> }}<br /> A voxel, or volumetric pixel, is a three-dimensional analogy of a pixel. The file extension for voxel files is {{tt|.VXL}}. Voxels may be virtually any colour (assuming the colour is utilised in the palette of the game or voxel editor)and can use surface normals. Voxels may also be animated with the use of an HVA file, but there are limits in the Tiberian Sun and Red Alert 2 engines as to what unit types may use certain types of animations. For example, in Tiberian Sun, an aircraft type may not utilise a turret animation.<br /> <br /> Voxels are usually used to render vehicles and turrets in the Tiberian Sun and Red Alert 2 engines, whereas SHP files are generally used for infantry units and buildings. This is due to hard-coded restrictions in the game engines, and also because SHPs are usually of a higher in-game quality than voxels. <br /> <br /> It is worth noting that units which are comprised of voxels will tilt while walking up a slope in the aforementioned engines, whereas an SHP unit, such as the Titan or Wolverine, will not. Voxels are generally used for the turrets of SHP buildings such as the Sentry Gun or Grand Cannon, because they allow 360 degree rotation of the turret, without the need for the facings that would be used in an SHP.<br /> <br /> *It's a surprising thing. For SHP file name &lt;u&gt;&lt;b&gt;&lt;font style=&quot;color:lightgreen&gt;&quot;place&quot;&lt;/font&gt;&lt;/b&gt;&lt;/u&gt; &lt;u&gt;&lt;b&gt;(SHP file for placing buildings)&lt;/b&gt;&lt;/u&gt;It can slope along sloped areas. Wrong with general SHP files!<br /> <br /> [[File:place.png]]<br /> <br /> *&lt;u&gt;&lt;b&gt;[[Animations]]&lt;/b&gt;&lt;/u&gt; that is defined in the section. The &lt;u&gt;&lt;b&gt;[[AnimList]]&lt;/b&gt;&lt;/u&gt; of weapons in &lt;u&gt;&lt;b&gt;[[AirburstWeapon]]&lt;/b&gt;&lt;/u&gt; can be tilted when It is played on a sloping surface.<br /> [[File:AnimationSlope.png]]<br /> <br /> ==Format==<br /> {{Stub}}<br /> [insert more info here, re: sections and stuff]&lt;br&gt;<br /> The individual voxels (in terms of volumetric pixels) are stored as a series of five values in WW's voxel format: The X, Y and Z position of the voxel, the color index, and the normal index.&lt;br&gt;<br /> The what color which the color index stands for depends on the palette the voxel is displayed with; what angle a normals value indicates depends on the normals generation and the normals array value for the index.<br /> <br /> Voxels cannot be larger than 255x255x255, and have severe graphical problems, such as artifacting and palette errors at such a length on any axis{{fnl|1}}. This could be a major setback for some types of voxel, such as especially long ships or aircraft, but not a big problem with most voxels which are generally no larger than 100 on the z axis.<br /> <br /> In addition to the .VXL file, all voxels must have a .HVA file, which defines the location the voxel occupies in 3 dimensional space relative to 0 on the X,Y,Z axes. THe HVA is also used to line up turrets and barrels vertically and change the point around which the voxels rotate, and to animate multi-sectioned voxels.<br /> Without an HVA, voxels cause an internal error.<br /> <br /> Multi-sectioned voxels are made up of a hierarchy of voxels within on .VXL This is most obvious in Tiberian Sun's Mammoth MK2, which was a singe .VXL file comprising the body, each upper and each lower leg, and each foot, for a total of 13 voxel objects in the file. This was paired with a more involved HVA that usual to give the unit a walking animation. The same process is used on a much smaller scale in the construction of helicopter units for RA2/YR, where the rotors are a separate section but not a separate file, making it easy to animate.<br /> There are no other examples in the vanilla games, but there have been a substantial number of multisectioned voxels released in the modding community.<br /> <br /> ==Rendering==<br /> <br /> ===Scale===<br /> <br /> {|<br /> |- style=&quot;vertical-align:top;&quot;<br /> |style=&quot;padding-left: 0;&quot;|When drawn parallel to the camera, or the player's point of view, the voxel-to-pixel ratio is exactly 1:1. For example, on default scale a voxel model that is 60 voxels long, when rotated to face sideways to the player PoV, will also appear as 60 pixels long.<br /> <br /> When rotated, voxels are transformed to appear isometric. In {{ts}}, a flat, square voxel model with length and width of 34 voxels will near perfectly fit within one cell. For {{ra2}}, this number is 43. Exact cell dimensions, in voxels, would be 33.94112 and 42.4264 for TS and RA2, respectively.<br /> <br /> One voxel equals approximately 6 (more specifically 6.03397) [[leptons]]. This is true for both TS and RA2, as leptons are relative to cell size.<br /> <br /> While the size of individual voxels cannot be altered, the voxel model's canvas can be changed using voxel/[[HVA]] bounds. This increases or decreases the space between the individual voxels, effectively exploding or shrinking the model. See [[voxel bounds]] for more information.<br /> |[[File:Voxel_test_1.png|thumb|Demonstrating {{ra2}} voxel scale with a voxel cube that fits as perfectly as possible in one [[cell]]. The model's dimensions are 43x43x43 voxels.]]<br /> |[[File:Voxel_test_2.png|thumb|The same cube, rotated to face the &quot;camera&quot;. Notice how the cube now appears exactly 43 pixels wide.]]<br /> |}<br /> <br /> ===Rotation===<br /> In-game, a voxel model has a total of 32,768 possible facings (32 facings per axis). Each facing is rendered only on demand, then cached for future use during the game session. This improves performance and conserves memory, a strategy needed especially at the time the games were made.<br /> <br /> ===Layering===<br /> {|<br /> |- style=&quot;vertical-align:top;&quot;<br /> |style=&quot;padding-left: 0;&quot;|On voxel models with multiple sections, the drawing order is determined by the size and position of the sections. Whichever section's canvas reaches the lowest depth in-game (lowest position on the Z-axis, i.e. &quot;closest to the screen&quot;), at any given angle, will be drawn on top, and subsequent sections are drawn in order on the depth axis. The [[HVA]] determines how voxel sections are positioned relative to one another.<br /> [[Turret|Turrets]] and barrels are layered in a more strict manner: The turret is always drawn above the body as if it were a regular tank. Similarly, if the unit has a barrel, the barrel is drawn above the turret, but only when the turret is facing towards the player's point of view.<br /> |[[File:TS_turret_barrel_configuration.gif|thumb|Demonstrating voxel turret/barrel drawing order.]]<br /> |}<br /> ==See also==<br /> *[[Normals]]<br /> *[[HVA]]<br /> *[[Voxel bounds]]<br /> *[[Voxel turret and barrel positioning]]<br /> *[http://www.sleipnirstuff.com/forum/viewtopic.php?f=11&amp;p=237785#237785 Brief explanation of how WW's voxel format looks like]<br /> *[http://www.sleipnirstuff.com/forum/viewtopic.php?t=8048 Perfect normals discovery thread]<br /> <br /> ==Footnotes==<br /> {{fn|1|Only conclusively tested in Tiberian Sun, but there is no reason to conclude that it is not a problem in RA2 - might require testing}}</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnimDamaged&diff=28553 2025-04-26T11:22:39Z

<p>Crimsonum: Better and more consistent phrasing.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Defines the [[animation]] to use instead of [[SpecialAnim]] when this building is active, but damaged to or below the [[ConditionYellow]] threshold. See {{f|SpecialAnim|link}} for more information the where and when special animations are used.<br /> <br /> == See Also ==<br /> *[[SpecialAnim]]<br /> *[[SpecialAnimTwoDamaged]]<br /> *[[SpecialAnimThreeDamaged]]<br /> *[[SpecialAnimFourDamaged]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnimDamaged&diff=28552 2025-04-26T08:12:52Z

<p>Crimsonum: Removed redundant information already found on the main SpecialAnim page. Also added links to related flags.</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Special animation to use when the [[BuildingTypes|building]] is damaged. See {{f|SpecialAnim|link}} for more information on special animations.<br /> <br /> == See Also ==<br /> *[[SpecialAnim]]<br /> *[[SpecialAnimTwoDamaged]]<br /> *[[SpecialAnimThreeDamaged]]<br /> *[[SpecialAnimFourDamaged]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnim&diff=28551 2025-04-26T08:09:58Z

<p>Crimsonum: add &#039;see also&#039; section</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies a special animation attached to this building. The condition and function of the animation depends on the building type:<br /> * [[Storage|Tiberium/Ore silo]] fill animation (requires {{f|SiloDamage|yes|link}})<br /> * First stage of the [[UnitRepair|service depot/repair depot/naval yard]] vehicle/ship repair animation<br /> * [[IsAnimDelayedFire|Weapon]] charging animation<br /> * [[Grinding|Grinder]] grinding animation<br /> * [[Bunker|Tank bunker]] extend animation to appear in front of the tank<br /> <br /> {{Bugs}}<br /> * In {{ra2}} and {{yr}}, using special anims with refineries gives highly unusual results; if the harvester has no ore, then the animation will not be played at all. It appears that the animation plays frames, up to a short but unknown limit, depending on how much ore the harvester deposits. Presumably this is part of an unused logic to play an 'ore dumping' animation.<br /> * If {{f|SpecialAnim}} is used with {{f|IsAnimDelayedFire|link}} and all related flags, the {{f|Image|link}} from {{f|Primary|link}} and {{f|ElitePrimary|link}} is ignored.<br /> <br /> ==See Also==<br /> * [[SpecialAnimDamaged]]<br /> * [[SpecialAnimTwo]]<br /> * [[SpecialAnimThree]]<br /> * [[SpecialAnimFour]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SiloDamage&diff=28550 2025-04-26T08:05:27Z

<p>Crimsonum: Created page with &quot;{{Flag |name={{PAGENAME}} |files={{Categ|Art(md).ini}} |values={{Values|bool}} |default=no |types=BuildingTypes |ts=yes |fs=yes |hp=yes |ra2=yes |yr=yes |ares=yes }} Specifies whether or not this building&#039;s image should be based on its current Tiberium storage level. This enables the building to use {{f|SpecialAnim|link}} for the storage fill animation. ==See Also== * SpecialAnim&quot;</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|bool}}<br /> |default=no<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies whether or not this building's image should be based on its current [[Storage|Tiberium storage level]]. This enables the building to use {{f|SpecialAnim|link}} for the storage fill animation.<br /> <br /> ==See Also==<br /> * [[SpecialAnim]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=Talk:SpecialAnim&diff=28549 2025-04-26T07:57:50Z

<p>Crimsonum: Created page with &quot;==Redundant information or wrong wording?== This part is weird: If SpecialAnim is used with IsAnimDelayedFire and all related flags, the Image from Primary and ElitePrimary is ignored. Is it trying to say that Image on the weapon is not drawn? Weapons don&#039;t use images, so that&#039;s pointless information. If it&#039;s instead trying to say that the building&#039;s image is not drawn when the building uses these weapons, then this bit needs to be reworded. – ~~~~&quot;</p> <hr /> <div>==Redundant information or wrong wording?==<br /> This part is weird:<br /> If SpecialAnim is used with IsAnimDelayedFire and all related flags, the Image from Primary and ElitePrimary is ignored.<br /> Is it trying to say that Image on the weapon is not drawn? Weapons don't use images, so that's pointless information.<br /> <br /> If it's instead trying to say that the building's image is not drawn when the building uses these weapons, then this bit needs to be reworded.<br /> <br /> – [[User:Crimsonum|Crimsonum]] ([[User talk:Crimsonum|talk]]) 09:57, 26 April 2025 (CEST)</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnim&diff=28548 2025-04-26T07:54:34Z

<p>Crimsonum: Updated</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> Specifies a special animation attached to this building. The condition and function of the animation depends on the building type:<br /> * [[Storage|Tiberium/Ore silo]] fill animation (requires {{f|SiloDamage|yes|link}})<br /> * First stage of the [[UnitRepair|service depot/repair depot/naval yard]] vehicle/ship repair animation<br /> * [[IsAnimDelayedFire|Weapon]] charging animation<br /> * [[Grinding|Grinder]] grinding animation<br /> * [[Bunker|Tank bunker]] extend animation to appear in front of the tank<br /> <br /> {{Bugs}}<br /> * In {{ra2}} and {{yr}}, using special anims with refineries gives highly unusual results; if the harvester has no ore, then the animation will not be played at all. It appears that the animation plays frames, up to a short but unknown limit, depending on how much ore the harvester deposits. Presumably this is part of an unused logic to play an 'ore dumping' animation.<br /> * If {{f|SpecialAnim}} is used with {{f|IsAnimDelayedFire|link}} and all related flags, the {{f|Image|link}} from {{f|Primary|link}} and {{f|ElitePrimary|link}} is ignored.</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnimFourDamaged&diff=28547 2025-04-26T07:29:43Z

<p>Crimsonum: Created page with &quot;{{Flag |name={{PAGENAME}} |files={{Categ|Art(md).ini}} |values={{Values|string|{{Categ|Animations}}}} |default=none |types=BuildingTypes |yr=yes |ares=yes }} Used solely by tank bunkers to specify the damaged version of the part of the retracting bunker wall animation that should appear behind the tank. ==See Also== * SpecialAnimFour * SpecialAnim * SpecialAnimTwo * SpecialAnimThree&quot;</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Used solely by [[Bunker|tank bunkers]] to specify the damaged version of the part of the retracting bunker wall animation that should appear behind the tank.<br /> <br /> ==See Also==<br /> * [[SpecialAnimFour]]<br /> * [[SpecialAnim]]<br /> * [[SpecialAnimTwo]]<br /> * [[SpecialAnimThree]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnimFour&diff=28546 2025-04-26T07:28:55Z

<p>Crimsonum: Created page with &quot;{{Flag |name={{PAGENAME}} |files={{Categ|Art(md).ini}} |values={{Values|string|{{Categ|Animations}}}} |default=none |types=BuildingTypes |yr=yes |ares=yes }} Used solely by tank bunkers to specify the part of the retracting bunker wall animation that should appear behind the tank. ==See Also== * SpecialAnimFourDamaged * SpecialAnim * SpecialAnimTwo * SpecialAnimThree&quot;</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Used solely by [[Bunker|tank bunkers]] to specify the part of the retracting bunker wall animation that should appear behind the tank.<br /> <br /> ==See Also==<br /> * [[SpecialAnimFourDamaged]]<br /> * [[SpecialAnim]]<br /> * [[SpecialAnimTwo]]<br /> * [[SpecialAnimThree]]</div>

Crimsonum https://modenc2.markjfox.net/index.php?title=SpecialAnimThree&diff=28545 2025-04-26T07:27:31Z

<p>Crimsonum: c&amp;p error</p> <hr /> <div>{{Flag<br /> |name={{PAGENAME}}<br /> |files={{Categ|Art(md).ini}}<br /> |values={{Values|string|{{Categ|Animations}}}}<br /> |default=none<br /> |types=[[BuildingTypes]]<br /> |ts=yes<br /> |fs=yes<br /> |hp=yes<br /> |ra2=yes<br /> |yr=yes<br /> |ares=yes<br /> }}<br /> <br /> Used by [[UnitRepair|service/repair depots and naval yards]] to specify the closing repair animation. It is also used by [[Bunker|tank bunkers]] to specify the part of the retracting bunker wall animation that should appear in front of the tank.<br /> <br /> ==See Also==<br /> * [[SpecialAnimThreeDamaged]]<br /> * [[SpecialAnim]]<br /> * [[SpecialAnimTwo]]<br /> * [[SpecialAnimFour]]</div>

Crimsonum