@systemparadox Fuck my life I just coded my rooms so that they can only spawn 1 creep each tick to avoid duplicity on their names (name + Game.time), but just found a new issue. On each room's memory i have entries such as "desiredUpgraders = 1". Then, on another module, i count creeps that belong to that room like that... totalUpgraders = 0; for (let i in Game.creeps){ let thisCreep = Game.creeps[i]; if(thisCreep.memory.role == 'upgrader'){ totalUpgraders ++; } //And so on... } //And then... if(totalUpgraders < desiredUpgraders){ SpawnCreep('upgrader'); } That was working perfectly so far, because there was only one spawn per room, but now that i have a room with controller level 7 and i have 2 spawns it will begin spawning that desired upgrader. Then, room.memory.isSpawning will be set to true for one tick to avoid duplicity on names, but the very next tick it will start spawning another upgrader on the other available spawn because the one being created doesn't exist yet so totalUpgraders < desiredUpgraders still returns true. I've been thinking on how to face this situation for a while, but can't see how at this moment. How do u solve this?

lol, that must have frustrated a whole lot of people xD

Works like a charm! Thank you guys!

@systemparadox Can't say if both transferred energy or only one, didn't realize tbh. But i'm sure there were 2 animations, so i guess one of them transferred only a tiny amount of energy and that's the reason of the cooldown. I didn't think of it until you and @JBYoshi said what you said and it just looked like an unfair bug to me.

I think I've found the cause of the confusion. In Room.findPath (https://github.com/screeps/engine/blob/master/src/game/rooms.js#L281), there is the following: var ret = globals.PathFinder.search(fromPos, {range: Math.max(1,opts.range || 0), pos: toPos}, searchOpts); for(let i=0; i<ret.path.length; i++) { let pos = ret.path[i]; if(pos.roomName != id) { break; } //... } This break statement is why Room.findPath only returns paths up to the room exit (in this case id is equivalent to this.name). The documentation for RoomPosition.findPathTo states: If the target is in another room, then the corresponding exit will be used as a target So this is expected for RoomPosition.findPathTo, but no such statement exists for Room.findPath, so the behaviour I am seeing is totally unexpected. It's even more confusing when you consider that the documentation for Room.findPath refers to options such as maxRooms. So the game does use the new pathfinder by default, but the results from Room.findPath are totally confusing. It uses the new pathfinder to find a path all the way to the target but only returns the part of the path inside the current room and discards the rest.

@flyasd1 Right, but he suggested using it to recognize choke points or open areas. That would mean the terrain is not relevant, only the number of tiles away from the walls: Using walls as seed points, it can be useful to identify choke points and areas with the most open space, etc.

So they do decay from use and just over time, I didn't realize that. I would still think we could make the tip more accurate. Roads and Tunnels decay from use and over time, so don't forget to repair them.