NoMovingFire: Difference between revisions
m 4 revisions imported |
Rain-Islet (talk | contribs) m [bot] Batch update {{Bugs}} templates. |
||
| Line 13: | Line 13: | ||
Since a vehicle will normally cease moving if it is within firing range anyway, the difference between {{f|NoMovingFire|yes|link}} and the default behavior is usually negligible, especially for vehicles without [[turret]]s.<br> | Since a vehicle will normally cease moving if it is within firing range anyway, the difference between {{f|NoMovingFire|yes|link}} and the default behavior is usually negligible, especially for vehicles without [[turret]]s.<br> | ||
{{Bugs}} | =={{Bugs}}== | ||
At least in {{ts}}, the flag doesn't work as expected. Units can still fire while moving, and [[ROF]] gets reset when the unit stops, allowing it to immediately fire again. | At least in {{ts}}, the flag doesn't work as expected. Units can still fire while moving, and [[ROF]] gets reset when the unit stops, allowing it to immediately fire again. | ||
Latest revision as of 17:39, 2 July 2025
|
|
|
|
|
|
| Flag: | NoMovingFire |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | no |
| Applicable to: | VehicleTypes |
This flag specifies whether or not a vehicle must stop moving completely before firing its weapon.
Since a vehicle will normally cease moving if it is within firing range anyway, the difference between NoMovingFire=yes and the default behavior is usually negligible, especially for vehicles without turrets.
Bugs/Side-Effects/Unexpected Limitations
At least in Tiberian Sun, the flag doesn't work as expected. Units can still fire while moving, and ROF gets reset when the unit stops, allowing it to immediately fire again.