• My Pages
  • Comments
  • Add Link
  • Subscribe
  • Subscribe User
  • Edit (GUI)
  • Edit (Text)
  • Rename Page
  • Copy Page
  • Load Page
  • Save Page
  • Delete Page
  • Attachments
  • Check Spelling
  • Diffs
  • Info
  • Revert to this revision
  • XML
  • Render as Docbook
  • Print View
  • Raw Text
  • Delete Cache
  • Like Pages
  • Local Site Map
  • Remove Spam
  • Package Pages
  • Sync Pages

    Revision 5 as of 2012-08-21 01:05:19

    Clear message

    How to write your goals

    Goals are the bread and butter of your bot's ability to manage your account. Unlike scripts, goals are "end result" actions to work towards, meaning you tell the bot what you want, and it will work on achieving that as it performs it's tasks. The thing to remember about goals is that they are not performed line by line in order. You can write most goals in any order you like and they will function the same. For example: 

    config comfort:1 
config npc:5 
npcheroes farmer1,farmer2

    The above goals would work the same if you wrote them as: 

    config npc:5
npcheroes farmer1,farmer2
config comfort:1

    Config goals (those with config whatever:[value] formats) can be combined one one line as well: 

    config npc:5,comfort:1
npcheroes farmer2,farmer1

    Notice in the above example, the npcheroes goal was not combined to the line with the config goals. While both types are goals, they will not work on the same line. The different types of goals are: Directives, Policies, and Config. As shown in the above examples, config goals can be joined together with a comma. Directives must be listed one per line, with the parameters after it. For example: 

    npcheroes farmer1,farmer2
herofirelimit 120
excludelist 123,456 234,567

    Policies must also be listed one per line. The formatting you will use for the parameters of a policy depend on the goal itself. For example: 

    tradepolicy /type:food /min:2d /max:20d /allowselltomin
comfortpolicy 15 20 popraise
rallypolicy n:5 v:5

    It is important to notice that in policies with /type:value formats, that you must have a space between each type, as shown above. Typing it as /type:food/min:2d will not work!

    Hero Strings in Goals

    Many places in the bot will allow you to specify heroes. The selection or list of heroes to be used will be referred to as the hero-string in various other places in the wiki.

    You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any' or even use no hero at all with 'none'. For example,

    • valleyheroes Biggy this would allow only hero Biggy to attack valleys & flats

    • npcheroes any,!Smarty,!Biggy this would allow any hero except Smarty and except Biggy to hit npcs

    • npcheroes 10 Biggy,Polly,Smarty this would allow heroes Biggy, Polly, and Smarty to hit npc10s

    • reinforce 123,456 none c:100000 this would allow you to reinforce 123,456 with cav but not to include a hero

    You may also use advanced filters in hero strings in the format of hero:filter. The hero name list (or 'any') must be stated first, followed by the filter(s). Any filters listed will apply to the entire line. For example,

    • valleyheroes any:attack>180 this would allow any hero with an attack over 180 to attack valleys & flats

    • valleyheroes any:politics<200 this would allow any hero with politics under 200 to attack valleys & flats

    • npcheroes 8 any:politics=best this would allow the best politics hero to hit npc8s

    • npcheroes 10 any:attack>300,base>60 this would allow any attack hero with both an attack over 300 AND a base over 60 to hit npc10s

    • attack 111,222 !Biggy,any:attack>180 c:99k,s:1k this would attack coordinates 111,222 with any hero over 180 attack other than hero Biggy with 99k cavs, 1k scouts

    • attack 111,222 !Polly,any:attack<100 w:5k this would attack coordinates 111,222 with any hero under 100 attack other than hero Polly with 5k warriors

    If you wish to apply seperate filters to seperate heroes, use multiple lines. For example,

    • npcheroes 5 any:base>60

    • npcheroes 5 any:attack<300

    The above lines mean that npc5s can be farmed with any hero that has greater than 60 base, OR any hero that has less than 300 attack.

    Multiple lines can be concatenated into a single line with the | symbol. For example,

    • npcheroes 5 any:base>60|any:attack<300

    The above line means exactly the same thing as the 2 before it.

    • npcheroes 5 any:base>60,attack<300

    If you were to instead use the line above, it would mean npc5s can be farmed with any hero that has both greater than 60 base, AND is less than 300 attack.

    All possible filters for use in hero strings are:

    • attack or att
    • politics or pol
    • intel or int
    • loyalty or loy
    • level or lvl
    • experience or exp points or pts
    • base or bse

    All possible comparisons to use in filters are:

    • < (less than)

    • > (greater than)

    • = (equal to)
    • != (not equal to)

    • <> (not equal to)

    • <= (less than or equal to)

    • >= (greater than or equal to)

    "Best" and "Worst" can be used in place of values for comparisons, example:

    • npcheroes 10 any:attack=best would allow npc10s to be farmed with the best attack hero.

    • npcheroes 5 any:attack<best would allow npc5s to be farmed with any hero lower than the best attack hero.

    Stats can be compared to other stats in place of values, example:

    • npcheroes 5 any:attack>politics would allow any hero with an attack score greater than it's politics score.

    • npcheroes 5 any:politics>level would allow any hero with a politics score greater than it's level.

    Wildcards can be used for the hero list. * will represent 1 or more characters, ? will represent 1 character. For example,

    • npcheroes 5 att*:attack>200 would allow npc5s to be farmed with any hero over 200 attack that has att in it's name.

    • npcheroes 5 *:base>60 would allow npc5s to be farmed with any hero that has a base over 60.

    CategoryGoals