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.
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 this config valley setting as the maximum level valley to obtain. Anytime 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.
|Usage:||valleytroops [/type:string] [/level:#] [level#] troop-string|
valleytroops 1 s:5000
forest or fo
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 setup 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:
This directive works the same as npc10limit, 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.
0 Do not hunt for medals
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.
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 it's 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.
|Usage:|| config valleyfarming:[level]|
valleyfarming forest_miles desert_miles hill_miles swamp_miles grassland_miles lake_miles
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, eg: 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.
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 first scout all valleys of the right levels within it's valley capturing radius as specified in distancepolicy. It is recommend to keep the number of miles to around 10 or less for this, otherwise the bot will spend all it's time scouting instead of actually attacking. When it finds valleys it's able to hit, it stores their coordinates for future attacking.
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 balista, 1 pike and 1 swordsmen are sent.
The following quantites 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: 25000
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 remove the safevalleyfarm goal. On every reconnection, the list of valleys 10 miles around your main is evaluated to see if a valley level has changed. If this is the case, safe farming is returned to a clear state and scouting restarts with a fresh list of valleys.
- 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 select what type of valleys you want to farm, only the levels.
- There is currently no way to specify what troops to use to attack a valley.
- Make sure you hold all your valleys before activating safe valley farming. You do not want to capture valleys with safe valley farming.
- There is still a small chance that an attack on a valley sent before maintenance hits the wrong level of valley after maintenance yielding losses. There is code to try and recall if the valley levels, but it can run only if the hit would occur while the bot is connected.