m (→Traininghero) |
m (→Traininghero) |
||
| Line 225: | Line 225: | ||
|- | |- | ||
! style="text-align:left;" | Example: | ! style="text-align:left;" | Example: | ||
| − | | traininghero BigGuy 120 2400 10 | + | | |
| + | <font size="2" face="courier" color="#0000FF">traininghero </font><font size="2" face="courier" color="#A43900">BigGuy 120 2400 10</font> | ||
|} | |} | ||
Revision as of 06:30, 14 June 2011
Contents
Hero
| Usage: | config hero:[switch] |
|---|---|
| Example: |
config hero:10 |
| Switch: |
0 - Disable Hero Management |
This config will tell the bot how you wish for your heroes to be hired and managed. In the example above, the bot will hire and upgrade 1 politics hero and the rest of your feasting hall slots with attack heroes. This must be set to a number higher than '1' in order for fasthero to function.
Fasthero
| Usage: | config fasthero:[attribute] |
|---|---|
| Example: |
config fasthero:65 |
With this config enabled, the bot will attempt to quickly hire and fire heroes from the inn, keeping only heroes of the attribute specified while keeping your config hero:x goal in mind. In the examples above, with config hero:10 set, you know you want the bot to keep 1 politics hero and the rest attack heroes. With config fasthero:65 set, the bot will attempt to hire & fire until it has found 1 65+ politics hero and the rest 65+ attack heroes. Having a level 1 inn in the city is recommended for this goal.
WARNING!!! The bot looks for attributes, not base, when selecting what heroes to keep.
It may fire your lvl 20 90 attack hero (with 70 base) in order to hire a lvl 50 101 attack inn hero (with 51 base). You can avoid heartache by setting up herofirelimit with a level lower than your good base heroes, or moving them to another city for safety.
Npcheroes
| Usage: | npcheroes [optional level] name1,name2,name3 |
|---|---|
| Example: |
npcheroes 10 BigGuy |
This directive tells the bot which heroes to use for which npc level. If this is not set, the bot will default to all allowed heroes to hit any npc level 1-5. You can specify heroes for every level of npc individually as shown in the examples above, or let it default to the older style by simply using 'npcheroes' with no npc level after it for all npcs of level 1-5, and 'npc10heroes' for npcs of level 10.
You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any'. In the example above, hero BigGuy will farm npc10s, hero PoliGuy will farm npc9s, all heroes other than BigGuy and IntelGuy will farm npc5s, and hero IntelGuy will farm npc4s.
NOTE: You must still enable farming of these levels of npcs via the config npc goal if you wish for the bot to farm them. Simply setting which heroes to use will not make the bot hit the npcs.
Npc10heroes
| Usage: | npc10heroes hero1,hero2,hero3 |
|---|---|
| Example: |
npc10heroes BigGuy,OtherBigGuy |
This directive tells the bot which heroes may be used to farm level 10 npcs. It is being phased out in lieu of the more powerful 'npcheroes' goal. You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any'. In the example above, only heroes BigGuy and OtherBigGuy will be used to farm npc10s.
NOTE: You must still enable farming of level 10 npcs via the npc10limit goal. Simply setting which heroes to use will not make the bot hit level 10 npcs.
Training
| Usage: | config training:[switch] |
|---|---|
| Example: |
config training:1 |
By default, when configured to hit npcs, the bot will only hit them each every 8 hours. With this config enabled and once npclimit is reached, the bot will hit npcs every 1 hour instead to level your heroes faster. If you wish to avoid going too far over your npclimit in food, you can instruct the bot to attack the npcs without transports by setting it to 2 instead, eg: config training:2.
Training10
| Usage: | config training10:[switch] |
|---|---|
| Example: |
config training10:1 |
By default, when configured to hit npc10s, the bot will only hit them each every 8 hours. With this config enabled, the bot will hit them every 1 hour instead to level your hero faster.
Trainpol
| Usage: | config trainpol:[switch] |
|---|---|
| Example: |
config trainpol:1 |
By default, the bot will not attack npcs with politics heroes. With this goal set, the politics hero will attack npcs, and be given priority for levelling by being sent before the attack heroes. Another (attack, normally) hero will be set as temporary mayor while your politics hero is out farming. You may notice a significant decrease in resource production with this enabled due to the temporary, lower politics mayors.
Trainint
| Usage: | config trainint:[switch] |
|---|---|
| Example: |
config trainint:1 |
By default, the bot will not attack npcs with intel heroes. With this goal set, the intel hero will attack npcs, and be given priority for levelling by being sent before the attack heroes.
KeepAttHome
| Usage: | config keepatthome:[switch] |
|---|---|
| Example: |
config keepatthome:1 |
By default the bot will send out all attack heroes on farming runs. With this goal set, the bot will keep the 2nd highest attack hero home in the city for defensive purposes.
Feastinghallspace
| Usage: | config feastinghallspace:[spaces] |
|---|---|
| Example: |
config feastinghallspace:1 |
This goal tells the bot how many slots empty you want in your feasting hall. With this set, the bot will attempt to fire the lowest attack attribute hero in the city until it reaches the required number of free slots.
The bot will fire heroes regardless of their politics or intel scores if they are the lowest attack score.
To avoid this you should also set herofirelimit with a level lower than your politics mayor and intel hero levels.
Nomayor
| Usage: | config nomayor:[switch] |
|---|---|
| Example: |
config nomayor:1 |
With this goal turned on, the bot will not keep a mayor appointed in the city. This will allow the politics hero to be sent out on farming runs. Note - you should use config trainpol:1 instead of config nomayor:1 to allow the politics hero to farm npcs and still be appointed mayor when it is not on a npc run.
Homeheroes
| Usage: | homeheroes [amount] |
|---|---|
| Example: |
homeheroes 3 |
This directive will tell the bot how many heroes you wish to remain in the city while it is sending troops out for farming, etc. By default, all allowed heroes are sent out for farming. If a custom npcheroes list is defined, this goal will reduce the number of heroes that are allowed to farm at a time from the list, and that have to stay home at any given time vs. using all applicable heroes that are in your feasting hall.
Traininghero
| Usage: | traininghero heroname [duration in seconds] |
|---|---|
| Example: |
traininghero BigGuy 120 |
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 example above, BigGuy will stay in the town for 120 seconds (2 minutes). The bot does not detect whether the traininghero is needed to queue in a town before sending it.
Starting in rev1707 you can add an additional minimum stay, maximum stay, and number of npcs to hit for the traininghero at each city.
| Usage: | traininghero heroname [[minstay [maxstay [npchits]]] |
|---|---|
| Example: |
traininghero BigGuy 120 2400 10 |
In the above example, BigGuy would stay at least 120 seconds, and may leave the city after at least 10 npc hits are made, or at least 2400 seconds have passed. Default minimum stay is 300 seconds.
Be sure not to set a town that is in 24 hour advanced teleport lockdown with your main traininghero, or it will get stuck!
Spamheroes
| Usage: | spamheroes hero1,hero2,hero3 |
|---|---|
| Example: | spamheroes !BigGuy,!OtherBigGuy,any |
This directive will tell the bot which heroes it may or may not use with loyaltyattack or spamattack. You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any'. In the example above, heroes BigGuy and OtherBigGuy will not be used, but any other hero may.
NotSpamheroes
| Usage: | notspamheroes hero1,hero2,hero3 |
|---|---|
| Example: | notspamheroes BigGuy,OtherBigGuy |
This directive will tell the bot which heroes are not used with loyaltyattack or spamattack. You may list hero names individually, and/or exclude heroes with '!name', and/or include all heroes with 'any'. In the example above, heroes BigGuy and OtherBigGuy will not be used, but any other hero may.
Nolevelheroes
| Usage: | nolevelheroes hero1,hero2,hero3 |
|---|---|
| Example: | nolevelheroes ForBob |
This directive will tell the bot not to upgrade a hero or heroes. In the example above, if the hero ForBob was being trained to give away to your friend Bob, you wouldn't want it to be upgraded due to Bob's rank and medal requirements. Setting this will allow ForBob to gain experience without being levelled up by the bot.
Herofirelimit
| Usage: | herofirelimit [level] |
|---|---|
| Example: | herofirelimit 70 |
This directive will tell the bot not to automatically fire any hero of the level specified. When not set, the default level to keep is 50.
Capturedfirelimit
| Usage: | capturedfirelimit [level] |
|---|---|
| Example: | capturedfirelimit 100 |
This directive will tell the bot not to automatically fire any captured hero of the level specified.