This goal, combined with AbandonFlats, can instruct the bot to automatically capture, hold, and release flats for maintenance to level them up in order to build npcs of the desired level. With this goal enabled, the bot will attempt to acquire (capture) all flats within the npc building distance specificed in DistancePolicy or NpcBuildPolicy and hold them. It will hold as many flats as possible, so be aware you will lose valleys in order to hold them.

The bot will use any available hero for flat acquisition, unless specified otherwise in ValleyHeroes.

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.
Beginning with version 2695, the maximum limit in miles is 150, rather than 50.

Distancepolicy supports fractional numbers, ie - 10.5 miles.

In order the numbers signify the distance for: npc farming, then npc building, then medal or valley farming, then valley acquisition, then map scanning and view distance.

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 replace NoAbandonFlats, NpcExcludeList, and Npc10ExcludeList.

By enabling this goal, the bot is instructed to farm the appropriate levels of valleys for medals. The bot will abandon 1 or more of your valleys to free up slots to hunt with. The bot hunts for medals via the catch & release method - capturing a valley and abandoning it before the next attack lands. The bot will use the specified ValleyTroops for medal hunting, or the default if not set.

The nearest valley of the right level that is within the maximum miles for medal farming as set in DistancePolicy will be used, unless specified otherwise with HuntingPos or HuntingType.

The bot will use any available hero for hunting, unless specified otherwise in ValleyHeroes.

The default troops used to medal hunt and valley farm:

Instead of allowing the bot to farm medals at the nearest valley of the level specified in config Hunting, this goal will tell the bot to medal hunt only at the specified coordinates.

Instead of allowing the bot to farm medals at the nearest valley of the level specified in config Hunting, this goal will tell the bot to restrict its medal hunting to only valleys of this type. In the example above, the bot will only attempt to hunt for medals in deserts found within the number of miles specified in DistancePolicy.

This directive tells the bot how many teams it may send out at a time. This will count npc farmers, valley farmers, valley acquisition, etc., teams, not just npc farmers. RallyPolicy is a better choice for this if you want to limit just a specific type of team.

This directive will tell the bot to attempt to find and farm for resources and medals within valleys of the specified level that it can safely hit for zero losses. The bot will scout all valleys of the right levels within its medal/valleyfarming radius as specified in DistancePolicy (the 3rd number). It is recommended to keep the number of miles to around 10 or less for this; otherwise the bot will spend a lot of time scouting valleys. When the bot finds a valley that is safe to attack for no losses, it will send an attack while continuing to scout for more. It will remember the coordinates to safe valleys to hit, and attack them once an hour for resources and medals.

The bot will use any available hero for safevalleyfarming, unless specified otherwise in ValleyHeroes.

The following rules are applied for safe farming:

• with a valley that has only archers on it, 1 scout and as many cavs as there are archers on the valley are sent.
• with a valley that has no cavs and no archers, only archers are sent with a quantity based on the valley level.
• with a valley that has cavs and no archers but up to 2 layers, archers with a quantity based on the valley level, accompanied with 1 ballista, 1 pike and 1 sword are sent.

The following quantities of archers for each valley level are used:

1: 50 / 2: 100 / 3: 200 / 4: 500 / 5: 1000 / 6: 2000 / 7: 4000 / 8: 8000 / 9: 15000 / 10: 30000

Valleys get farmed at most once per hour, so it is possible that not all found valleys will be farmed due to closer valleys being ready to hit again.

Saving goals with the same list of valley levels will not disrupt valley farming operations. If however you change the valley levels, the list of valleys to farm is reset and scouting will have to be performed again. To stop farming simply comment (# or // at the beginning of the line) or remove the safevalleyfarm goal.You can also use safevalleyfarm off in goals to disable it. On every reconnection, safe farming is returned to a clear state and scouting restarts with a fresh list of valleys.

Using the ValleyFarming directive you can optionally specify what distance the bot will safevalleyfarm specific types of valleys, if you wish. For example, with the following goals:

safevalleyfarm 9,10
valleyfarming 10 3 10 3 3 3

Your bot will scout and if possible safefarm level 9 and 10 forests and hills for 10 miles out, and deserts, swamps, grasslands, and lakes for 3 miles out. You would not include the config valleyfarming goal along with safevalleyfarm.

Limitations:

• Safe valley farming cannot be used at the same time as config hunting and will not perform any operations.
• There is currently no way to specify what troops to use to attack a valley.
• Make sure all your valley slots are filled before activating safe valley farming. You do not want to capture valleys with safe valley farming.

This goal tells the bot to capture valleys for increased resource production in your cities. The bot will automatically know to capture forests for cities with a higher production of lumber, hills for cities with a higher production of iron, deserts for cities with a higher production of stone, and lakes for cities with a higher production of food. You will benefit more from valleys (more than 200k per hour production bonus) in a pure resource city of all lumber or all iron, rather than mixed fields with partial lumber and iron.

If config ValleyMin is present, the bot will use the config Valley setting as the maximum level valley to obtain. Using both goals in combination, any time a valley becomes available of a higher level (up to this maximum), the bot will drop the lowest level valley to upgrade to the higher one, until all valleys are of this level.

The bot will use any available hero for valley acquisition, unless specified otherwise in ValleyHeroes.

Valley Production Bonus

The following is a table listing the benefits given for each valley type and level.

Enabling valley farming will tell the bot you want it to continually attack nearby valleys for extra resources. In the above example, config valleyfarming:10 tells the bot to farm level 10 valleys, and valleyfarming 5 0 5 0 0 0 tells the bot that you want it to farm up to 5 miles for forests and hills, but not farm any of the other types.

If you enable config valleyfarming, but do not specify the types of valleys to farm, the bot will farm valleys of the same resource type as the city, e.g., the bot will farm forests if your city is mostly lumber.

The bot will use any available hero for valleyfarming, unless specified otherwise in ValleyHeroes.

The default troops used to medal hunt and valley farm:

This directive will tell the bot which heroes it may or may not use to acquire flats for holding or npc building, as well as heroes for valley acquisition, hunting, valleyfarming, and safevalleyfarming.

In the 1st example above, only the heroes named AttackDude and ValleyGuy would be allowed to perform any march against a valley or flat.

In the 2nd example above, using advanced hero strings, any hero with 60+ attack other than the traininghero would be usable. I've found safevalleyfarm will often lose troops if a politics or intel hero with very low attack are sent. Since adding this to my goals, I have had no more losses on safevalleyfarming and much lower losses on everything else.

See HeroString for details on how to set up the hero string for this goal.

When running this command from the script window instead of as a goal, you can use the \reset switch to clear all valleyheroes in memory, either from scripts or goals. For example: valleyheroes /reset. Note that clearing via script will only last until the bot is restarted, unless the script is ran each restart, or the goals are cleared as well.

This directive works the same as NpcLimits, only for attacking valleys. This tells the bot the minimum number of troops it must have in the city before it will attack another valley. In the example above, the bot must have 50k archers and 100k warriors before it will resume valley or medal farming.

This goal tells the bot the minimum level of valley you wish it to acquire for resource production. It must be used alongside config Valley as a maximum. The bot will acquire the highest level valleys it can find first up to the maximum setting, and then acquire lower and lower ones until all slots are filled, or valleymin is reached.

If you wish to change the default troops sent to each valley and flat while capturing valleys for resources, building npcs, or medal farming, you can specify the troops using this directive. If any level is omitted, the bot will use the default. In the above examples, the bot would use 5k scouts to attack level 1-3 valleys & flats, 10k scouts to attack level 4-5 valleys & flats, 50k scouts to attack level 6-7 valleys & flats, 100k scouts to attack level 8 valleys & flats, 12.8k archers/1 sword+pike+scout/40k warriors to attack level 9 valleys & flats, and 19990 archers/1 sword+pike+scout/60k warriors to attack level 10 valleys & flats.

Optional switches for level and valley type may be added to override other valleytroop goals, or defaults. In the last two lines of examples above, the bot is instructed to use 19990 archers/1 sword+pike+scout/60k warriors to attack level 10 valleys & flats, but if the level 10 valley is a forest, it will instead use 100k scouts. An option like this could, for instance, allow you to set up the bot to do your medal hunting with safer and slower troops, while grabbing the forests it needs for resource production with faster scouts.

Default Valley Troops

The default troops used to capture valleys, capture flats for npc building, etc.:

The default troops used to medal hunt and valley farm: