Posts made by ggyyggyy

The WORK/MOVE only miner will drop all energy in the ground, and then you can pickup the energy from the ground with the CARRY/MOVE creeps

I write a little script, like the following

Creep.prototype.transferEnergyAndMove = function(mysource) {

if(this.transferEnergy(mysource) == ERR_NOT_IN_RANGE) {
    var startCpu = Game.getUsedCpu();     
this.moveTo(mysource,{reusePath:9,serializeMemory:true});

var elapsed = Game.getUsedCpu() - startCpu;
console.log(' transferEnergyAndMove has used '+elapsed+' CPU time');   

}

};

and the results shock to me ,
[10:13:57] transferEnergyAndMove has used 0.30031800000000075 CPU time
[10:13:59] transferEnergyAndMove has used 0.3367020000000007 CPU time
[10:14:02] transferEnergyAndMove has used 0.323207 CPU time
[10:14:05] transferEnergyAndMove has used 0.3165210000000016 CPU time
[10:14:07] transferEnergyAndMove has used 13.078899999999999 CPU time
[10:14:10] transferEnergyAndMove has used 0.3080759999999998 CPU time
[10:14:10] transferEnergyAndMove has used 1.7853649999999988 CPU time

What the terrible CPU time use like that 'transferEnergyAndMove has used 13.078899999999999 CPU time', how to do reduce this!? Any good methods to replace the moveTo() !?

There is no different if your # of MOVE larger than # of other parts. Add MOVE parts cannot help you move faster.