Jump to content

Veinhole: Difference between revisions

From ModEnc²
en>DCoder
No edit summary
 
m 6 revisions imported
 
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{DeeZireInclusion}}<br />
{{Flag
Can be set to 'yes' or 'no' and is used to specify that this warhead is a veinhole. This remains residual from Tiberian Sun and does not reflect the existence of the Veinhole Monster. The effect of this is that any units with ImmuneToVeins=yes set can not be affected or targeted by this warhead. In effect, this allows you to add a custom weapon thus make exceptions to what it can affect and target.
|name={{PAGENAME}}
|files={{Categ|ini=rules}}
|values={{values|boolean}}
|default=false
|types={{Categ|Warhead|Warheads}}
|ts=yes
|fs=yes
|ets=yes
|ra2obsolete=yes
}}
 
If set to 'true', this warhead cannot affect objects which have {{f|ImmuneToVeins|yes|link}}.
 
In YR, this flag is still parsed, but does not have any effect. The same appears to also be the case for plain RA2 1.006.

Latest revision as of 22:11, 31 March 2025

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: Veinhole
File(s): rules(md).ini
Values: Boolean values: yes or no, true or false, 1 or 0
Default: false
Applicable to: Warheads

Logic related to Veinhole, as a whole or in part, is obsolete in Red Alert 2 and/or Yuri's Revenge.



If set to 'true', this warhead cannot affect objects which have ImmuneToVeins=yes.

In YR, this flag is still parsed, but does not have any effect. The same appears to also be the case for plain RA2 1.006.