(→Troopsusereserved) |
(→Troopdelbadque) |
||
| Line 110: | Line 110: | ||
|} | |} | ||
| − | By default, the bot will always use your [[ | + | By default, the bot will always use your [[Hero_Goals#Traininghero|traininghero]] to queue troops. If you do not have one set, the bot will attempt to use the highest attack hero available in the city. Sometimes you may queue manually, or lag may cause the bot to queue with the wrong hero. In this case, the bot recognizes the queue as 'bad' because it is not an optimal time to completion. With this enabled, the bot will sometimes cancel these bad queues so that it can replace them with good ones using the right hero. Do not enable this if you have instant troops ''hidden'' in the barracks behind deliberately slow builds that you plan to cancel when the instant troops are needed. |
==Reservedbarrack== | ==Reservedbarrack== | ||
Revision as of 00:48, 25 May 2011
Contents
Troop
| Usage: | troop troops_to_queue |
|---|---|
| Example: | troop p:1,sw:1,cav:1 troop a:100000,b:5000,t:5000 warr:15000,wo:5000,p:5000,sw:5000,s:5000,cav:1000,cata:1000,ram:5,cp:5 |
This directive is how you tell the bot what troops to queue for you. The bot reads each line from left to right, top to bottom. The bot will not move on to the 2nd troop line until the 1st line is completed, and if at any point in time a previous line becomes invalid (eg, you get attacked and lose all your pikes) the bot will drop back to the 1st incomplete line to finish that one first.
Using the above examples, the bot will first build 1 pike, 1 sword, and 1 cavalry in that order. Once complete the bot will then build 100k archers, 5k ballista/trans, 15k warriors, 5k workers/pikes/swords/scouts, 1k cav/phracts, and 5 rams/pults. Once that's completed the bot will then build 50k warriors, 15k pikes/swords, 50k scouts, and 200k archers. Once that's completed the bot will then build 250k archers, 100k scouts, 10k cav, and 5k phracts. Finally, the bot will start building 400k archers, 200k scouts, 10k ballista/trans.
If the bot is currently working on building the 4th line of troop goals, and you get attacked and you lose all your cavalry and pike, with the above settings, the bot will stop queuing the 4th line and instead build 1 pike/cav again from the 1st line, then go to the 2nd line and build the 5k pike and 1k cav, then go to the 3rd line and build the 15k pike, then resume where it left off on the 4th line.
| Usage: | /increment: /queuetime: |
|---|---|
| Example: | troop /increment:.1 /queuetime:.5 b:5k,t:5k troop /usereserved:0 /usepopmax:1 a:100k |
Starting with versions later than rev1268, the bot also allows switches to individual troop goal lines that will override the default and configured troop settings. If no switches are specified, the bot will use the configured goals for all troops, or the default settings if both are lacking.
Troopqueuetime
| Usage: | config troopqueuetime:[hours] |
|---|---|
| Example: | config troopqueuetime:2 |
This goal allows you to tell the bot how many hours per individual troop queue you want. It is recommended to adjust this number as your traininghero's attack attribute grows or number of barracks changes, so that the bot can utilize your population and time more efficiently. If this is not set, the bot defaults to 15 minute queue times.
Troopsusereserved
| Usage: | config troopsusereserved:[switch] |
|---|---|
| Example: | config troopsusereserved:1 |
By default, Y.A.E.B. will attempt keep 1 day worth of food in each city, or the number of days specified in config extrafood. The bot will not queue troops if doing so would bring it under this amount of days. You can override this behavior and allow it to continue to queue new troops by enabling this goal.
Enabling this without knowing what you're doing could cause the bot to send your city into refuge!
Troopsusepopmax
| Usage: | config troopsusepopmax:[amount] |
|---|---|
| Example: | config troopsusepopmax:1 config troopsusepopmax:0.5 |
By default, Y.A.E.B. will only use your idle population to queue new troops. You can allow it to use your entire population, by dropping production temporarily, by setting this to '1'. The bot can also use a percentage of your total population by using a number lower than '1', eg: config troopsusepopmax:0.5.
Troopincrement
| Usage: | config troopincrement:[amount] |
|---|---|
| Example: | config troopincrement:.01 config troopincrement:500 |
By default, Y.A.E.B. will queue troops in the other you specify from left to right, on each sequential 'troop' line. By setting this goal, you can tell the bot to instead queue a percentage or specific amount of each troop on the line. For example, if your goals contained:
troop w:100000,s:100000,p:100000,sw:100000,c:100000,t:3500,b:3200,a:300000
The bot will first train 100k warriors, then 100k scouts, and so on without troopincrement set.
If given the line above and using config troopincrement:.01 then the bot will instead queue 1000 warriors (1%) and then queue 1000 scouts (1%), continuing down the line, and then restarting at the beginning of the line to rinse and repeat until the entire line goal has been met.
For the percentage challenged, the bot will also accept whole numbers as the actual amount to queue, eg: config troopincrement:500. In this case the bot will queue 500 warriors then 500 scouts then 500 pike, continuing down the line, and then restarting at the beginning of the line to rinse and repeat until the entire line goal has been met.
Troopdelbadque
| Usage: | config troopdelbadque:[switch] |
|---|---|
| Example: | config troopdelbadque:1 |
By default, the bot will always use your traininghero to queue troops. If you do not have one set, the bot will attempt to use the highest attack hero available in the city. Sometimes you may queue manually, or lag may cause the bot to queue with the wrong hero. In this case, the bot recognizes the queue as 'bad' because it is not an optimal time to completion. With this enabled, the bot will sometimes cancel these bad queues so that it can replace them with good ones using the right hero. Do not enable this if you have instant troops hidden in the barracks behind deliberately slow builds that you plan to cancel when the instant troops are needed.
Reservedbarrack
| Usage: | config reservedbarrack:[switch] |
|---|---|
| Example: | config reservedbarrack:1 |
By enabling this, the bot will reserve 1 barrack in the city free of queues to use to build instant troops when under attack.
Keeptroops
| Usage: | keeptroops city_name troops quantity |
|---|---|
| Example: | keeptroops OtherCity w:100k,s:400k,p:100k,sw:200k,a:400k 10k |
This goal will tell the bot to automatically send troops to another city when it reaches more than the amount you specify. In the example above, when ThisCity has more than 100k warriors, or 400k scouts, or 100k pikes, or 200k swords, or 400k archers then the bot will send extras to OtherCity in increments of at least 10k. When combined with troop goals set higher than these amounts, the bot would continually queue troops to be sent to another city. This can be useful to stock or restock a war city or continually rebuild troops for a npc10 farming city. Only one keeptroops goal per city is possible.
Requesttroops
| Usage: | requesttroops coord type local_min remote_min remote_request |
|---|---|
| Example1: | requesttroops OtherCity archer 200k 300k 10k |
| Example2: | requesttroops OtherCity archer 200k -1 10k |
| Example3: | requesttroops OtherCity archer 200k 300k -1 |
| Example4: | requesttroops OtherCity archer -1 300k 10k |
This goal will tell the bot to automatically request troops be sent 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. As with the sendresources and requestresources directives, requesttroops and sendtroops are also able to use -1 as a value. 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. This can be useful to reinforce a city under attack or restock a city that farms npc10s.
In the 1st example above, if ThisCity falls below 200k archers, and OtherCity has at least 300k archers, then ThisCity will request OtherCity send archers to it in 10k increments.
In the 2nd example above, if ThisCity falls below 200k archers, then request 10k archers from OtherCity, regardless of how many archers OtherCity has. With this line, the bot will keep requesting archers, 10k at a time, until ThisCity has at least 200k or OtherCity runs out of archers.
In the 3rd example above, if ThisCity falls below 200k archers, and OtherCity has at least 300k archers, then it will request as many archers at once as it takes to achieve 200k archers in ThisCity, without putting OtherCity below 300k.
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.
Sendtroops
| Usage: | sendtroops coords trooptype local_min remote_min quantity |
|---|---|
| Example: | sendtroops OtherCity archer 300k 200k 10k |
This goal works exactly like requesttroops only in reverse. As with requesttroops above, a -1 value can be used. 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. This can be useful to stock or restock a war city or continually rebuild troops for a npc10 farming city. In the example above, if ThisCity has at least 300k archers, and OtherCity has below 200k archers, then ThisCity will send OtherCity archers in increments of 10k.