How about we can also convert a pixel back to 2500 bucket? (Probably with a cooldown of 100 ticks?)

It only regenerates little mineral, and does not work when mineral is depleted. Therefore it is almost useless at the moment. If we can make it also decrease ticksToRegenerate by 5/10/15/20/25 ticks (maybe more?) every 10 ticks when mineral is depleted, this power can actually be a valid choice.

It does more damage than attack. Dismantle is 50 damage per body part per tick, and attack is 30 damage per body part per tick.

@atanner I love the idea, since it solves a lot of problems we have at the moment. However, I think this "reservation system" can have problems when different players try to issue conflicting commands, and ownership can be simply flipped when a player issue two commands in a row.

I think the reservation system can be the same as controller reservation, and the warp container does not decay when it is reserved, since a claim creep is already necessary to maintain warp containers, and a creep is not necessary to operate the warp container, making warp containers easier to use.

@u-238 said in Discussion: long-range logistics revamp:

@tun9an0 I also thought about creep convoys with energy to help sieged colony. But depedning on the terrain your path will go through attacking squad or not. In first case it is very hard to keep haulers alive, sure there can be healers and attacking creeps or towers can heal them... But what if attacker just have more creeps and will intercept haulers easily

The purpose of blockading a room is to prevent resource from going in. Otherwise while the attacker is spending a lot of resource attacking, the defender can just spam repairers. I think a good way to help the sieged room is to send a relief squad from another room with some energy/battery.

However, currently this way is not quite efficient since creep carry capacity is too low. If we buff carry boosts to the level of harvest boosts, we will have an interesting way to help out a sieged room.

Might be a bit different from what is originally proposed, but I think a warp container can be like this:

• Limited to 1 per room.
• Each provides 500 capacity.
• If two warp containers are in rooms next to each other, they are in the same part of network. Their capacity adds up, and they share content. Total capacity cannot exceed for example 4000. This allows creation of huge network if you can defend. If previously disconnected networks are now connected, the content is added and merged in the new network. If previously connected network is broken up, content is divided evenly into subnetworks.
• Cooldown between withdrawing is fixed to 10 seconds, just like the send cooldown for terminals.

All numbers / functions are suggestions and can be changed.

This container will not replace containers or links at all, and throughput is much lower than terminal because of its limited capacity and cooldown when withdrawing, but helps for remotes and when terminals are blocked.

You can let him setup a buy order of 1 piece of energy for 100k credits.

You can already automate this with HTTP requests if you have a script running on your own machine.

The endpoint is: [POST] https://screeps.com/api/game/create-invader.

Parameter is:

{
   room: ROOM_NAME, 
   shard: SHARD_NAME, 
   size: "small" | "big", 
   type: "Melee" | "Ranged" | "Healer",
   boosted?: true
}

We write code. It is not hard to read page source to find out the link to the post and open it.

You can write a script that subscribes to your console websocket stream to log everything.

https://github.com/screepers/python-screeps Here is the link to the python api.