Controllers decay ridiculously slow, I understand if you lose a room because you're AI got outsmarted, or overpowered that you want some comeback potential to getting the room back.

But, I took a room when it was RCL5 on 7/7, it's now 7/13. 

The played quit when I took his room, he has a 2nd room but there has been no attempt to take it back, and no progress in that room.

Yet, I still have to wait a week+ for it to die.

I could understand initially it taking as long as it does to decay but I think one or a combination of the following should be implemented:

1. Make it so you can attack enemy controller with less than 5 CLAIM body parts, that way people pre-RCL 7 can clear out enemy rooms and not wait two decades for it to just passively decay.
2. Make decay rate ramp up. Initially to prevent a controller from going neutral over night or two, make it start high (like it is right now 50,000). Then each successful uninterrupted downgrade should remove the next amount of ticks required. I.E. 50,000 ticks for RCL 6 -> RCL 5, then 40,000 ticks for RCL 5 -> RCL 4, with a minimum being like 28,000 (about 24 hours). Numbers are just an example, but some sort of system that ramps up the speed of how fast controllers decay.
3. Reduce the amount of ticks it takes to decay if no spawn is present for a certain amount of time. That way if they have been obliterated from the room, then it wont take as long for it to decay.
4. Or just reduce the overall time it takes for controllers to decay at every level, Right now we have to wait approximately 42hours per level. Assuming one tick is approximately 3 seconds, as I have observed. Meaning even if they only had RCL 4, you'd still have to wait 5.2 days before it decays. Which if you are a new player or a freshly spawned player trying to expand, it really dampens your expansion, to have new players spawn in, then before you can attack them due to newbie spawn they already have RCL3/4+ and defenses.

Hope I typed these thoroughly enough to understand what I am getting at.

It's a big frustration to me, and other players I have talked to...

@Dissi, documentation needs to be way updated than, and turrets need to be nerfed...

@Dissi, So you're saying its 600 dmg a tick at 19 or < range?

Towers are doing more than 150 dmg per shot at > 10 range.

I am getting an error:
main:20
if (creep.memory.role == "miner") {
^TypeError: Cannot read property 'role' of undefined
at main:20:25

I recently expanded to a new room and I am trying to adapt my code to work with two rooms.
However, I am running into issues.
THis is my code in main:

for (var spawnName in Game.spawns) {
    var spawn = Game.spawns[spawnName];
    cm.checkForNewSpawn(spawn);
    var creeps = _(Game.creeps).filter({
        memory: {
            room: spawn.room.name
        }
});
for (var name in creeps) {
    console.log("name " + name);
    var creep = Game.creeps[name];
    if (creep === undefined) {
        continue;
    }
    console.log(creep.name);
    if (creep.memory.role == "miner") {
        cm.harvest(creep, spawn);
    } else if (creep.memory.role == "builder") {
        cm.build(creep, spawn);
    } else if (creep.memory.role == "runner") {
        cm.transfer(creep, spawn);
    } else if (creep.memory.role == "struct") {
        cm.repair(creep, spawn);
    } else {
        creep.moveTo(creep.room.controller);
        creep.claimController(creep.room.controller);
    }

When I create a creep I set in its memory 'room' to equal the room's name that the spawnpoint which created the creep is in.

That way I can keep track of my creeps by the room.

So, I get the list of all creeps (Game.creeps), and filter it (with lodash) by 'memory: { room: "roomname" } So, it should return only the creeps within the room of the current spawn.

However, when i then assign the creep to a variable and try to use it. I get all sorts of errors.

Like, when I try to print the name of the creep I got all sort of weird messages instead like "___constructor___"

Any idea what I am doing wrong?