Diff for "RequestResources" - NEAT Portal Wiki

Diff for "RequestResources"

Differences between revisions 6 and 7

Usage:	requestresources coords resType localAmount remoteAmount minBatch maxBatch troopType
Example:	requestresources any food 100m 1b 50m 100m requestresources HubCity wood 25m 40m 5m * cavalry

RequestResources works just like SendResources, except in reverse.

Requestresources is used to instruct the bot to automatically request certain resources from certain destinations when the conditions specified are met. As an example, you can tell the bot to ask a resource depot city for 10mil wood anytime it falls below 15mil wood, while keeping at least 30mil in the sending city.

Since a picture speaks a thousand words...

Requestresources tends to look more complicated than it is. The things to remember are as follows:

Coordinates to request from can be in either xxx,yyy or city name format including "any". When using a city name, it must be on the same account.
The city to request from, resource type, local amount, and remote amount are required.
The minimum and maximum batch sizes and troop type to use for transporting 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 requesting city above the local amount. You must have BELOW this amount in order to have a request sent. 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 sending city below the remote amount. You must have ABOVE this amount in order to send some to the requesting city. 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.

CategoryAllGoals CategoryResourceGoals

RequestResources (last edited 2017-12-16 18:54:00 by Inanna)

-  ⇤ ← Revision 6 as of 2013-02-07 20:50:25 → 
  Size: 1539
  Editor: Inanna
  Comment:
+   ← Revision 7 as of 2014-08-30 19:55:22 → ⇥
  Size: 3369
  Editor: Inanna
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-||<tablebgcolor="#F9F9F9" tablestyle="margin:1em 1em 1em 0px;border-style:solid;border-color:rgb(170, 170, 170);color:rgb(0, 0, 0);font-family:sans-serif;font-size:13px;line-height:19.5px;text-align:start; " tableclass="wikitable"#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em; ">Usage: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">requestresources coords type local_min remote_min remote_request [trooptype] ||
||<#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em; ">Example: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">requestresources !OtherCity food 100m 1b 50m<<BR>>requestresources 111,222 iron 20m -1 5m cavalry ||
+||<tablebgcolor="#F9F9F9" tablestyle="margin:1em 1em 1em 0px;border-style:solid;border-color:rgb(170, 170, 170);color:rgb(0, 0, 0);font-family:sans-serif;font-size:13px;line-height:19.5px;text-align:start;  " tableclass="wikitable"#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;  ">Usage: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">requestresources coords resType localAmount remoteAmount minBatch maxBatch troopType ||
||<#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;  ">Example: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">requestresources any food 100m 1b 50m 100m<<BR>>requestresources !HubCity wood 25m 40m 5m * cavalry ||
 Line 4:
+!RequestResources works just like SendResources, except in reverse.
-Line 5:
+Line 6:
-'''Coords can be in either xxx,yyy  or city name format including "any" (on same account only)'''
+Requestresources is used to instruct the bot to automatically request certain resources from certain destinations when the conditions specified are met. As an example, you can tell the bot to ask a resource depot city for 10mil wood anytime it falls below 15mil wood, while keeping at least 30mil in the sending city.
-Line 7:
+Line 8:
-Requestresources works just like SendResources, except in reverse.
+Since a picture speaks a thousand words...
-Line 9:
+Line 10:
-In the 1st example above, the bot will request 50 million food from !OtherCity if !ThisCity has under 100 million food and !OtherCity has at least 1 billion food. Since no trooptype is set, the bot will default to sending with transports.
+{{http://i.imgur.com/g3fA4MT.png}}
-Line 11:
+Line 12:
-In the 2nd example above, the bot will request 5 million iron from 111,222 if !ThisCity has under 20 million iron, regardless of how much iron is in 111,222, and it will use cavalry to transport the iron.
+Requestresources tends to look more complicated than it is. The things to remember are as follows:
-Line 13:
+Line 14:
-The use of -1 and -2 parameters are possible with requestresources exactly as detailed above with SendResources.
+ * Coordinates to request from can be in either xxx,yyy or city name format including "any". When using a city name, it must be on the same account.

 * The city to request from, resource type, local amount, and remote amount are required. 

 * The minimum and maximum batch sizes and troop type to use for transporting 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 requesting city above the local amount. You must have BELOW this amount in order to have a request sent. 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 sending city below the remote amount. You must have ABOVE this amount in order to send some to the requesting city. 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.