1. Any sort of report that is made (contact, spotting, kills claimed, losses, etc) generates radio traffic that can lead to intercept and a SIGINT spotting. We only track the "highest" level of spotting, so a unit already spotted visually is not checked for SIGINT, since a visual spotting is more precise than a SIGINT cut. These are tagged to the reporting unit.
2. Orders also generate radio events. All Orders radio traffic is tagged to the HiHQ. Orders issued during pre-game setup or on the turn of arrival for a reinforcement unit are not counted as distributed by radio.
3. Radio traffic continues even when you issue no orders due to reporting by subordinate units.
4. The game checks for SIGINT detection for each order issued . And with each order given (edit: since the previous orders phase), the chance of detection at that point increases. So, you issue lots of orders, there's lots of die rolling, with the odds getting slightly worse for you with each die roll. The main contributor to being detected by SIGINT is the level of EW burden.
5. HQ survivability: Yes, keep it moving. You want to set up a rhythm of alternating HQ move orders and subordinate unit orders. By this I mean, you don't want to be giving out a slew or orders to line units and arty barrage orders when your HQ is sitting still and also order the HQ to move at the same time. That's inviting an arty strike during command delay, as you've seen. I plot long moves (back and forth, too) for my HQs. I check the last waypoint time and make sure it extends past the next estimated command cycle time. If it doesn't, then what I do depends on if I give few or many orders. If few orders, then I'll issue a new move order. If many (10+), then I'll move the waypoint so the HQ will stay moving the whole turn.
The above doesn't guarantee you HQ won't take arty or rocket fire, but it will mitigate it. This is an interesting read.
< Message edited by IronMikeGolf -- 9/19/2019 5:19:35 PM >