Improvements

Now that I've been running my script for several days, I've had an opportunity to refine some of the behaviors.

1. Ditched the meleeGuard all together. He really wasn't effectual against the invaders.
2. 2 rangedGuards continue to manage the keepers, but when invaders spawn, they jump to the neighboring room to assist. The 4 of them are better able to tackle the invaders. They return when done.
3. If there are more than one invader in range, the rangedGuards use rangedMassAttack. This turns out to be the key for the healers as they can only heal one unit at a time. The healer gets preoccupied healing itself, while you dwindle down the others.
4. If a guard is engaged with a keeper, and invaders spawn, it abandons the keeper.
5. When invaders spawn (in any room) units without attack parts evacuate the room. They return after the all-clear.
6. Some global pathing and caching improvements have shortened travel distances some.

Also, someone on Slack pointed out that damaged parts still generate fatigue. So ignore my comment above about alternating the parts.

The current logarithmic formula for transaction cost really puts the max trade distance at 15 rooms away. Beyond that point, it costs more to send than what you receive. In my opinion, that is too short given the size of the world.

I'd strongly favor doubling that distance to 30 rooms with a minor modification to the `calcTransactionCost` formula:

`Math.ceil( amount * (Math.log(0.05*linearDistanceBetweenRooms + 1) + 0.05) )`

For backwards compatibility, it may be best if `ConstructionSite` had a `structureId` property that later became `Structure.id` upon completion.

@Atavus Thanks!

I think part of my strategy is a result of my host rooms being only RCL7. Your guard body costs 6100 energy each; which I cannot yet afford. I look forward to RCL8. For now I do prefer the lower guard cost (3800) and consider the occasional invader failures cheaper than maintaining a heavier force.

I do find it curious that you stack your parts together. I tend to cascade mine (and use a custom short-hand). Example:

    TMTMTMTMTMRMRMRMRMRMRMRMRMRMRMHMHMHMHMHM

I think the advantage of this is that when taking damage, I don't sacrifice my most valuable parts first or the ability to move.

Update : Invader Squads are Brutal

My above scenario does not hold up as well to invader squads as I'd hoped, particularly when I get three ranged and two healers. So a quick mod:

If no invaders: 2 miners, 1 extractor, 4 haulers, 0 meleeGuard, 2 rangedGuards
If invaders: 0 miners, 0 extractors, 0 haulers, 2 meleeGuard, 3 rangedGuards 

Related: Invader squads appear more intense lately. I'm working on some more intelligent evacuation orders for reserved rooms to reduce loses.

I'm interested in soliciting high level strategies for cracking keeper lair rooms.

I recently used my 3-day weekend to prepare what seems to be reliable code for cracking and harvesting from keeper lair rooms. My strategy adds 10 creeps per room to my population, and a 2-3 cpu tick average. I'm netting more energy than I spend; plus minerals. So I'm happy.

However, I'm sure there is room for improvement; so I'm curious to hear what other people's strategies are. I'm holding 2 rooms in perpetuity. If I could somehow get the efficiency up, I could probably hold 2 more. (GCL 4: Own 4 rooms, reserve 8 more, plus 2 keeper lairs. Avg 45/60 cpu, 130 population)

Also, I hope this helps someone. It took some trial and error to figure out how to crack these rooms.

2 x Miners : 8 work, 8 move (1000 Energy)

Upon entering room, locate source with lair with largest ticksToSpawn count. Link to lair. Move to node. Harvest and drop. On node empty or lair ticksToSpawn less than 20, move on to next source.

Strengths: Works well as the miners perpetually avoid the keepers and never get attacked. 

Weaknesses: RunAway check only backs away 5 spaces in opposite direction of hostile. Occasionally, an invader backs a miner into corner.

2 x RangedGuards : 5 Tough, 10 Ranged, 5 Heal, 20 Move (3800 Energy)

Locate nearest hostile. Approach staying 4 spaces away (backs up in opposite direction if pursued), attacks till dead. Heals self if below max

If no hostiles, then move to lair with lowest ticksToSpawn and wait 5 spaces away.

• Strengths: Heals at a rate nearly equal to damage received if creep can avoid melee attack.
• Weakness: Backup behavior is dumb and creep can get stuck on wall or in swamp. If they engage the invaders without a MeleeGuard, they get stuck in deadlock due to healers.

1 x MeleeGuard : 5 Tough, 10 Attack, 5 Heal, 20 Move (3100 Energy)

Locate nearest hostile with no Attack parts, then engage in melee attacks. This guy exists for the periodic invader swarms and favors healers over ranged units.

He waits near the middle of the room till an invader swarm comes and does not assist with keeper control.

• Strengths: If there are only two healer creeps, he'll overpower them. Even with two ranged invaders, he heals faster than damage received.
• Weaknesses: He can't overpower three healers. They heal faster than he can damage. If the RangedGuards step in and help, it's fine. Otherwise, they get stuck in a deadlock till someone runs their ticksToLive.
• Opportunities: This guy is expensive and spends most of his time standing around. I wish I could find a way to predict incoming invaders and spawn on demand.

4 x Hauler : 10 Carry, 10 Move (1000 Energy)

Locate nearest dropped resource that is in a non hostile zone (determined as having no hostiles in 5 square radius). Pick it up till full or gone. Return to homeRoom storage.

Has basic "run away" logic if hostile enters in 5 square radius. Waits near middle of room if there are no 'safe' resources to pick up.

• Strengths: Rarely ever gets attacked, fairly cheap to spawn
• Weakness: I'm leaving a TON of unclaimed energy on the ground.
• Opportunities: I'm boosting with ZO & KH when available in home room; but availability is sporadic. (O & H is coming from my lairs)

1 x Extractor : 3 Carry, 8 Work, 11 Move (1300 Energy)

Locate mineral/extractor and move towards. If keeper near by, wait 5 squares away. Mines till full, or lair.ticksToSpawn < 10, or creep.ticksToLive < 100. Then goes home to dump in terminal (failover to storage).

• Strengths: Rarely gets attacked. Averages 3 full trips (450 mineral) per life span. No mineral waste and cheaper than buying on market.
• Weakness: Most of lifespan is wasted in transit between rooms.

*bump* There appears to be a bug either in the market UI or in `Game.market.calcTransactionCost()`, depending on developers intentions for wrapping behavior.

I'm currently positioned in the far south-east corner of the map. When attempting to deal with a player in the far north-west corner, the market UI echos a distance of 4 rooms. However, `calcTransactionCost` and `deal` are using the non-wrap distances for determining energy transfer cost.

@Artem Thanks for the tip. Including your own lodash works perfectly well with no discernible cpu impact.

I'd like to confirm your findings; as I observed the same.

1. calcTransactionCost does not wrap the map. However, the market UI does.
2. calcTransactionCost uses natural log and not log base 10

The formula found in the calcTransactionCost documentation uses javascript's Math.log routine, which uses the natural log by default.

Coincidentally, if you chart this, you'll find that for a room of distance 15, the energy cost will equal the units transferred. IE, spend 1000 energy to sell 1000 energy 15 rooms away. 

Strictly my opinion, but I feel the energy cost for transfers is rather high.  I'm sitting on a resource surplus, but am unwilling to unload it as all transactions appear to be a significant net negative.