Topics created by RaskVann

Fyi: this does not happen in world.

We have just deployed a patch which is intended to track down this malfunction. We need to know about every single case of when this happens again, so please post it here every time.

Thanks for reporting, fixed.

Was making the wrong assumption. Didn't realize it stopped after having energy elsewhere in the room as long as it exceeded 300. Thanks, I corrected the mistake.

Their lair will begin spawning a new one when they die, whether through decay or combat. Their combat logic seems to be: move to the nearest source, attack the closest creep. They currently don't seem to move at all after reaching their source.

Wish I could edit my previous posts. Thanks for everyone that helped. The issue was due to a bad recalledSpawner reference. Issue is resolved.

Try to debug those findNextRoom calls, it seems to be a problem in the recursion in your code.

My code for each role define parts percent in the body and cost. totalPercent is the max amount of a room energy it will use    parts: {         pieces:[            {typeName:WORK, percent:0.5, cost:100},             {typeName:CARRY, percent:0.25, cost:50},             {typeName:MOVE, percent:0.25, cost:50}        ],        totalPercent:0.67    },   then you just have to go through parts.pieces the amount of each part is percent * energyRoom * totalpercent /cost And then loop pushing each typeName in an array

You do not own walls and roads, so they won't show up under FIND_MY_STRUCTURES. This is intended.

The documentation is fixed, thank you for reporting. You can assign memory in the same tick using the returned name value like this: var flagName = room.createFlag(10, 10, undefined, COLOR_RED); Memory.flags[flagName] = {type: 'attack'}; flag.memory.type will be available in the following tick when the flag is created.