Diff for "RequestTroops" - NEAT Portal Wiki

Diff for "RequestTroops"

Differences between revisions 5 and 7 (spanning 2 versions)

Usage:	requesttroops coords troopType localAmount remoteAmount minBatch maxBatch
Example:	requesttroops any archer 200k 300k 10k 100k requesttroops WarCity scout 1m 10m 50k 100k

RequestTroops works just like SendTroops, except in reverse.

Requesttroops is used to instruct the bot to automatically request certain troops from certain destinations when the conditions specified are met. As an example, you can instruct a city that's trebbing for hero levels to request scouts automatically from your warcity, to maintain a level of scouts that allow continued attacks, without dropping your warcity too low on scouts.

Since a picture speaks a thousand words...

Requesttroops 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". In order to request troops, the coordinates/name must be on the same account. You can request from multiple cities by seperating the coordinates or names with a |. For example requesttroops WarCity|HubCity|FarmCity scout 1m 1m 10k 100k. You cannot exclude a specific city using !cityname.
The city to request from, 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 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. It 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 troops there faster.
The bot takes into account troops that will be arriving before the reinforcement could when calculating how much is needed at the receiving city.

CategoryAllGoals CategoryTroopGoals

RequestTroops (last edited 2014-12-15 20:33:31 by Inanna)

-  ⇤ ← Revision 5 as of 2013-07-15 17:42:01 → 
  Size: 3048
  Editor: Inanna
  Comment:
+   ← Revision 7 as of 2014-12-15 20:33:31 → ⇥
  Size: 3596
  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;">requesttroops coord type local_min remote_min remote_request ||
||<#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;">requesttroops !OtherCity archer 200k 300k 10k<<BR>>requesttroops 111,222 archer 200k -1 10k<<BR>>requesttroops any archer 200k 300k -1<<BR>>requesttroops !OtherCity archer -1 300k 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;">requesttroops 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;">requesttroops any archer 200k 300k 10k 100k<<BR>>requesttroops !WarCity scout 1m 10m 50k 100k ||
 Line 4:
+!RequestTroops works just like SendTroops, except in reverse.
-Line 5:
+Line 6:
-'''coord can be in either xxx,yyy  or city name format including "any" '''
+Requesttroops is used to instruct the bot to automatically request certain troops from certain destinations when the conditions specified are met. As an example, you can instruct a city that's trebbing for hero levels to request scouts automatically from your warcity, to maintain a level of scouts that allow continued attacks, without dropping your warcity too low on scouts.
-Line 7:
+Line 8:
-'''note using city name is valid within the same account'''
+Since a picture speaks a thousand words...
-Line 9:
+Line 10:
-This goal will tell the bot to automatically request troops from another city to this one when it reaches an amount under what you specify and if the other city has an amount over what you specify. This goal can be useful to constantly restock a warcity or city that farms npc10s from remote feeder/builder cities.
+{{http://i.imgur.com/xGWmLWd.png}}
-Line 11:
+Line 12:
-A city can have as many requesttroop goal lines as desired, with each one containing a different troop type and/or city to request help from. The city to request from 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).
+Requesttroops tends to look more complicated than it is. The things to remember are as follows:
-Line 13:
+Line 14:
-As with the sendresources and requestresources directives, requesttroops and sendtroops 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.
+ * Coordinates to request from can be in either xxx,yyy or city name format including "any". In order to request troops, the coordinates/name must be on the same account.  You can request from multiple cities by seperating the coordinates or names with a |. For example ''requesttroops !WarCity|!HubCity|!FarmCity scout 1m 1m 10k 100k''. You cannot exclude a specific city using !cityname.
-Line 15:
+Line 16:
-In the 1st example above, if !ThisCity falls below 200k archers, and !OtherCity has more than 300k archers, then !ThisCity will request !OtherCity send archers to it in 10k increments. Note that !OtherCity would need 310k archers before 10k would be sent away, to prevent it falling below 300k itself.
+ * The city to request from, troop type, local amount, and remote amount are required.
-Line 17:
+Line 18:
-In the 2nd example above, if !ThisCity falls below 200k archers, then request 10k archers from 111,222, regardless of how many archers 111,222 has. With this line, the bot will keep requesting archers, 10k at a time, until !ThisCity has at least 200k or 111,222 runs out of archers.
+ * 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:
+Line 20:
-In the 3rd example above, if !ThisCity falls below 200k archers, and any other city has more than 300k archers, then it will request as many archers at once as it takes to achieve 200k archers in !ThisCity, without putting the other city below 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:
+Line 22:
-In the 4th example above, the bot will request 10k archers at a time be sent from !OtherCity to !ThisCity, regardless of how many archers are in !ThisCity and as long as !OtherCity doesn't fall below 300k archers.
+ * 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. It 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 troops there faster.

 * The bot takes into account troops that will be arriving before the reinforcement could when calculating how much is needed at the receiving city.