RadLevelDelay: Difference between revisions
en>DCoder Rewrite, math comment |
en>Nighthawk200 m Template Updated |
||
| Line 3: | Line 3: | ||
|files={{Categ|Rules(md).ini}} | |files={{Categ|Rules(md).ini}} | ||
|values=unsigned integers | |values=unsigned integers | ||
|default=no | |default=no | ||
|types={{Categ|Radiation|N/A}} | |types={{Categ|Radiation|N/A}} | ||
| | |ra2=yes | ||
|yr=yes | |||
|rp=yes | |||
}} | }} | ||
Revision as of 11:35, 2 April 2007
|
|
|
|
|
|
| Flag: | RadLevelDelay |
| File(s): | Rules(md).ini |
| Values: | unsigned integers |
| Default: | no |
| Applicable to: | N/A |
Delay, in frames, between radiation level recalculations. This means, although the radiation is reapplied every RadApplicationDelay frames, and the site exists for RadDurationMultiple * RadLevel frames, the actual radiation level in the zone is recalculated only this often.
(If you graph radiation level in the site's center over time, X axis - time, Y axis - radiation level, the rad level theoretically would be a straight line. But in fact it will be a "staircase" just above that line. A crude graphical explanation where red line = theoretical values, black blocks - factual values. So, the larger this value, the wider each stairstep.)