Diff for "Hero" - NEAT Portal Wiki

Diff for "Hero"

Differences between revisions 11 and 14 (spanning 3 versions)

Usage:	config hero:[switch]
Example:	config hero:10
Switch:	0 - Disable Hero Management 1 - Level up & reward heroes only 10 - Keep 1 good Politics hero all other attack heroes 11 - Keep 1 good Politics and 1 good Intel hero all others attack heroes 12 - Keep 1 good Politics and 2 good Intel heroes all others attack heroes 20 - Keep 2 good Politics heroes all others attack heroes 21 - Keep 2 good Politics and 1 good Intel hero all others attack heroes 22 - Keep 2 good Politics and 2 good Intel heroes all others attack heroes

This config will tell the bot how you wish your heroes to be hired and managed by the various automated tasks the bot does.

In the the 3rd example above (switch 10), the bot will keep 1 politics hero and in all the rest of your available feasting hall slots it will keep attack heroes.

This goal must be set to 10+ in order for FastHero to function.

It is important to note that when a task in the bot, for example TrainingHero movement or FastHero, need a space opened up in the feasting hall that it will consider config hero as its base for what type of hero to fire. If you have for example, config hero:20 then it will disregard the 2 best politics heroes, and then fire one of the remaining heroes with the worst attack score. This worst attack score could very well be an intel hero or a third poli hero. It will not necessarily fire the lowest level hero or a junk captured hero if they have a better attack score. Config hero should reflect what type of heroes you want left in the city, and used alongside KeepHeroes and KeepCapturedHeroes goals to ensure the bot never fires a hero you want to keep.

CategoryAllGoals CategoryHeroGoals CategoryConfigGoals

Hero (last edited 2015-08-20 15:10:20 by Inanna)

-  ⇤ ← Revision 11 as of 2012-09-06 11:44:38 → 
  Size: 2424
  Editor: Inanna
  Comment:
+   ← Revision 14 as of 2012-12-10 20:42:38 → ⇥
  Size: 2479
  Editor: Susannah
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 8:
-In the example above, the bot will keep 1 politics hero and all the rest of your available feasting hall slots attack heroes.
+In the the 3rd example above (switch 10), the bot will keep 1 politics hero and in all the rest of your available feasting hall slots it will keep attack heroes.
 Line 12:
-It is important to note that when a task in the bot, for example TrainingHero movement or FastHero, need a space opened up in the feasting hall that it will consider config hero as it's base for what type of hero to fire. If you have for example, config hero:20 then it will disregard the 2 best politics heroes, and then fire one of the remaining heroes with the worst attack score. This worst attack score could very well be an intel hero or a third poli hero. It will not necessarily fire the lowest level hero or a junk captured hero if they have a better attack score. Config hero should reflect what type of heroes you want left in the city, and used alongside KeepHeroes and KeepCapturedHeroes goals to ensure the bot never fires a hero you want to keep.
+It is important to note that when a task in the bot, for example TrainingHero movement or FastHero, need a space opened up in the feasting hall that it will consider config hero as its base for what type of hero to fire. If you have for example, config hero:20 then it will disregard the 2 best politics heroes, and then fire one of the remaining heroes with the worst attack score. This worst attack score could very well be an intel hero or a third poli hero. It will not necessarily fire the lowest level hero or a junk captured hero if they have a better attack score. Config hero should reflect what type of heroes you want left in the city, and used alongside KeepHeroes and KeepCapturedHeroes goals to ensure the bot never fires a hero you want to keep.
 Line 15:
-CategoryAllGoals CategoryHeroGoals
+CategoryAllGoals CategoryHeroGoals CategoryConfigGoals