This section of goals includes any goals that affect your entire account as well as a few misc. goals that do not fit into another specific category.
Abandon
Abandon Goal
Usage: |
config abandon:[switch] |
Example: |
config abandon:1 |
Default: |
config abandon:0 |
Switch: |
0 = off |
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!
Be sure to move out All heroes as well
Abandon Script
Usage: |
abandon XXX,YYY |
Example: |
abandon 111,222 |
This script tells the bot to abandon the valley at 111,222.
Obsolete
Contents
All of the following goals still function within the bot. They have been replaced by a more powerful or functional goal however. If you are updating your goals, or writing them from scratch, you should not use these. They may be removed from the bot at a future date.
BallsUsed
Usage: |
ballsused npc1s,npc2s,npc3s,npc4s,npc5s |
Example: |
ballsused 25,50,170,250,500 |
This directive is being phased out in lieu of the more powerful NpcTroops goal.
NoAbandonFlats
Usage: |
noabandonflats flat1 flat2 [...] flatX |
Example: |
noabandonflats 111,222 111,333 111,444 |
This directive is now obsolete. Please use ExcludeList instead.
Npc10Heroes
Usage: |
npc10heroes hero-string |
Example: |
npc10heroes hero-string |
This directive tells the bot which heroes may be used to farm level 10 npcs. It is being phased out in lieu of the more powerful NpcHeroes goal.
See HeroString for details on how to set up the hero string for this goal.
Npc10List
Usage: |
npc10list npc1 npc2 npc3 npc4 |
Example: |
npc10list 111,222 111,333 111,444 |
This directive is being phased out in lieu of the more powerful NpcLimits goal.
Npc10Troops
Usage: |
npc10troops troops_to_send |
Example: |
npc10troops a:90000,wo:2000,w:2000,s:4000,t:2000 |
This directive is being phased out in lieu of the more powerful NpcTroops goal.
Npc10Limit
Usage: |
npc10limit troops_to_have |
Example: |
npc10limit a:390000,s:50000 |
This directive is being phased out in lieu of the more powerful NpcLimits goal.
Npc10ExcludeList
Usage: |
npc10excludelist npc1 npc2 npc3 npc4 |
Example: |
npc10excludelist 111,222 111,333 111,444 |
This directive is being phased out in lieu of the more powerful ExcludeList goal.
NpcExcludeList
Usage: |
npcexcludelist npc1 npc2 npc3 npc4 |
Example: |
npcexcludelist 111,222 111,333 111,444 |
This directive is being phased out in lieu of the more powerful ExcludeList goal.
Research
Usage: |
research type:level[type:level,type:level] |
Example: |
research lo:5 |
Techs: |
agriculture - ag |
As with troop and build goals, the bot will perform research goals line by line in sequential order. In the 1st example above, the bot will research logistics to level 5. In the 2nd example above, the bot will research logistics to level 5, horseback riding to level 5, and compass to level 4.
The bot will automatically build and upgrade any buildings necessary to complete research goals.
By default the bot sets config research:1 internally if you have any research goal lines present. If you wish to disable all researching for a city temporarily, instead of adding a // or # to each research line, you can simply add config research:0 to goals.
WARNING!!!
If you specify research goals that require a level 10 building, the bot WILL use your Michelangelo scripts to upgrade buildings to level 10 first!
Be sure to only specify upgrades to level 10 research for military science, metal casting, horseback riding, lumbering, mining, privateering, and masonry in an unconverted npc10, or in cities with those buildings already at level 10 (e.g., a city with a level 10 warehouse for stockpiling 10) unless you're willing to spend your scripts.
As of the 3096 public release, you are able to use conditions in goals. Conditions are checks to see if certain buildings or research targets are met first, and if so then to perform some research task. For example, if I wanted to research privateering only if the academy was already level 10:
research ?a:10?pr:10
Looks confusing, but I promise it's not. The stuff inside the ??s is the condition. So we're checking above "if the academy is level 10, then research privateering to level 10".
You're able to mix in both research and building conditions in the goal, like so:
build ?met:10,w:10?q:0:0,ws:0:0
The above says if metal casting is level 10 and walls are level 10 then demolish all quarries and the workshop. Of course, this is a build goal and not a research goal, but I couldn't really think of a practical application to show you a research goal using both =)
Now, just to throw in a bit of confusion for you... the ?condition?goal can be written in reverse too as goal?condition?. The following both mean the same thing:
research ?ho:10?st:0:0 research st:0:0?ho:10?
The above two lines both say "if horseback riding is level 10, demolish the stable completely".
It is important to note when using conditions in research or build goals, you must use "st" for stable and "sp" for stockpiling. You may still use "st" for stockpiling in pure research goals without conditions.
If you would like even more precise control over research order along with building order, check out the Plan goal.
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 first example above, the bot would run from 6AM to 12 noon, and stop the rest of the time.
In the second example above, the bot would run from 6AM to 12 noon, stop, then run again from 5PM to 11PM.