Jump to content

AmbientChangeRate: Difference between revisions

From ModEnc²
m 4 revisions imported
Rain-Islet (talk | contribs)
m [bot] Batch update {{Bugs}} templates.
 
Line 14: Line 14:
{{fn|1|on default speed, meaning 900 [[frames]].}}
{{fn|1|on default speed, meaning 900 [[frames]].}}


{{bugs}}
=={{bugs}}==


If {{f|{{PAGENAME}}}} is defined in [[map]] code, you must also redefine {{f|ExtraUnitLight|link}}, {{f|ExtraInfantryLight|link}} and {{f|ExtraAircraftLight|link}}, else these are reset to [[rules]] value without decimal component.
If {{f|{{PAGENAME}}}} is defined in [[map]] code, you must also redefine {{f|ExtraUnitLight|link}}, {{f|ExtraInfantryLight|link}} and {{f|ExtraAircraftLight|link}}, else these are reset to [[rules]] value without decimal component.

Latest revision as of 17:08, 2 July 2025

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: AmbientChangeRate
File(s): rules(md).ini
Values: Floating point values: Any decimal number (clearer range should be added in Template:Values).
Applicable to: AudioVisual


Specifies the default rate at which ambient light is recalculated. When the ambient lighting level in a map is changed via trigger action #73, the game waits this many minutes1 between each step of lighting increase or decrease. This delay can be changed with action #72. The actual amount of lighting changed in each step is defined by AmbientChangeStep.

1 on default speed, meaning 900 frames.

Bugs/Side-Effects/Unexpected Limitations

If AmbientChangeRate is defined in map code, you must also redefine ExtraUnitLight, ExtraInfantryLight and ExtraAircraftLight, else these are reset to rules value without decimal component.

See Also