Diff for "ProcessingPolicy" - NEAT Portal Wiki

Diff for "ProcessingPolicy"

Differences between revisions 14 and 15

Usage:	processingpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy[:priority] policy[:priority]
Default:	processingpolicy q:10 b:10 a:10 v:10 s:10 m:10 t:10 r:10 n:10
Arguments:	q = resque b = buildnpc v = valleyfarming n = npcfarming s = safevalleyfarming a = valleyacquisition m = medalhunting t = sendtroops r = sendresources

This policy will allow you to instruct the bot the priority with which it will try to perform it's tasks such as npc farming, valley acquisition, etc.

By default all tasks have equal priority in the bot, so the bot would try to send out roughly the same number of each task. For example, after a few hours of running, the bot would have attempted to send out the same number of npc farmers as it would have medal farmers, if both tasks were equal in priority in your goals (or not specified at all). Troops, heroes, or farming targets could prevent it from actually sending equal amounts of course. Each time the bot sends out a mission of a certain type, it will accumulate a higher internal point value on that task. Tasks with the lowest points will be given priority to perform first, when possible.

You can specify one or more tasks to have higher priority than some or all others. For example, if you used in goals processingpolicy n:10 m:20 then medal farming would have a 2x higher priority than npc farming, and roughly double the number of medal farmers would be sent to the number of npc farmers. Once again - if you have heroes or troops limiting medal farmers or just don't have the valleys to farm, the bot may not be able to keep the ratio you desire.

The default priority for any task is 10 if not specified. You can however specify some lower than that. You are also able to use the * (asterix) symbol to include any task not specified. For example, processingpolicy n:10 m:20 *:5 in your goals would mean to give 10 priority to npc farmers, 20 to medal farmers, and 5 to everything else. In that example, there would be roughly 4x more medal farmers sent out as anything else, 2x more npc farmers sent out as anything else, and 2x more medal farmers sent out than npc farmers.

You can turn off certain tasks using the ! symbol. For example, processingpolicy !b would disable npc building completely. You can even use the * to disable everything but what you specify. For example, processingpolicy m:10 n:20 a:30 !* would give medal farming a priority of 10, npc farming a priority of 20, valley acquisition a priority of 30, and disable everything else.

Disabling a task in processingpolicy can be written a few ways for your convenience. The following examples all mean the same thing - disable npc building:

         processingpolicy !b
         processingpolicy b:0
         processingpolicy b:off
         processingpolicy b:false
         processingpolicy b:no

You can also specify times to turn on or off certain tasks. For example, if you wanted to disable npc farming between the hours of 1pm and 2pm, you could do processingpolicy /start:13:00 /end:1400 !n

Processingpolicy allows using a = instead of a : in all places as well for your convenience. The following examples both mean the same thing - disable npc farming between the hours of 1pm and 2pm:

         processingpolicy /start:13:00 /end:14:00 !n
         processingpolicy /start=13:00 /end=14:00 !n

Using the = is not limited to just timed policies. You can use it freely in all processingpolicy goals, for example processingpolicy n=10 b=20 a=30 works too.

CategoryAllGoals CategoryCityGoals

ProcessingPolicy (last edited 2016-09-15 21:38:15 by Inanna)

-  ⇤ ← Revision 14 as of 2012-08-25 19:08:19 → 
  Size: 2140
  Editor: Susannah
  Comment:
+   ← Revision 15 as of 2013-08-08 15:21:22 → ⇥
  Size: 4453
  Editor: Inanna
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-||<tablebgcolor="#F9F9F9" tablestyle="margin:1em 1em 1em 0px;border-style:solid;border-color:rgb(170, 170, 170);color:rgb(0, 0, 0);font-family:sans-serif;font-size:13px;line-height:19.5px;text-align:start;" tableclass="wikitable"#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">Usage: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">processingpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy-list ||
||<style="border-style: solid; border-color: rgb(170, 170, 170); padding: 0.2em; background-color: rgb(242, 242, 242); ">Example: ||<style="border-style: solid; border-color: rgb(170, 170, 170); padding: 0.2em; ">processingpolicy t b r a n<<BR>>processingpolicy buildnpc valleyacquisition npcfarming<<BR>>processingpolicy /start:13:00:00 /end:13:59:59 medalhunting<<BR>>processingpolicy /start:13:00:00 /end:13:59:59 !medalhunting ||
+||<tablebgcolor="#F9F9F9" tablestyle="margin:1em 1em 1em 0px;border-style:solid;border-color:rgb(170, 170, 170);color:rgb(0, 0, 0);font-family:sans-serif;font-size:13px;line-height:19.5px;text-align:start;" tableclass="wikitable"#F2F2F2 style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">Usage: ||<style="border-style:solid;border-color:rgb(170, 170, 170);padding:0.2em;">processingpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy[:priority] policy[:priority] ||
||<style="border-style: solid; border-color: rgb(170, 170, 170); padding: 0.2em; background-color: rgb(242, 242, 242); ">Default: ||<style="border-style: solid; border-color: rgb(170, 170, 170); padding: 0.2em; ">processingpolicy q:10 b:10 a:10 v:10 s:10 m:10 t:10 r:10 n:10 ||
 Line 5:
-This policy will allow you to instruct the bot the order in which it will perform its functions.
+This policy will allow you to instruct the bot the priority with which it will try to perform it's tasks such as npc farming, valley acquisition, etc.
 Line 7:
-In the first example above, the bot will send troops if/as goals specify, then build npcs, then transport resources, then capture valleys for production, then npc farm...all of it before any other normal processing is done.
+By default all tasks have equal priority in the bot, so the bot would try to send out roughly the same number of each task. For example, after a few hours of running, the bot would have attempted to send out the same number of npc farmers as it would have medal farmers, if both tasks were equal in priority in your goals (or not specified at all). Troops, heroes, or farming targets could prevent it from actually sending equal amounts of course. Each time the bot sends out a mission of a certain type, it will accumulate a higher internal point value on that task. Tasks with the lowest points will be given priority to perform first, when possible.
 Line 9:
-In the second example above, the bot will first build npcs, then capture valleys for production, then npc farm...all before any other normal processing is done.
+You can specify one or more tasks to have higher priority than some or all others. For example, if you used in goals ''processingpolicy n:10 m:20'' then medal farming would have a 2x higher priority than npc farming, and roughly double the number of medal farmers would be sent to the number of npc farmers. Once again - if you have heroes or troops limiting medal farmers or just don't have the valleys to farm, the bot may not be able to keep the ratio you desire.
 Line 11:
-In the third example above, the bot will put medal farming as the first priority before others, during the hour between 1PM to 2PM.
+The default priority for any task is 10 if not specified. You can however specify some lower than that. You are also able to use the * (asterix) symbol to include any task not specified. For example, ''processingpolicy n:10 m:20 *:5'' in your goals would mean to give 10 priority to npc farmers, 20 to medal farmers, and 5 to everything else. In that example, there would be roughly 4x more medal farmers sent out as anything else, 2x more npc farmers sent out as anything else, and 2x more medal farmers sent out than npc farmers.
 Line 13:
-In the fourth example above, the bot will '''not''' allow medal hunting during the hour between 1PM to 2PM. The ! denies a certain process from happening.
+You can turn off certain tasks using the ! symbol. For example, ''processingpolicy !b'' would disable npc building completely. You can even use the * to disable everything but what you specify. For example, ''processingpolicy m:10 n:20 a:30 !*'' would give medal farming a priority of 10, npc farming a priority of 20, valley acquisition a priority of 30, and disable everything else.
 Line 15:
+Disabling a task in processingpolicy can be written a few ways for your convenience. The following examples all mean the same thing - disable npc building:

 {{{
         processingpolicy !b
         processingpolicy b:0
         processingpolicy b:off
         processingpolicy b:false
         processingpolicy b:no
}}}

You can also specify times to turn on or off certain tasks. For example, if you wanted to disable npc farming between the hours of 1pm and 2pm, you could do ''processingpolicy /start:13:00 /end:1400 !n''

Processingpolicy allows using a = instead of a : in all places as well for your convenience. The following examples both mean the same thing - disable npc farming between the hours of 1pm and 2pm:

 {{{
         processingpolicy /start:13:00 /end:14:00 !n
         processingpolicy /start=13:00 /end=14:00 !n
}}}

Using the = is not limited to just timed policies. You can use it freely in all processingpolicy goals, for example ''processingpolicy n=10 b=20 a=30'' works too.