You can always reset your own memory.  You just create a new branch that only has code in it to wipe the memory, switch to that branch, then switch back.

Yeah, this *totally* wouldn't be abused by players to do processing on their own servers and upload the results back to their creeps, therefore bypassing the CPU limit.

Not at all.

I'm looking at optimising my pathfinding and while getClosestByPath is sometimes needed in some rooms due to complex layout, I'm finding that I'm having to recalculate the path after I've already called this.

The function already has the path data, it could just return it along with the object.

Hi,

All other ingame objects that decay have a .ticksToDecay property that returns an integer saying how many ticks until the object takes hits damage, however containers do not.

Please can this be added?

Hey,

When calling createCreep on a spawn then immediately afterwards calling .spawning it returns null.  From looking at the documentation (http://support.screeps.com/hc/en-us/articles/205990342-StructureSpawn#spawning) there's nothing there that should require a round trip to the server.  Please can we make .spawning immediately return data?

This would be great if it also fixed the issue where multiple calls to .createCreep all return OK when the first one should really return OK and subsequent ones should return ERR_BUSY.

D'oh!

I'd also love to be able to turn off email notifications if I have Screeps open already (either through the site or Steam).