How is constant CPU cost applied?

Reply to How is constant CPU cost applied? on Wed, 31 Jan 2018 15:54:21 GMT

MrFaul — Wed, 31 Jan 2018 15:54:21 GMT

I didn't find any information on this but when exactly is the const CPU cost applied on the function call or only if it is successfully scheduled?

Also only for one action or every call that is possible?

In example for two creep.move() calls on the same creep to change direction in a last minute attempt.

Reply to How is constant CPU cost applied? on Invalid Date

starwar15432 — Invalid Date

If the function returns OK then you are charged to CONST cpu cost

Reply to How is constant CPU cost applied? on Wed, 31 Jan 2018 15:15:56 GMT

MrFaul — Wed, 31 Jan 2018 15:15:56 GMT

So that means:

creep.move(TOP) // blocked ->neglected cost 
creep.move(RIGHT) // possible -> 0.2 cost
// More code something happens
creep.move(DOWN) // possible -> 0.2 cost again

Right? or did I misunderstood something?

Reply to How is constant CPU cost applied? on Wed, 31 Jan 2018 15:33:56 GMT

PostCrafter — Wed, 31 Jan 2018 15:33:56 GMT

Sounds about right, except that each type of intent will only cost once for each creep. If your creep moves once and changes it mind in the same tick and moves somewhere else the constant cost is only applied for the first move call. In your example above this means that the constant cost will only be applied to creep.move(RIGHT).

Also keep in mind that multiple creeps trying to move to the same tile, interacting with the same object or conflicting actions will not conflict with each other inside your code, they will both return OK and the constant cost will be applied multiple times, even if only one of those actions is actually executed.

Reply to How is constant CPU cost applied? on Invalid Date

MrFaul — Invalid Date

Thx for the info.

Reply to How is constant CPU cost applied? on Thu, 01 Feb 2018 07:49:17 GMT

Dissi — Thu, 01 Feb 2018 07:49:17 GMT

@mrfaul said in How is constant CPU cost applied?:

So that means:

creep.move(TOP) // blocked ->neglected cost <<<<<< this is consuming 0.2 anyway as move is returning OK
creep.move(RIGHT) // possible -> 0.2 cost
// More code something happens
creep.move(DOWN) // possible -> 0.2 cost again

Right? or did I misunderstood something?

The result of this code is 0.6 CPU used. if you get OK back from the API you will have consumed the CPU.

EDIT:
I'm wrong. Looked at the code and it's only 0.2: https://github.com/screeps/driver/blob/master/lib/runtime/runtime.js#L148

Reply to How is constant CPU cost applied? on Thu, 01 Feb 2018 12:00:18 GMT

MrFaul — Thu, 01 Feb 2018 12:00:18 GMT

Maybe this should somewhere into the CPU limit doc...
Apparently even veterans are slightly confused