AmbientChangeStep: Difference between revisions
en>Crimsonum m Added into the new bugs category. |
en>E1 Elite mNo edit summary |
||
| Line 14: | Line 14: | ||
{{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== | ||
Revision as of 15:46, 4 December 2020
|
|
|
|
|
|
| Flag: | AmbientChangeStep |
| 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 amount of ambient light to change on each "step" of ambient light recalculations. When the ambient lighting level in a map is changed via trigger action #73, the map's Ambient value (or IonAmbient, if Ion Storm/Lightning Storm is active) is increased or decreased in steps by this amount until it reaches the new level. This amount can be changed with action #71. The default delay between each step is defined by AmbientChangeRate.
Bugs/Side-Effects/Unexpected Limitations
If AmbientChangeStep is defined in map code, you must also redefine ExtraUnitLight, ExtraInfantryLight and ExtraAircraftLight, else these are reset to rules value without decimal component.