NPC Goals - Revision history

Inanna: /* Npcbounds */

2012-08-16T09:40:46Z

‎Npcbounds

Inanna: /* Npctroops */

2012-08-16T09:40:30Z

‎Npctroops

Inanna: /* Npclist */

2012-08-16T09:40:20Z

‎Npclist

Inanna: /* Npc */

2012-08-16T09:40:04Z

‎Npc

Inanna: /* Npc10list */

2012-08-16T09:39:35Z

‎Npc10list

Inanna: /* Farmingcyclemin */

2012-08-16T09:39:10Z

‎Farmingcyclemin

Inanna: /* Npclimit */

2012-08-16T09:38:27Z

‎Npclimit

Inanna: /* Npcteams */

2012-06-24T23:32:56Z

‎Npcteams

Inanna at 17:37, 21 November 2011

2011-11-21T17:37:31Z

Show changes

Inanna: /* Farmingcyclemin */

2011-11-16T16:51:02Z

‎Farmingcyclemin

@@ Line 238: / Line 238: @@
 |}
-By default, Y.A.E.B. will find and farm npcs on it's own as specified with [[NPC_Goals#Farmingpolicy|farmingpolicy]]. However, you may sometimes wish to restrict your bot to only farm npcs in a specific area. You can do so with this directive. This tells the bot the bounderies in which it may farm. In the example above, the bot would be allowed to farm in a square with the top left corner at 200,400 and the bottom right corner at 215,415 for level 5 npcs. In the 2nd example above, the bot will only farm level 8 npcs between 200,400 and 205,405.
+By default, the bot will find and farm npcs on it's own as specified with [[NPC_Goals#Farmingpolicy|farmingpolicy]]. However, you may sometimes wish to restrict your bot to only farm npcs in a specific area. You can do so with this directive. This tells the bot the bounderies in which it may farm. In the example above, the bot would be allowed to farm in a square with the top left corner at 200,400 and the bottom right corner at 215,415 for level 5 npcs. In the 2nd example above, the bot will only farm level 8 npcs between 200,400 and 205,405.
 The bot will process which npcs to farm based on the priorities specified [[NPC_Goals#Farming_Restrictions|here]].

@@ Line 164: / Line 164: @@
 |}
-By deafult, Y.A.E.B. will send out what it thinks is the optimal troop setup for each level of npc it farms. You can configure your own troop settings with this directive. In the example above, the bot will send out 400 ballista and 400 transports to level 5 npcs, 100k warriors to level 8 npcs, and 90k archers/2k workers/2k warriors/2k transports to level 9 and 10 npcs.
+By deafult, the bot will send out what it thinks is the optimal troop setup for each level of npc it farms. You can configure your own troop settings with this directive. In the example above, the bot will send out 400 ballista and 400 transports to level 5 npcs, 100k warriors to level 8 npcs, and 90k archers/2k workers/2k warriors/2k transports to level 9 and 10 npcs.
 You can let the bot decide how many transports to send on a npc run by leaving them out in the goal. The bot will then send enough transports for a full plunder based on your logistics level. If you wish the bot to actually send 0 transports, use t:0 in the goal.

@@ Line 144: / Line 144: @@
 |}
-By default, Y.A.E.B. will find and farm npcs on it's own of the level you specify via the config npc goal. However, you may sometimes wish to restrict your bot to only farm specific npcs. You can do so with this directive. By listing the coordinates of every npc you wish the bot to farm, you can restrict it's farming. In the examples above, the bot will farm level level 5 npcs at the specified coordinates, and level 8 npcs at the other specified coordinates. Details on how the bot prioritizes which npcs to farm with the various available settings can be found [[NPC_Goals#Farming_Restrictions|here]].
+By default, the bot will find and farm npcs on it's own of the level you specify via the config npc goal. However, you may sometimes wish to restrict your bot to only farm specific npcs. You can do so with this directive. By listing the coordinates of every npc you wish the bot to farm, you can restrict it's farming. In the examples above, the bot will farm level level 5 npcs at the specified coordinates, and level 8 npcs at the other specified coordinates. Details on how the bot prioritizes which npcs to farm with the various available settings can be found [[NPC_Goals#Farming_Restrictions|here]].
 NOTE: it is not recommended to use this unless you need to due to sharing npcs with a friendly neighbor, etc. It's much better to let the bot decide what to hit.

@@ Line 40: / Line 40: @@
 If npclimit is set and reached (ie, config npclimit:10 and you have 10+ days of food in the city), and if config training:1 or config training:2 is enabled, the bot will restart again at the nearest npc every hour instead to train your heroes. The 8 hour default can be changed via [[NPC_Goals#Farmingpolicy|farmingpolicy]] for each level of npc farmed, or [[NPC_Goals#Farmingcycle|farmingcycle]] for all npcs.
-Y.A.E.B. will automatically detect maintenance and reset your farming cycle after it relogs. You can also manually reset it by typing \resetfarminghistory in the [[In-Line_Commands|Commands]] window.
+The bot will automatically detect maintenance and reset your farming cycle after it relogs. You can also manually reset it by typing \resetfarminghistory in the [[In-Line_Commands|Commands]] window.
 <br>

@@ Line 386: / Line 386: @@
 |}
-This directive is being phased out in lieu of the more powerful [[NPC_Goals#NpcLimits|npclimits]] goal that has been expanded to accept a level parameter in versions after ''rev1268''.
+This directive is being phased out in lieu of the more powerful [[NPC_Goals#NpcLimits|npclimits]] goal.
 <br>

@@ Line 220: / Line 220: @@
 |}
-By default, the bot will farm the npcs in range once every 8.4 hours, or as specified by another goal (see above). With the newest versions of the bot, it can select which npc to farm next based on a calculated "best-option" using the resources refilled in the npc since your last attack on it, and the travel time to the npc and back.
+By default, the bot will farm the npcs in range once every 8.4 hours, or as specified by another goal (see above). Using this goal, the bot can select which npc to farm next based on a calculated "best-option" using the resources refilled in the npc since your last attack on it, and the travel time to the npc and back.
 With farmingcyclemin, you can tell the bot how many hours minimum since a particular npc was hit, before it can hit it again if it's the best option to attack next. This will work in conjunction with [[NPC_Goals#Farmingcycle|config farmingcycle]], using farmingcycle as the max hours since the last hit. This goal only affects level 1-5 npc farming. If farmingcyclemin is used, but farmingcycle is not, it will default to a max 8.4 hours.

@@ Line 124: / Line 124: @@
 |}
-This goal sets a limit in days for the amount of food obtained when farming npc's. Y.A.E.B. will limit farming to the specified number of days based on your troops' food consumption.
+This goal sets a limit in days for the amount of food obtained when farming npc's. the bot will limit farming to the specified number of days based on your troops' food consumption.
 If this goal is not reached, the bot will farm your npcs once every 8 hours. Once it is reached, the bot will no longer farm until it falls below the specified number of days, or unless config training:1 or config training:2 is enabled for level 1-9 npcs, or config training10:1 is enabled for npc10s.
-If this goal is not set, the bot will default to a 1 day npclimit. You can make it unlimited by putting an unreachable number in, for example config npclimit:9999
+If this goal is not set, the bot will default to a 1 day npclimit. You can make it unlimited by putting an unreachable number in, for example config npclimit:9999. However, the bot will default to unlimited if config trading:1 is set, or default to 10 days if trading is off.
 <br>

@@ Line 358: / Line 358: @@
 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.
-[[General#Rallypolicy|Rallypolicy]] is a better way to go for this.
+[[General_Goals#Rallypolicy|Rallypolicy]] is a better way to go for this.
 <br>

@@ Line 439: / Line 439: @@
 |}
-By default, the bot will farm the npcs in range once every 8.4 hours, or as specified by another goal (see above). You can now instruct the bot to select which npc to farm next based on a calculated "best-option" using the resources refilled in the npc since your last attack on it, and the travel time to the npc and back. With farmingcyclemin, you can tell the bot how many hours minimum since a particular npc was hit, before it can hit it again. This will work in conjunction with [[NPC_Goals#Farmingcycle|config farmingcycle]], using farmingcycle as the max hours since the last hit. This goal only affects level 1-5 npc farming.
+By default, the bot will farm the npcs in range once every 8.4 hours, or as specified by another goal (see above). With the newest versions of the bot, it can select which npc to farm next based on a calculated "best-option" using the resources refilled in the npc since your last attack on it, and the travel time to the npc and back.
 For example, the bot could hit an npc 8 miles away for 100% plunder, or it could, in that same amount of time, hit 2 or more npcs 1 mile away for 50% plunder each.. the bot would chose the 1 mile away npcs instead with this goal enabled. This way you would gain the same or even more resources while having your heroes and troops closer to home for emergencies, share smaller areas of npcs with neighbors without over-farming each other as much, send less transports per mission on partially refilled npcs, and keep your closest npcs emptier than usual in order to chase away pesky neighbors that may want your nearby npcs.