ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
AmbientChangeRate: Difference between revisions
Jump to navigation
Jump to search
m Added into the new bugs category. |
mNo edit summary |
||
| Line 16: | Line 16: | ||
{{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 | 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. | ||
==See Also== | ==See Also== | ||
Latest revision as of 13:46, 4 December 2020
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.