@artch So spawnCreep will still use globals.Memory even when you don't specify a memory?

Seems to work normally again

I created a pull request with the documentation changes: https://github.com/screeps/docs/pull/54

Trying to log in to screeps via github prompts me to authorize the "Screeps Public Test Realm" github app, since the shard go-live

I'd hope a mention of the safe mode would find its way into the error code list in these methods

If I have a creep that is trying to withdraw from a container with code like:

if (creep.withdraw(container, RESOURCE_ENERGY) === ERR_NOT_IN_RANGE) {
  creep.moveTo(container);
}

and the creep is in an enemy room with safe mode activated, the withdraw call will fail with ERR_NOT_OWNER, even though the container itself is in a different room that doesn't have safe mode on, and doesn't have a hostile rampart over it.

The call should not fail in this case.

The documentation for withdraw lacks mentions of the effect of safe mode too.

Those functions expect an array of either RoomPosition or RoomObject objects as an argument, you are passing in a string ("W26S21").

Instead of using describeExits and passing that to findClosestByPath, you could try using [Room.find](http://support.screeps.com/hc/en-us/articles/203079011-Room#find) with the FIND_EXIT_TOP, FIND_EXIT_BOTTOM etc as the first parameter which should give you all the exit tiles in that particular direction, and then passing the result of the find to findClosestByPath.