Interesting. The API quickstart guide doesn't mention nukes in it's chart of attacker/target %'s.
Speaking of silos, I'm trying to wrap my head around some kind of way to perfectly sync every volley of nukes silos launch, and just can't seem to make any progress.
Currently, my code maps out nearly every possible 'safe' position to place something. Safe meaning not too close to a city. Next, it pseudo-randomly places a single silo and then clusters the rest around that silo starting with a tight ring and fanning out till all silos are placed. This seems to give a good cluster at a decent speed (1.2~1.5 on the clock at 20x) and in a good enough variation that nobody can easily predict silo placement. I.e. it does a fairly decent job simulating human placement. In addition, it will work with totally random cities (even 50).
The problem lies with isolating the silo furthest away from Target1, firing only one nuke, and then linking all the rest of the silos to that nuke and its Target1 (each next silo firing at the appropriate time). Repeat for Target2 (and the first firing silo may not be the same).
I have a master table of all units and can (thanks to Montyphy and Martin) grab all units of a type and team (all my silos) and I also have a master table of all cites (again can filter), but can't seem to link the two. Edit: I can fire my silos and tell them to target the same cities, but can't stagger the launch (fire in proper sequence).
In short:
Imagine I want to hit the three circled cities and have all six silos land their nukes at the exact same time on each city. For New York, I would start with the silos on the left and fire in sequence to the right. I would do the opposite for San Francisco (fire from right to left). For Houston (?), I would fire from top to bottom.
And yes, the bot did place the silos above. I've abandoned perfectly stacked double row placement as dynamically synced launching will make that unnecessary.