Quote:
Originally Posted by DRG
If you shift the fire mission with a spotter THAT becomes your new spotter for that fire mission. By using that new spotter to shift fire you have put him in control of it
|
I see. What happens in the spotter is killed? Does accuracy depend on who has been the spotter during the pre-mission delay or on the active spotter at the moment the salvo is delivered?
Suppose I planned a mission from the HQ with the standard 3.3-turn delay, and only in the third turn did my observer team manage to gain a height commanding a good view of the enemy. Should I hurry to the Bombardment screen and reassign the existing mission to the observers by a small shift, even at the expense of a short extra delay? Will it increase the accuracy of a) this mission or b) of the following repeat missions, supposedly due to the spotter's noting where the shots land and reporting it back for correction?
Quote:
Originally Posted by DRG
There is nothing that reports spotter X is controlling fire mission Y so yes, if you use more than one spotter you have to keep track yourself but it's really just a matter of keeping the spotter with the best view of the target as the one that shifts fire
|
Understood, but this is quite inconvenient because one must take utmost care in ensuring that one orders repeat missions and shifts existing ones on behalf of the right spotter.
With several active spotters and many artillery units, it means that the user must cycle through his spotters, which is not easy, opening the bombardment screen for each and giving orders to that spotter's artillery units. It would be much better if shifts and repeat missions for all artillery could be managed in a single visit to the Bombardment screen, without the risk of choosing the wrong spotter or the wrong artillery unit during the more tedious procedure required in the current version.
IMHO, spotters-artillery assignments should be
- transparent, i.e. the user should be able to see which spotters are currently working with which artillery, and
- stable, i.e. it shouldn't be so easy accidentally to mix them up while correcting or repeating existing missions.