Topics created by keenathar

@keenathar Thanks, we'll take a look

However I'm still curious how it makes a difference, just for my own understanding. To understand this, you should output your targetRoom. Basically you're changing the value of creep.room.name in your code to the value of targetRoom so it doesn't match the real state of the world anymore. Most of our API code is not intended to work with objects modified like this which cause weird exceptions or unexpected behavior here and there which are extremely hard to debug. This specific case was because you changed creep.room.name to the name of a room that you don't have a vision to. This broke one of the checks in Creep.claimController.

It is possible to have an 11x11 with all extensions fillable from the inside. Part of the way I achieved that in my newer rooms was by putting the observer/nuker/power spawn in the place of otherwise unreachable extensions. e.g. in your diagram at (4,1) and (1,4). On the basis you don't often have to refill the nuker/power spawn, I don't see it as a big deal that you have to go into the outer ring for those. One thing you've done well in this diagram that other people don't always do (and not to do this seems to me like a mistake) is to have all your paths as diagonals. That uses the in-base empty space most efficiently.

Yes, the same would happen when a tunnel disappears when some creep is staying there, it may find itself in a blocked location, and its tombstone will also be inaccessible. It feels consistent and intended behavior.

It's already planned. See Dev updates thread: Re-designing many game interfaces ... for example, it's planned to add a list of community driven private servers to the login page of steam client.