quote:
Originally posted by Lastseer:
Then CI comes down to who is spending more on intelligence. If he outspends you offsensively, he gets you. If your defense outspends his offense, then you're safe.
But it ought to be based only on RECENT spending. Why should large sums of money spent on CI twenty years ago protect you now? An Intel upstart willing to pour tons of resources into his current projects should be able to beat someone who's been investing in CI for a long time at a low level. I think that is why I/CI projects cost finite amounts.
The solution, IMHO, is to have CI points "hang around" for a while after the project completes. The simplest way would be to lose a certain percent each turn before adding in the newly acquired CI points. Something like this:
CI=CI*0.9+(NewCI)
In any case, you're definitely right that CI projects shouldn't automatically synchronize over time. That's a rip-off. Could you counter that by making different CI projects (all at the same level) that take different amounts of time to complete? You might be able to get the same effect that I've proposed above, without requiring reprogramming from MM.
Re: Proposed counter intelligence fix
Threaded Mode