Is this really the best solution you could come up with to the problem?
Logically this is going to be bad to wire up. And for those of us generating a pixel it means once every 17 - 50 ticks we're going to skip the entire tick and nothing in our entire codebase gets to act?
I understand needing to slow down pixel generation. But this is a terrible solution.
The engine code actually very rarely to never calls the structure isActive method, it's hard coded to check against controller and does a very, very expensive partition operation every time it's callled. It's also however not easy to fix, as the ideal would be to calculate and cache this information whenever RCL changed or a structure was placed/destroyed.
If possible, it would be helpful if the console was available while in map view as well
Thanks! I can confirm it does work now!
The engine code suggests it should but I think this line is what's preventing it from working:
var extensions = _.filter(roomObjects, i => i.type == 'extension' && i.user == target.user && !i.off);
at https://github.com/screeps/engine/blob/master/src/processor/intents/power-creeps/usePower.js#L112
I think it's caused by the i.user == target.user portion, and containers not being owned.
Probably related to the recent downtime, but at time of writing I've got several rooms on shard0 not ticking properly. Containers with negative decay, creeps with no ticksToLive, invaders not moving, downgrade timers running but not accepting upgrade actions (despite displaying the animation).
Facing a situation I could resolve with a single cpu halt, but can't execute anything due to the error.
@o4kapuk That's in shard0 E55S37
Invader cores can also apparently overlap structures
