Jump to content

ChronoReinfDelay: Difference between revisions

From ModEnc²
en>DCoder
No edit summary
 
m 7 revisions imported
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{DeeZireInclusion}}<br />
{{Flag
The delay, in frames, that units remain 'static' after being teleported to the player through the 'reinforce by chronoshift' trigger within a map file (for example as seen in the final Allied mission in the single player campaign).
|values={{Values|unsigned integers}}
|default=180 ;<del>60</del>
|types={{Categ|General}}
|ra2=yes
|yr=yes
|rp=yes
}}
'''ChronoReinfDelay''' specifies the delay in frames that units will take to fully "phase in" after being given to a player via the "reinforce by chronoshift" map trigger. This is needed because the units are simply created where they are reinforced to, rather than being teleported some distance; thus the normal chronoshift algorithm cannot be used to determine the delay.

Latest revision as of 21:38, 31 March 2025

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: ChronoReinfDelay
File(s): rules(md).ini
Values: Unsigned integers: All non-negative whole numbers from 0 to either 32767, 2147483647 or 4294967295.
Default: 180 ;60
Applicable to: General


ChronoReinfDelay specifies the delay in frames that units will take to fully "phase in" after being given to a player via the "reinforce by chronoshift" map trigger. This is needed because the units are simply created where they are reinforced to, rather than being teleported some distance; thus the normal chronoshift algorithm cannot be used to determine the delay.