m (Added a reference from DistancePolicy to SafeValleyFarm.) |
m (→Schedulepolicy: used 24 hour clock for 5 pm start) |
||
| Line 45: | Line 45: | ||
<font size="2" face="courier" color="#0000FF">schedulepolicy </font><font size="2" face="courier" color="#A43900">06:00 12:00</font> | <font size="2" face="courier" color="#0000FF">schedulepolicy </font><font size="2" face="courier" color="#A43900">06:00 12:00</font> | ||
|} | |} | ||
| − | This policy will tell the bot to start and stop performing actions during certain times of the day. In the example above, the bot would run from 6 to 12, and stop the rest of the time. You can add multiple start and end times to this policy, eg: schedulepolicy 06:00 12:00 | + | This policy will tell the bot to start and stop performing actions during certain times of the day. In the example above, the bot would run from 6 to 12, and stop the rest of the time. You can add multiple start and end times to this policy, eg: schedulepolicy 06:00 12:00 17:00 23:00. |
<br> | <br> | ||
Revision as of 03:44, 15 July 2012
Contents
Main City Goals
The bot will recognize your oldest city as your main city. The one with an asterix (*) by the name is the main city. There are a few config settings that are only placed in the main city.
Maintenance
| Usage: | config maintenance:[minutes] |
|---|---|
| Example: |
config maintenance:36 |
This tells the bot, in minutes, how long to wait until it tries to reconnect after a server maintenance shutdown.
ResetFarmingHistoryOnStartup
| Usage: | config resetfarminghistoryonstartup:[switch] |
|---|---|
| Example: |
config resetfarminghistoryonstartup:1 |
This goal will tell the bot to reset it's farming history, and begin again anew, each time you restart the bot. By default the bot will remember where it left off in the farming cycle when it's restarted.
Schedulepolicy
| Usage: | schedulepolicy start_time end_time [start_time end_time start_time end_time] |
|---|---|
| Example: |
schedulepolicy 06:00 12:00 |
This policy will tell the bot to start and stop performing actions during certain times of the day. In the example above, the bot would run from 6 to 12, and stop the rest of the time. You can add multiple start and end times to this policy, eg: schedulepolicy 06:00 12:00 17:00 23:00.
Every City Goals
ProcessingPolicy
| Usage: | processignpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy-list |
|---|---|
| Example: |
processingpolicy t b r a n |
| Arguments: |
q = resque |
This policy will allow you to instruct the bot the order in which it will perform it's functions. In the first example above, the bot will send troops if/as goals specify, then build npcs, then transport resources, then capture valleys for production, then npc farm... all of it before any other normal processing is done. In the second example above, the bot will first build npcs, then capture valleys for production, then npc farm... all before any other normal processing is done. In the third example above, the bot will put medal farming as the first priority before others, during the hour between 1PM to 2PM. The use of ! is also allowed to deny a certain process from happening, eg: processingpolicy /start:13:00:00 /end:13:59:59 !medalhunting to disallow medal farming between 1PM and 2PM.
Comfort
| Usage: | config comfort:[switch] |
|---|---|
| Example: |
config comfort:1 |
Enable the comfort goal and Y.A.E.B. will automagiclly perform comforting on your city as it is required. This goal along with config gate:[time], config hiding:[time], config npc:[level] all working together can make it so your cities are virtually impossible to capture. With comforting activated Y.A.E.B. will raise loyalty, reduce grievance, adjust tax rates to prevent riots, and perform misc. comforting actions as specified in compfortpolicy. This goal is required in order to use comfortpolicy.
Comfortpolicy
| Usage: | comfortpolicy min_time max_time [options] |
|---|---|
| Example: |
comfortpolicy 15 20 popraise pray |
| Arguements: |
gold, go |
This policy will tell the bot to, in the example above, perform population raising if needed every 15-20 minutes, and if not needed then pray every 15-20 minutes. You may include any levying or comforting option in this, eg: comfortpolicy 15 20 popraise food pray, to have the bot perform population raising if needed every 15-20 minutes, and if not then levy food every 15-20 minutes and follow with a prayer every 15-20 minutes.
Multiple types of resources can be listed for levying, it will cycle through them each time.
Distancepolicy
| Usage: | distancepolicy npc_farming npc_building medal_farming valley_capturing map_scanning |
|---|---|
| Example: |
distancepolicy 10 20 5 25 25 |
This policy will tell the bot how far, in miles, it may go from your city to perform these actions in order. This number must be a whole number between 5 and 50.
The valley capturing distance also specifies how far the bot may go to farm valleys safely.
Rallypolicy
| Usage: | rallypolicy policytype:[level:]:maximumslots [policytype:[level:]:maximumslots] |
|---|---|
| Example: |
rallypolicy n:10:1 n:8 v:1 |
| Arguments: |
n = npc farming |
This policy will allow you to instruct the bot how many of each mission can be done at the rally. This does not reserve rally spots for these tasks, it merely limits how many it can do at one time. Rallypolicy counts both returning and marching missions in it's total.
You could, for example, do rallypolicy n:10:1 n:6 v:5 b:2, which would instruct your bot that it may use up to 1 slot for npc10s, 6 slots total for npcs (which would count the npc10 as one of them), 5 slots for valley farming/medal hunting, and 2 slots for npc building. You won't need a lvl 13 rally spot for this to work. Whichever task is performed first can use UP TO that many slots, then the next task will use UP TO it's limit or the rally spot limit, so on and so forth until your rally spots are all in use, the rallypolicy limit is reached for every task, or your tasks are all in progress.
Taxpolicy
| Usage: | taxpolicy min_rate max_rate |
|---|---|
| Example: |
taxpolicy 20 100 |
This policy will tell the bot the range of tax you want set. The example above would maintain a minimum 20% tax rate and 100% maximum rate. If the bot detects that additional gold is necessary to prevent a revolt, it will increase the tax rate as necessary, up to "max_rate". The default values are 0 (min) and 100 (max). A default of 0 (min) allows the bot to maintain maximum population. Players with established accounts will probably wish to use the defaults.
Extrafood
| Usage: | config extrafood:[days] |
|---|---|
| Example: |
config extrafood:5 |
By default the bot will attempt to keep 1 day worth of food for each city, but you can change this amount with this goal. The bot will not queue troops, queue wall fortifications, or sell food if it would bring it below this number of days. Less than 1 day is also possible, eg: config extrafood:0.5.
This goal is removed in rev1847 and later.
Nohealing
| Usage: | config nohealing:[switch] |
|---|---|
| Example: |
config nohealing:1 |
When this goal is turned on, it will tell your bot that you do not want it to heal injured troops in the medic camp.
ReportsToKeep
| Usage: | reportstokeep items(0|1) valley.HighLoss npc5.HighLoss npc10.LowLoss npc10.HighLoss |
|---|---|
| Example: |
reportstokeep 1 a:500 b:1 a:3800 a:6000 |
This directive will tell the bot which reports you want it to keep. In the above example, any report with a treasure acquired will be kept because the first number is set to "1". Any valley attack report will be kept if the archers lost in it are 500 or more. Any npc5 attack report will be kept if 1 or more ballista are lost. Any npc10 report will be kept if the archers lost are lower than 3.8k or higher than 6k. All other reports will be read and deleted by the bot. You can set these numbers to 0 in order to have it keep every report, eg: reportstokeep 1 a:0 b:0 a:0 a:0.
Excludelist
| Usage: | excludelist coord1 coord2 [...] coordX |
|---|---|
| Example: |
excludelist 111,222 111,333 111,444 |
This directive will tell the bot to exclude anything at those coordinates. No npc farming runs, valley acquisition runs, valley farming runs, npc building missions, or flat acquisition runs will be sent to these coordinates. This single goal can (and in the future will completely) replace noabandonflats, npcexcludelist, and npc10excludelist.
NoAbandonFlats
| Usage: | noabandonflats flat1 flat2 [...] flatX |
|---|---|
| Example: |
noabandonflats 111,222 111,333 111,444 |
This directive is now obsolete. Please use excludelist instead.
Abandon
| Usage: | config abandon:[switch] |
|---|---|
| Example: |
config abandon:1 |
This goal tells the bot that you are planning to abandon this city. The bot will destroy all troops, wall defenses, and queues in the city and will lower loyalty by levying and adjusting the tax rate upwards. The bot will not perform comforting actions on the city with this goal set. This is useful when you plan to give a city away or abandon it. The bot will not automatically abandon the city once it reaches 0 loyalty.
WARNING!!! You should run evacuatetown in the scripts window before you set this goal!