Hero Goals - Revision history

Inanna: /* HeroString */

2012-08-16T23:37:27Z

‎HeroString

Inanna: /* Nolevelheroes */

2012-08-16T09:36:51Z

‎Nolevelheroes

Inanna: /* Valleyheroes */

2012-08-16T09:36:35Z

‎Valleyheroes

Inanna: /* Fasthero */

2012-08-16T09:36:19Z

‎Fasthero

Inanna: /* HeroString */

2012-08-16T09:36:00Z

‎HeroString

Inanna: /* HeroString */

2012-08-16T09:35:18Z

‎HeroString

Anonymous: /* HeroString */ added 'none'

2012-07-04T19:34:44Z

‎HeroString: added 'none'

Inanna: /* Traininghero */

2012-02-13T15:39:52Z

‎Traininghero

Inanna: /* Traininghero */

2012-02-13T15:37:54Z

‎Traininghero

Inanna: /* HeroString */

2012-02-05T12:42:47Z

‎HeroString

@@ Line 52: / Line 52: @@
 You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any' or even use no hero at all with 'none'. For example,
-<u>valleyheroes BigGuy</u> ''this would allow only hero BigGuy to attack valleys & flats''<br>
+<u>valleyheroes Biggy</u> ''this would allow only hero Biggy to attack valleys & flats''<br>
-<u>npcheroes any,!Intelguy,!BigGuy</u> ''this would allow any hero except IntelGuy and except BigGuy to hit npcs''<br>
+<u>npcheroes any,!Smarty,!Biggy</u> ''this would allow any hero except Smarty and except Biggy to hit npcs''<br>
-<u>npcheroes 10 BigGuy,PoliGuy,IntelGuy</u> ''this would allow heroes BigGuy, PoliGuy, and IntelGuy to hit npc10s''<br>
+<u>npcheroes 10 Biggy,Polly,Smarty</u> ''this would allow heroes Biggy, Polly, and Smarty to hit npc10s''<br>
 <u>reinforce 123,456 none c:100000</u> ''this would allow you to reinforce 123,456 with cav but not to include a hero''
@@ Line 64: / Line 64: @@
 <u>npcheroes 8 any:politics=best</u> ''this would allow the best politics hero to hit npc8s''<br>
 <u>npcheroes 10 any:attack>300,base>60</u> ''this would allow any attack hero with both an attack over 300 AND a base over 60 to hit npc10s''<br>
-<u>attack 111,222 !BigGuy,any:attack>180 c:99k,s:1k</u> ''this would attack coordinates 111,222 with any hero over 180 attack other than hero BigGuy with 99k cavs, 1k scouts''<br>
+<u>attack 111,222 !Biggy,any:attack>180 c:99k,s:1k</u> ''this would attack coordinates 111,222 with any hero over 180 attack other than hero Biggy with 99k cavs, 1k scouts''<br>
-<u>attack 111,222 !PoliticsGuy,any:attack<100 w:5k</u> ''this would attack coordinates 111,222 with any hero under 100 attack other than hero PoliticsGuy with 5k warriors''
+<u>attack 111,222 !Polly,any:attack<100 w:5k</u> ''this would attack coordinates 111,222 with any hero under 100 attack other than hero Polly with 5k warriors''
 If you wish to apply seperate filters to seperate heroes, use multiple lines. For example,

← Older revision		Revision as of 09:36, 16 August 2012
Line 375:		Line 375:

	Another example, incorporating the new advanced hero strings: ''nolevelheros any:intel>=163'' would allow your intel heroes to grow until 163 int, then stop, letting you save up the points for adding to attack in the future... saving you holy waters to create a nice mech hitter. :)		Another example, incorporating the new advanced hero strings: ''nolevelheros any:intel>=163'' would allow your intel heroes to grow until 163 int, then stop, letting you save up the points for adding to attack in the future... saving you holy waters to create a nice mech hitter. :)
−
−	~~''Advanced hero strings added in revisions after Nov 4, 2011.''~~

	<br>		<br>

← Older revision		Revision as of 09:36, 16 August 2012
Line 181:		Line 181:

	See [[Hero_Goals#HeroString\|Hero String]] for details on how to setup the hero string for this goal. <br>		See [[Hero_Goals#HeroString\|Hero String]] for details on how to setup the hero string for this goal. <br>
−	~~''Advanced hero strings were added in revisions after Nov 4, 2011.''~~

	<br>		<br>

← Older revision		Revision as of 09:36, 16 August 2012
Line 41:		Line 41:

	A helpful tip if filling multiple slots of heroes with fasthero in a city that is capable of farming npcs is to set valleyheroes and npcheroes using advanced hero strings to only use those with a high(er) base. For example, ''npcheroes 5 any:base>=65'', would allow npc farming to only send out any hero with 65 or higher base, so that the junk ones fasthero is still processing will be idle for it to fire and replace.		A helpful tip if filling multiple slots of heroes with fasthero in a city that is capable of farming npcs is to set valleyheroes and npcheroes using advanced hero strings to only use those with a high(er) base. For example, ''npcheroes 5 any:base>=65'', would allow npc farming to only send out any hero with 65 or higher base, so that the junk ones fasthero is still processing will be idle for it to fire and replace.
−
−	~~''Advanced hero strings were added in revisions after Nov 4, 2011.''~~

	If fasthero is set to 120 or higher, then it will search for heroes in a different way. The hero's combined base of attack + intel will be taken into account. So for example, if a hero has 65 attack and 65 intel and is level 10, it's combined base would be 65+65-10 = 120 and would be kept with config fasthero:120. When selecting which hero to fire with a 120+ fasthero setting, the bot will choose from all available heroes, not just idle ones.		If fasthero is set to 120 or higher, then it will search for heroes in a different way. The hero's combined base of attack + intel will be taken into account. So for example, if a hero has 65 attack and 65 intel and is level 10, it's combined base would be 65+65-10 = 120 and would be kept with config fasthero:120. When selecting which hero to fire with a 120+ fasthero setting, the bot will choose from all available heroes, not just idle ones.

← Older revision		Revision as of 09:36, 16 August 2012
Line 60:		Line 60:


−	~~In revisions after Nov 4, 2011, you~~ may also use advanced filters in hero strings in the format of hero:filter. The hero name list (or 'any') must be stated first, followed by the filter(s). Any filters listed will apply to the entire line. For example,	+	You may also use advanced filters in hero strings in the format of hero:filter. The hero name list (or 'any') must be stated first, followed by the filter(s). Any filters listed will apply to the entire line. For example,

	<u>valleyheroes any:attack>180</u> ''this would allow any hero with an attack over 180 to attack valleys & flats''<br>		<u>valleyheroes any:attack>180</u> ''this would allow any hero with an attack over 180 to attack valleys & flats''<br>

@@ Line 50: / Line 50: @@
 ==HeroString==
-Many places in YAEB will allow you to specify heroes. The selection or list of heroes to be used will be referred to as the hero-string in various other places in the wiki.
+Many places in the bot will allow you to specify heroes. The selection or list of heroes to be used will be referred to as the hero-string in various other places in the wiki.
 You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any' or even use no hero at all with 'none'. For example,

@@ Line 323: / Line 323: @@
 |}
-This directive will tell the bot who your main training hero is for use in queuing troops. You can have a different traininghero for different towns, or the same one for all towns. This hero will be automatically moved by the bot to each town that lists it as it's traininghero. By default the bot will remain for 10 minutes in each town. You can adjust this duration to stay by adding a time, in seconds, to the end of the line. In the first example above, BigGuy will stay in the town for 10 minutes to queue/farm before moving along. In the second example above, BigGuy will stay in the town for 120 seconds (2 minutes) to queue/farm before moving along. In the third example above, BigGuy would stay at least 120 seconds (2 minutes), and may leave the city after at least 10 npc hits are made, or at least 2400 seconds (40 minutes) have passed.
+This directive will tell the bot who your main training hero is for use in queuing troops. You can have a different traininghero for different towns, or the same one for all towns. This hero will be automatically moved by the bot to each town that lists it as it's traininghero. By default the bot will remain for 10 minutes in each town. You can adjust this duration to stay by adding a time, in seconds, to the end of the line.
 The bot does not detect whether the traininghero is needed to queue in a town before sending it. If the traininghero is setup to farm npcs in the city, and a "0" is given as the optional npchits value, then the bot will not farm npcs in that town. It needs to be at least "1". Also if the traininghero is setup to farm npcs in the city and the remaining stay of the default 10 minutes or the configured maxstay time is less than the round trip travel time to the next npc for him to farm, he will still hit that npc even though it exceeds the maxstay. He will be moved to the next city upon returning from a npc trip that exceeds the maxstay time.

@@ Line 333: / Line 333: @@
 npcheroes 5 !BigGuy,any
 </pre>
 <span style="color:red">Be sure not to set a town that is in 24 hour advanced teleport lockdown with your main traininghero, or it will get stuck!</span>

@@ Line 62: / Line 62: @@
 <u>valleyheroes any:attack>180</u> ''this would allow any hero with an attack over 180 to attack valleys & flats''<br>
-<u>valleyhereos any:politics<200</u> ''this would allow any hero with politics under 200 to attack valleys & flats''<br>
+<u>valleyheroes any:politics<200</u> ''this would allow any hero with politics under 200 to attack valleys & flats''<br>
 <u>npcheroes 8 any:politics=best</u> ''this would allow the best politics hero to hit npc8s''<br>
 <u>npcheroes 10 any:attack>300,base>60</u> ''this would allow any attack hero with both an attack over 300 AND a base over 60 to hit npc10s''<br>