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 and directives, that you must have a space between each type, as shown above. Typing it as /type:food/min:2d will not work! Whereas with config goals, it is just the opposite. Typing it as config npc: 1 will not work, because of the space after npc:

One exception to the rule in goals about the order they're written not mattering, is if you accidently duplicate goals. Some goals are able to take up multiple lines, for example the troop goal can have as many lines as you want. Most, however, can only exist one time in the goals. If you duplicate one of these, the 1st one will be discarded for 2nd (or for the last, if you repeat it more). For example:

• config npc:5
  npcheroes 5 any,!bigguy
  config npc:10
  npcheroes 10 bigguy

The above is a very common mistake in goals. Config npc cannot exist twice in your goals. In this case, while the bot is loading your goals and reading them from top to bottom, it will first set the value of config npc to 5, then read two lines later and set the value of config npc to 10 instead. This means your bot can only farm level 10 npcs, and will not hit 5s at all. Be careful that you don't mistakenly duplicate lines in goals that are not intended to be.

Certain config goals in the bot can be turned on and off with a 0 or 1. Still others have a 2 or higher number as an option. Each configuration goal will be explained in the guide later, but for general knowledge:

• 0 means off/no/false
• 1 means on/yes/true

To be sure you are typing your goals correctly, view the usage and examples in this wiki, and write them exactly as you see them as far as spacing and symbols go.

CategoryHowTo