Hi,
So in parts of the docs and the helper popups, it is repeated that moveTo, or more over the path finding code underneath, uses a lot of CPU. I have gotten the point where my CPU is getting to 17/20, I have a few rooms. So i am looking for targets to reduce that CPU. An obvious one, is do more with less creeps, however once you hit that limit, should I be putting time into movement code. It seems like a lot of effort to me, to solve this problem, when I could be doing more interesting challenges.
MY question is, have people found this to be one of their biggest challenges as they expand, have they implemented custom code to get around path finding over head? Or is there other hidden things to look out for with higher CPU?
Would it logically follow that a distance further away, would take more CPU, to calculate the path finding for?
Cheers