Usage: |
sendresources coords resType localAmount remoteAmount minBatch maxBatch troopType |
Example: |
sendresources any food 1b 100m 50m 100m |
Sendresources is used to instruct the bot to automatically transport certain resources to certain destinations when the conditions specified are met. As an example, you can tell the bot to send 10mil wood to any of your cities that fall below 5mil wood, while keeping at least 10mil in the sending city.
Since a picture speaks a thousand words...
Sendresources tends to look more complicated than it is. The things to remember are as follows:
Coordinates to send to can be in either xxx,yyy or city name format including "any". When using a city name, the destination must be on the same account. You can send to multiple cities by seperating the coordinates or names with a |. For example sendresources WarCity|HubCity|FarmCity food 10m 20m 1m 1m s. You cannot exclude a specific city using !cityname.
- The destination, resource type, local amount, and remote amount are required.
- The minimum and maximum batch sizes and troop type to use for sending are optional. If only specifying one number for the batch size, then it's considered to be the maximum amount NOT the minimum amount. If you do not specify either a maximum or minimum batch amount, then it will send as much or as little as it is able to send in order to keep the local and remote amounts correct.
- You may use a * in place of numbers for the local or remote amounts or the minimum or maximum batch sizes, to indicate that the amounts don't matter.
- The bot will not put the sending city below the local amount. You must have OVER this amount in order to send some. The exception is in case you use a * for the local amount, then it will send regardless of the local amount.
- The bot will not put the receiving city above the remote amount. It must have BELOW this amount in order to send some. The exception is in case you use a * for the remote amount, then it will send regardless of the remote amount.
- If you specify a minimum batch and that amount would put the sending city below it's localAmount, or the receiving city above it's remoteAmount, then it will not send yet. It will wait until the batch size is ok to send. If you use a * for the minimum batch then the bot will send any amount it decides to.
- If the receiving city is critically low on something (the bot considers 50% or less of the remoteAmount to be critically low) then it will ignore the minimumBatch and send less to get resources there faster.
- The bot takes into account resources that will be arriving before the transport could when calculating how much is needed at the receiving city.
- By default the bot will only allow 1 mission per destination at a time in the rally. This means if this city is sending to or returning from city A then another send to city A will not happen until the existing one lands and returns. You can override this using the /slots switch. For example:
sendresources /slots=3 any food 1b 100m 50m 100m sendresources any food 1b 100m 50m 100m /slots:2