Diff for "SendTroops" - NEAT Portal Wiki

Diff for "SendTroops"

Differences between revisions 5 and 6

Usage:	sendtroops coords troopType localAmount remoteAmount minBatch maxBatch
Example:	sendtroops any ballista 10k 5k 500 5k sendtroops TrebCity scout 100k 2m 50k 100k

Sendtroops is used to instruct the bot to automatically transport certain troops to certain destinations when the conditions specified are met. As an example, you can tell the bot to send scouts from your warcity 50-100k at a time to your city that is trebbing so it doesn't run out of scouts to hit with, without bringing your warcity below a certain amount.

Since a picture speaks a thousand words...

Sendtroops 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 sendtroops WarCity|HubCity|FarmCity scout 1m 1m 10k 100k. You cannot exclude a specific city using !cityname.
The destination, troop type, local amount, and remote amount are required.
The minimum and maximum batch sizes 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 troops there faster.
The bot takes into account troops that will be arriving before the reinforcements could when calculating how many are needed at the receiving city.

CategoryAllGoals CategoryTroopGoals

SendTroops (last edited 2014-09-01 20:41:54 by Inanna)

-  ⇤ ← Revision 5 as of 2013-01-15 22:34:01 → 
  Size: 3396
  Editor: Daniel
  Comment:
+   ← Revision 6 as of 2014-09-01 20:41:54 → ⇥
  Size: 3437
  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;">sendtroops coord trooptype local_min remote_min quantity ||
||<#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;">sendtroops !OtherCity|!AnotherCity archer 300k 200k 10k<<BR>>sendtroops 111,222 archer 300k -1 10k<<BR>>sendtroops !OtherCity archer 300k 200k -1<<BR>>sendtroops !OtherCity archer -1 200k 10k<<BR>>sendtroops 111,222 archer 300k -2 10k ||
+||<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;">sendtroops coords troopType localAmount remoteAmount minBatch maxBatch ||
||<#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;">sendtroops any ballista 10k 5k 500 5k<<BR>>sendtroops !TrebCity scout 100k 2m 50k 100k ||
 Line 5:
-'''coord can be in either xxx,yyy  or city name format including "all" '''
+Sendtroops is used to instruct the bot to automatically transport certain troops to certain destinations when the conditions specified are met. As an example, you can tell the bot to send scouts from your warcity 50-100k at a time to your city that is trebbing so it doesn't run out of scouts to hit with, without bringing your warcity below a certain amount.
 Line 7:
-'''note using city name is valid within the same account'''
+Since a picture speaks a thousand words...
 Line 9:
-This goal will tell the bot to automatically send troops from this city to another one when it reaches an amount over what you specify and if the other city has an amount under what you specify. This goal can be useful to constantly restock another city that farms npc10s, or have several building/feeder cities that build troops for a war city to accumulate.
+{{http://i.imgur.com/YlDcWHt.png}}
 Line 11:
-A city can have as many sendtroop goal lines as desired, with each one containing a different troop type and/or city to send troops to. The city to send to parameter can be written as coordinates (111,222) or the city name if same account (!OtherCity) or to encompass any city (any) or as multiple city names or coordinates separated by the | symbol (City1|City2|City3 or 111,222|111,223|111,224).
+Sendtroops tends to look more complicated than it is. The things to remember are as follows:
 Line 13:
-As with the sendresources and requestresources directives, sendtroops and requesttroops are also able to use -1 as a parameter. The -2 parameter can be used for the remote quantity to force the bot to behave more like the older keeptroop goal (sending quantities of at least the amount specified, but more than it if possible).
+ * 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 ''sendtroops !WarCity|!HubCity|!FarmCity scout 1m 1m 10k 100k''. You cannot exclude a specific city using !cityname.
 Line 15:
-In the 1st example above, if !ThisCity has more than 300k archers, and either !OtherCity or !AnotherCity has below 200k archers, then !ThisCity will send !OtherCity or !AnotherCity archers in increments of 10k. Note that !ThisCity would need to have 310k archers to begin with before sending 10k away, to avoid putting itself below the 300k minimum.
+ * The destination, troop type, local amount, and remote amount are required.
 Line 17:
-In the 2nd example above, if !ThisCity has more than 300k archers, then it will send in increments of 10k to 111,222... regardless of how many archers 111,222 has, as long as !ThisCity doesn't fall below 300k.
+ * The minimum and maximum batch sizes 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.
 Line 19:
-In the 3rd example above, if !ThisCity has more than 300k archers, and !OtherCity has below 200k archers, then !ThisCity will send !OtherCity as many archers as needed to bring !OtherCity up to 200k, while keeping !ThisCity above 300k.
+ * 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.
 Line 21:
-In the 4th example above, if !OtherCity has below 200k archers, then !ThisCity will send it archers in 10k increments until it gets above 200k, regardless of how many archers !ThisCity has.
+ * 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.
 Line 23:
-In the 5th example above, if !ThisCity has more than 300k archers, then it will send all archers over that to 111,222, regardless of how many 111,222 has and how many it sends at a time, as long as the minimum sent is at least 10k archers.
+ * 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 troops there faster.

 * The bot takes into account troops that will be arriving before the reinforcements could when calculating how many are needed at the receiving city.