NEAT Portal Wiki - User contributions [en]

Hero Scripts

2012-09-15T15:39:14Z

Inanna: /* UseHeroItem */

==FindHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| findhero stat
|-
! style="text-align:left;" | Example:
|
findHero atk 
findHero pol 
findHero int
|}

Valid command line arguments for findhero are pol for politics, atk for attack and int for intelligence.

This command will recruit the best hero of the type specified that is available in the inn at the time.

==SetMayor==

{| class="wikitable"
! style="text-align:left;" | Usage:
| setMayor stat
|-
! style="text-align:left;" | Example:
|
setMayor pol 
setMayor atk 
setMayor int 
setMayor remove
|}

Valid arguments for setMayor are pol for politics, atk for attack and int for intelligence.

This command will change your current mayor for one of the specified attribute. It automatically selects the highest level of the attribute that you specify (stat is the label for the attribute argument).
This is very useful when creating, upgrading and demolishing buildings, as you can specify the highest level politic hero you have to go into office. Capturing a level ten and only have a level 9 Feasting hall in one city? You can remove the mayor with this command to make sure he marches with the rest of the troops.

==SetMayorByName==

{| class="wikitable"
! style="text-align:left;" | Usage:
| setMayorbyname HeroName
|-
! style="text-align:left;" | Example:
|
setMayorbyname ATKATK 
setMayorbyname ken 
setMayorbyname henry
|}

This command will allow you to specify the Mayor you wish to assign by hero name.

==PersuadeHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| persuadehero hero
|-
! style="text-align:left;" | Example:
| persuadehero ken
|}

Persuade a captured hero ken, the medals required for the persuasion if any are shown in hero tab.

==FireHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| firehero hero
|-
! style="text-align:left;" | Example:
| firehero ken
|}

Used to fire a hero from the feasting hall.

The Hero status must be either idle, mayor, or captured, i.e. is not on a mission away from town.

==ReleaseHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| releasehero heroName
|-
! style="text-align:left;" | Example:
| releasehero Prisoner
|}

Used to dismiss a captive hero from the feasting hall.

==WaterHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| waterhero heroName
|-
! style="text-align:left;" | Example:
| waterhero BigGuy
|}

Used to apply holy water item to a hero in the feasting hall.

==GetSpamHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| getspamhero [optional management or strategem]
|-
! style="text-align:left;" | Example:
|
getspamhero 
getspamhero management 
getspamhero strategem
|}

First example used to get the best attack hero currently available in the inn.
Second example used to get the best politics hero currently available in the inn.
Third example used to get the Highest intelligence hero currently available in the inn.

==ChangeHeroName==

{| class="wikitable"
! style="text-align:left;" | Usage:
| changeheroname oldName newName
|-
! style="text-align:left;" | Example:
| changeheroname ken henry
|}

Used to rename a hero.

==UpLevelHero==

'''Currently not implemented'''

==UpLevelHeroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| uplevelheroes
|-
! style="text-align:left;" | Example:
| uplevelheroes
|}

Implemented, but currently does nothing unless city's config hero: is set to non-zero. (This is a bug)
Upgrades all heroes in current city (unless named in the ''NoLevelHeroes'' goal). Each hero is upgraded up only one level and its best attribute increased.

==UseHeroItem==

{| class="wikitable"
! style="text-align:left;" | Usage:
| useheroitem hero_name item_name
|-
! style="text-align:left;" | Example:
|
useheroitem BigGuy on_war 
useheroitem BigGuy anabasis 
useheroitem BigGuy nation_medal
|}

Used to apply hero buffing items to the specified hero.

==AwardGold==

{| class="wikitable"
! style="text-align:left;" | Usage:
| awardgold hero
|-
! style="text-align:left;" | Example:
| awardgold ken
|}

Used to increase hero loyalty by 5 using a gold reward.

==RewardHeroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| rewardheroes
|-
! style="text-align:left;" | Example:
| rewardheroes
|}

Finds and rewards all heroes with loyalty below 100, using gold.

==WaitHero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| waithero hero
|-
! style="text-align:left;" | Example:
| waithero ken
|}

Pause script until hero ken is available.

==WaitHeroLost==

{| class="wikitable"
! style="text-align:left;" | Usage:
| waitherolost hero1,hero2,...
|-
! style="text-align:left;" | Example:
| waitherolost ken,henry
|}

Pause script until one of the heroes specified is captured.

==listallheroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| listallheroes
|-
! style="text-align:left;" | Example:
| listallheroes
|}

Will output a list of all your heroes, seperated by city, even if they are not currently in the city.

There is a temporary (I assume) bug that prevents your training hero from being enumerated, but a bug report has been filed.

City Scripts

2012-09-13T16:28:48Z

Inanna: /* Levy */

==Comfort==

{| class="wikitable"
! style="text-align:left;" | Usage:
| comfort comforttype
|-
! style="text-align:left;" | Example:
|
comfort pray 
comfort 1 
comfort bless 
comfort 4
|}

Performs one of the comfort commands in the city that it is run from.

'''comforttype'''
{| class="wikitable"
| 1 || relief
|-
| 2 || pray
|-
| 3 || bless
|-
| 4 || popraise
|}

==Levy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| levy levytype
|-
! style="text-align:left;" | Example:
|
levy 1 
levy food 
levy 3 
levy stone 
levy 5 
|}

Performs one of the levy actions in the city run from.

'''levytype'''
{| class="wikitable"
| 1 || gold
|-
| 2 || food
|-
| 3 || wood
|-
| 4 || stone
|-
| 5 || iron
|}

==SetTaxRate==

{| class="wikitable"
! style="text-align:left;" | Usage:
| settaxrate rate%
|-
! style="text-align:left;" | Example:
| settaxrate 20
|}

Sets Tax Rate to 20%

==Production==

{| class="wikitable"
! style="text-align:left;" | Usage:
| production food% wood% stone% iron%
|-
! style="text-align:left;" | Example:
| production 100 100 100 100
|}

Sets city production of resources. You must use a number between 0 and 100. This script will also adjust the corresponding [[Resource_Goals#Production|goal of the same name]].

==SetFocus==

{| class="wikitable"
! style="text-align:left;" | Usage:
| setfocus
|-
! style="text-align:left;" | Example:
| setfocus
|}

The bot functions in a linear manner, moving from one city to the next after a given amount of time. The ''setfocus'' command will cause the bot to immediately focus on the city from which the command is issued for one task cycle. Enabling the Task Flow debug option will allow you to see what one task cycle is, and how long it lasts.

==RenameCity==

{| class="wikitable"
! style="text-align:left;" | Usage:
| renamecity newname [picture ID 1-4]
|-
! style="text-align:left;" | Example:
|
renamecity BottingRulz 
renamecity BottingRulz 3
|}

Change a city's name and (optionally) picture. The picture IDs are as follows:

1 - [[File:Citylogo_01.png]] 
2 - [[File:Citylogo_02.png]] 
3 - [[File:Citylogo_03.png]] 
4 - [[File:Citylogo_04.png]]

 

==Evacuatetown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| evacuatetown coords
|-
! style="text-align:left;" | Example:
| evacuatetown 111,222
|}

This script command will tell the bot to send all troops and resources that it can carry to the specified coordinates from this city, in order for the town to be abandoned later. The bot will leave all of the heroes in the city. You must move them manually. This script should be run before [[General_Goals#Abandon|config abandon:1]] is used in goals.

To cancel the evacuation use '''EndEvacuate'''.

==Teleport==

{| class="wikitable"
! style="text-align:left;" | Usage:
| teleport [state or coords]
|-
! style="text-align:left;" | Example:
|
teleport saxony 
teleport 111,222
|-
! style="text-align:left;" | States:
|
friesland, saxony, north march, bohemia, 
lower lorraine, franconia, thuringia, moravia, 
upper lorraine, swabia, bavaria, carinthia, 
burgundy, lombardy, tuscany, romagna
|}

Random teleports your city to the state specified, or if using coordinates instead will advanced teleport your city to the coordinates specified. When trying to advance teleport, the bot will first use the Pioneer teleports available after server merge if you have them.

==Abandon==

{| class="wikitable"
! style="text-align:left;" | Usage:
| abandon XXX,YYY
|-
! style="text-align:left;" | Example:
|
abandon 111,222 
|}

Abandon the valley at 111,222

==AbandonTown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| AbandonTown [city]
|-
! style="text-align:left;" | Example:
|
abandontown 111,222 
abandontown OtherCity
|}

*You can only run ''abandontown'' from a different city than the one you want to abandon.
*The city being abandoned can be referred to by name or coordinates.
*The bot '''does not check''' for troops or heroes. Any heroes or troops in the town '''or travelling''' from the town will be irreplacably deleted.
*Be sure your escaping troops have arrived at their destination before abandoning any city.

Abandontown should be used with care. It is best to allow the bot to BUILD NPCs, but for whatever purpose you must use this command DOUBLE CHECK that you have entered the correct coordinates or city name to be abandoned. Be sure to run 'evacuatetown' script command previous to using this command if you have troops or resources in the city to be moved.

There are No 2nd Chances using this command!

There is no crying in baseball. If you accidentaly delete your level 850 training hero, we feel really bad for you, but don't come crying to us. We cannot get it back for you.

==Buildcity==

{| class="wikitable"
! style="text-align:left;" | Usage:
| buildcity xxx,yyy
|-
! style="text-align:left;" | Example:
| buildcity 111,222
|}

Used to build a city on at 111,222. It will capture the flat for you.

To cancel a city building, use '''CancelBuildcity'''.

Advanced Scripting

2012-09-05T15:36:11Z

Inanna: /* Variables */

There is a great deal of info the bot is able to make available for the advanced scripter, via the ifgoto and ifgosub scripts. The complete list of variables usable is a work in progress, and a debt of gratitude goes to several bot users for testing and finding them. Special thanks to '''Dismayed''' for compiling it all into a list.

==Ifgoto==

{| class="wikitable"
! style="text-align:left;" | Usage:
| ifgoto ( reference {operator} value ) label
|-
! style="text-align:left;" | Example:
| ifgoto ( m_city.cityManager.resource.stone.amount > 250000 ) CheckATT
|}

See [[Advanced_Scripting#Ifgosub|ifgosub]]

==Ifgosub==

{| class="wikitable"
! style="text-align:left;" | Usage:
| ifgosub ( reference {operator} value ) label
|-
! style="text-align:left;"| Example:
| ifgosub ( m_city.cityManager.resource.stone.amount > 250000 ) CheckATT
|}

Conditional Statements enable checking of resources,troops,population,…etc.

Conditional Statements add a whole new dimension to scripts allowing more human-like interaction & less "insuffient resource" statements.

Variables for use in ifgoto & ifgosub statements can be found below.

<blockquote><pre>
ifgosub ( m_city.cityManager.resource.stone.amount > 250000 ) CheckATT
ifgosub ( m_city.cityManager.resource.iron.amount > 150000 ) CheckTrain
sleep rnd:3000
loop 0
//
label CheckTrain
ifgosub ( m_city.cityManager.resource.wood.amount > 150000 ) TrainTroops
gosubreturn
//
label CheckATT
ifgosub ( m_city.cityManager.resource.wood.amount > 250000 ) UpATT
gosubreturn
//
label TrainTroops
train arch:250 Bubba
repeat 4
gosubreturn
//
label UpATT
walldefense archertowers 250
gosubreturn
</pre></blockquote>

==Variables==

 

Please leave Updates/Comments/etc at:
https://docs.google.com/spreadsheet/ccc?key=0AmZxBXW9lbSwdHJEbVA0bnoxbXZ5QXV4eDdUMUpyQVE

 

{| class="wikitable"
! Print:
! Command:
! Result:
|-
! || ||
|-
! || ||
|-
! // Enemy || ||
|-
| print m_city.cityManager.hasEnemyArmiesWithin(60) || ||
|-
| print hasEnemyArmies------- m_city.cityManager.hasEnemyArmies || cityManager.hasEnemyArmies || .........................checked ok....................
|-
| print m_city.cityManager.enemyArmies[0].targetFieldCoords || cityManager.enemyArmies[0].targetFieldCoords || .........................checked ok....................
|-
| print m_city.cityManager.cityCoords || cityManager.cityCoords || .........................checked ok....................
|-
| print NumberOfRealAttacks------- m_city.cityManager.NumberOfRealAttacks || cityManager.NumberOfRealAttacks || .........................checked ok....................
|-
| print EnemyArmies 0 reachTime------- m_city.cityManager.enemyArmies[0].reachTime || cityManager.enemyArmies[0].reachTime || .........................checked ok....................
|-
| print enemyArmies 0 armyId-------m_city.cityManager.enemyArmies[0].armyId || cityManager.enemyArmies[0].armyId || My Result Error #1069 Supplier supplied enemyArmies 0 -------armyId 123456789
|-
| print enemyArmies 0 missionType-------m_city.cityManager.enemyArmies[0].missionType || cityManager.enemyArmies[0].missionType || My Result Error #1069 Supplier supplied enemyArmies 0 -------missionType 5
|-
| print enemyArmies 0 king-------m_city.cityManager.enemyArmies[0].king || cityManager.enemyArmies[0].king || My Result Error #1069 Supplier supplied enemyArmies 0 -------king Attacker Name
|-
| print enemyArmies 0 resource.iron-------m_city.cityManager.enemyArmies[0].resource.iron || cityManager.enemyArmies[0].resource.iron || My Result Error #1069 Supplier supplied enemyArmies 0 -------resource.iron 0
|-
| print enemyArmies 0 startFieldId-------m_city.cityManager.enemyArmies[0].startFieldId || cityManager.enemyArmies[0].startFieldId || My Result Error #1069 Supplier supplied enemyArmies 0 -------startFieldId 666999
|-
| print m_city.cityManager.enemyArmies[0].startFieldCoords || cityManager.enemyArmies[0].startFieldCoords || .........................checked ok....................
|-
| print enemyArmies 0 targetPosName-------m_city.cityManager.enemyArmies[0].targetPosName || cityManager.enemyArmies[0].targetPosName || My Result Error #1069 Supplier supplied enemyArmies 0 -------targetPosName MYCITY
|-
| print enemyArmies 0 direction-------m_city.cityManager.enemyArmies[0].direction || cityManager.enemyArmies[0].direction || My Result Error #1069 Supplier supplied enemyArmies 0 -------direction 1
|-
| print enemyArmies 0 restTime-------m_city.cityManager.enemyArmies[0].restTime || cityManager.enemyArmies[0].restTime || My Result Error #1069 Supplier supplied enemyArmies 0 -------restTime 0
|-
| print enemyArmies 0 startTime-------m_city.cityManager.enemyArmies[0].startTime || cityManager.enemyArmies[0].startTime || My Result Error #1069 Supplier supplied enemyArmies 0 -------startTime 1339652736137
|-
| print enemyArmies 0 .startPosName------- m_city.cityManager.enemyArmies[0].startPosName || cityManager.enemyArmies[0].startPosName || My Result Error #1069 Supplier supplied enemyArmies 0 -------.startPosName ATTACKING CITY
|-
| print enemyArmies 0 .heroLevel------- m_city.cityManager.enemyArmies[0].heroLevel || cityManager.enemyArmies[0].heroLevel || My Result Error #1069 Supplier supplied enemyArmies 0 -------.heroLevel 184
|-
| print enemyArmies 0 .reachTime------- m_city.cityManager.enemyArmies[0].reachTime || cityManager.enemyArmies[0].reachTime || My Result Error #1069 Supplier supplied enemyArmies 0 -------.reachTime 1339656323138
|-
| print enemyArmies 0 .hero------- m_city.cityManager.enemyArmies[0].hero || cityManager.enemyArmies[0].hero || My Result Error #1069 Supplier supplied enemyArmies 0 -------.hero HeroName
|-
| print enemyArmies 0 .targetFieldId------- m_city.cityManager.enemyArmies[0].targetFieldId || cityManager.enemyArmies[0].targetFieldId || My Result Error #1069 Supplier supplied enemyArmies 0 -------.targetFieldId 999444
|-
| print enemyArmies 0 .alliance------- m_city.cityManager.enemyArmies[0].alliance || cityManager.enemyArmies[0].alliance || My Result Error #1069 Supplier supplied enemyArmies 0 -------.alliance ATTACKING ALLIANCE
|-
| print enemyArmies 0 troop peasant------- m_city.cityManager.enemyArmies[0].troop.peasants || cityManager.enemyArmies[0].troop.peasants || .........................checked ok....................
|-
| print enemyArmies 0 troop militia------- m_city.cityManager.enemyArmies[0].troop.militia || cityManager.enemyArmies[0].troop.militia || .........................checked ok....................
|-
| print enemyArmies 0 troop scouter------- m_city.cityManager.enemyArmies[0].troop.scouter || cityManager.enemyArmies[0].troop.scouter || .........................checked ok....................
|-
| print enemyArmies 0 troop pikemen------- m_city.cityManager.enemyArmies[0].troop.pikemen || cityManager.enemyArmies[0].troop.pikemen || .........................checked ok....................
|-
| print enemyArmies 0 troop swordsmen------- m_city.cityManager.enemyArmies[0].troop.swordsmen || cityManager.enemyArmies[0].troop.swordsmen || .........................checked ok....................
|-
| print enemyArmies 0 troop archer------- m_city.cityManager.enemyArmies[0].troop.archer || cityManager.enemyArmies[0].troop.archer || .........................checked ok....................
|-
| print enemyArmies 0 troop lightCavalry------- m_city.cityManager.enemyArmies[0].troop.lightCavalry || cityManager.enemyArmies[0].troop.lightCavalry || .........................checked ok....................
|-
| print enemyArmies 0 troop heavyCavalry------- m_city.cityManager.enemyArmies[0].troop.heavyCavalry || cityManager.enemyArmies[0].troop.heavyCavalry || .........................checked ok....................
|-
| print enemyArmies 0 troop carriage------- m_city.cityManager.enemyArmies[0].troop.carriage || cityManager.enemyArmies[0].troop.carriage || .........................checked ok....................
|-
| print EnemyArmies 0 troop ballista------- m_city.cityManager.enemyArmies[0].troop.ballista || cityManager.enemyArmies[0].troop.ballista || .........................checked ok....................
|-
| print EnemyArmies troop batteringRam------- m_city.cityManager.enemyArmies[0].troop.batteringRam || cityManager.enemyArmies[0].troop.batteringRam || .........................checked ok....................
|-
| print EnemyArmies troop catapult------- m_city.cityManager.enemyArmies[0].troop.catapult || cityManager.enemyArmies[0].troop.catapult || .........................checked ok....................
|-
! // Resource || ||
|-
| print resource taxRate: ( m_city.cityManager.resource.texRate ) || cityManager.resource.texRate ) || .........................checked ok....................
|-
| print resource buildPeople: ( m_city.cityManager.resource.buildPeople ) || cityManager.resource.buildPeople ) || .........................checked ok....................
|-
| print resource complaint: ( m_city.cityManager.resource.complaint ) || cityManager.resource.complaint ) || .........................checked ok....................
|-
| print resource curPopulation: ( m_city.cityManager.resource.curPopulation ) || cityManager.resource.curPopulation ) || .........................checked ok....................
|-
| print resource food workPeople: ( m_city.cityManager.resource.food.workPeople ) || cityManager.resource.food.workPeople ) || .........................checked ok....................
|-
| print resource iron workPeople: ( m_city.cityManager.resource.iron.workPeople ) || cityManager.resource.iron.workPeople ) || .........................checked ok....................
|-
| print resource stone workPeople: ( m_city.cityManager.resource.stone.workPeople ) || cityManager.resource.stone.workPeople ) || .........................checked ok....................
|-
| print resource wood workPeople: ( m_city.cityManager.resource.wood.workPeople ) || cityManager.resource.wood.workPeople ) || .........................checked ok....................
|-
| print resource maxPopulation: ( m_city.cityManager.resource.maxPopulation ) || cityManager.resource.maxPopulation ) || .........................checked ok....................
|-
| print resource workPeople: ( m_city.cityManager.resource.workPeople ) || cityManager.resource.workPeople ) || .........................checked ok....................
|-
| print resource support: ( m_city.cityManager.resource.support ) || cityManager.resource.support ) || .........................checked ok....................
|-
| print resource food: ( m_city.cityManager.resource.food ) || cityManager.resource.food ) || .........................checked ok....................
|-
| print resource food amount: ( m_city.cityManager.resource.food.amount ) || cityManager.resource.food.amount ) || .........................checked ok....................
|-
| print resource food increaseRate: ( m_city.cityManager.resource.food.increaseRate ) || cityManager.resource.food.increaseRate ) || .........................checked ok....................
|-
| print resource food max: ( m_city.cityManager.resource.food.max ) || cityManager.resource.food.max ) || .........................checked ok....................
|-
| print resource food storeRercent: ( m_city.cityManager.resource.food.storeRercent ) || cityManager.resource.food.storeRercent ) || .........................checked ok....................
|-
| print resource troopCostFood: ( m_city.cityManager.resource.troopCostFood ) || cityManager.resource.troopCostFood ) || .........................checked ok....................
|-
| print resource gold: ( m_city.cityManager.resource.gold ) || cityManager.resource.gold ) || .........................checked ok....................
|-
| print resource taxIncome: ( m_city.cityManager.resource.taxIncome ) || cityManager.resource.taxIncome ) || .........................checked ok....................
|-
| print resource iron: ( m_city.cityManager.resource.iron ) || cityManager.resource.iron ) || .........................checked ok....................
|-
| print resource iron amount: ( m_city.cityManager.resource.iron.amount ) || cityManager.resource.iron.amount ) || .........................checked ok....................
|-
| print resource iron increaseRate: ( m_city.cityManager.resource.iron.increaseRate ) || cityManager.resource.iron.increaseRate ) || .........................checked ok....................
|-
| print resource iron max: ( m_city.cityManager.resource.iron.max ) || cityManager.resource.iron.max ) || .........................checked ok....................
|-
| print resource iron storeRercent: ( m_city.cityManager.resource.iron.storeRercent ) || cityManager.resource.iron.storeRercent ) || .........................checked ok....................
|-
| print resource stone: ( m_city.cityManager.resource.stone ) || cityManager.resource.stone ) || .........................checked ok....................
|-
| print resource stone amount: ( m_city.cityManager.resource.stone.amount ) || cityManager.resource.stone.amount ) || .........................checked ok....................
|-
| print resource stone increaseRate: ( m_city.cityManager.resource.stone.increaseRate ) || cityManager.resource.stone.increaseRate ) || .........................checked ok....................
|-
| print resource stone max: ( m_city.cityManager.resource.stone.max ) || cityManager.resource.stone.max ) || .........................checked ok....................
|-
| print resource stone storeRercent: ( m_city.cityManager.resource.stone.storeRercent ) || cityManager.resource.stone.storeRercent ) || .........................checked ok....................
|-
| print resource wood: ( m_city.cityManager.resource.wood ) || cityManager.resource.wood ) || .........................checked ok....................
|-
| print resource wood amount: ( m_city.cityManager.resource.wood.amount ) || cityManager.resource.wood.amount ) || .........................checked ok....................
|-
| print resource wood increaseRate: ( m_city.cityManager.resource.wood.increaseRate ) || cityManager.resource.wood.increaseRate ) || .........................checked ok....................
|-
| print resource wood max: ( m_city.cityManager.resource.wood.max ) || cityManager.resource.wood.max ) || .........................checked ok....................
|-
| print resource wood storeRercent: ( m_city.cityManager.resource.wood.storeRercent ) || cityManager.resource.wood.storeRercent ) || .........................checked ok....................
|-
| print castle resource support ( m_city.cityManager.castle.resource.support ) || cityManager.castle.resource.support || .........................checked ok....................
|-
| print castle resource troopCostFood ( m_city.cityManager.castle.resource.troopCostFood ) || cityManager.castle.resource.troopCostFood || .........................checked ok....................
|-
| print castle resource workPeople ( m_city.cityManager.castle.resource.workPeople ) || cityManager.castle.resource.workPeople || .........................checked ok....................
|-
| print castle resource herosSalary ( m_city.cityManager.castle.resource.herosSalary ) || cityManager.castle.resource.herosSalary || .........................checked ok....................
|-
| print castle resource maxPopulation ( m_city.cityManager.castle.resource.maxPopulation ) || cityManager.castle.resource.maxPopulation || .........................checked ok....................
|-
| print castle resource populationDirection ( m_city.cityManager.castle.resource.populationDirection ) || cityManager.castle.resource.populationDirection || .........................checked ok....................
|-
| print castle resource gold ( m_city.cityManager.castle.resource.gold ) || cityManager.castle.resource.gold || .........................checked ok....................
|-
| print castle resource curPopulation ( m_city.cityManager.castle.resource.curPopulation ) || cityManager.castle.resource.curPopulation || .........................checked ok....................
|-
| print castle resource complaint ( m_city.cityManager.castle.resource.complaint ) || cityManager.castle.resource.complaint || .........................checked ok....................
|-
| print castle resource taxIncome ( m_city.cityManager.castle.resource.taxIncome ) || cityManager.castle.resource.taxIncome || .........................checked ok....................
|-
| print gold ( m_city.cityManager.estResource.gold ) || cityManager.estResource.gold || .........................checked ok....................
|-
| print food ( m_city.cityManager.estResource.food ) || cityManager.estResource.food || .........................checked ok....................
|-
| print wood ( m_city.cityManager.estResource.wood ) || cityManager.estResource.wood || .........................checked ok....................
|-
| print stone ( m_city.cityManager.estResource.stone ) || cityManager.estResource.stone || .........................checked ok....................
|-
| print iron ( m_city.cityManager.estResource.iron ) || cityManager.estResource.iron || .........................checked ok....................
|-
| print ( m_city.cityManager.ResourceProduction.food ) || cityManager.ResourceProduction.food || .........................checked ok....................
|-
| print ( m_city.cityManager.ResourceProduction.wood ) || cityManager.ResourceProduction.wood || .........................checked ok....................
|-
| print ( m_city.cityManager.ResourceProduction.stone ) || cityManager.ResourceProduction.stone || .........................checked ok....................
|-
| print ( m_city.cityManager.ResourceProduction.iron ) || cityManager.ResourceProduction.iron || .........................checked ok....................
|-
! // Fields || ||
|-
| print fields[0] id: ( m_city.cityManager.fields[0].id ) || cityManager.fields[0].id ) || .........................checked ok....................
|-
| print fields[0] level: ( m_city.cityManager.fields[0].level ) || cityManager.fields[0].level ) || .........................checked ok....................
|-
| print fields[0] name: ( m_city.cityManager.fields[0].name ) || cityManager.fields[0].name ) || .........................checked ok....................
|-
| print fields[0] type: ( m_city.cityManager.fields[0].type ) || cityManager.fields[0].type ) || .........................checked ok....................
|-
| print fields[1] id: ( m_city.cityManager.fields[1].id ) || cityManager.fields[1].id ) || .........................checked ok....................
|-
| print fields[1] level: ( m_city.cityManager.fields[1].level ) || cityManager.fields[1].level ) || .........................checked ok....................
|-
| print fields[1] name: ( m_city.cityManager.fields[1].name ) || cityManager.fields[1].name ) || .........................checked ok....................
|-
| print fields[1] type: ( m_city.cityManager.fields[1].type ) || cityManager.fields[1].type ) || .........................checked ok....................
|-
| print –fields length------- m_city.cityManager.fields.length || cityManager.fields.length || .........................checked ok....................
|-
| print –fields 9 type------- m_city.cityManager.fields[9].type || cityManager.fields[9].type || .........................checked ok....................
|-
| print fieldId ( m_city.cityManager.fieldId ) || cityManager.fieldId || .........................checked ok....................
|-
! // Hero || ||
|-
| print AnyIdleHero(any): ( m_city.AnyIdleHero(any) ) || AnyIdleHero(any) ) || .........................checked ok....................
|-
| print m_city.cityManager.TrainingHeroIsHere || cityManager.TrainingHeroIsHere || .........................checked ok....................
|-
| print AnyIdleHero(Queen): ( m_city.AnyIdleHero(Queen) ) || AnyIdleHero(Queen) ) || .........................checked ok....................
|-
| print IsHeroInCastle(Queen): ( m_city.IsHeroInCastle(Queen) ) || IsHeroInCastle(Queen) ) || .........................checked ok....................
|-
| print heros[0] logoUrl: ( m_city.cityManager.heroes[0].logoUrl ) || cityManager.heroes[0].logoUrl ) || .........................checked ok....................
|-
| print heros[0] id: ( m_city.cityManager.heroes[0].id ) || cityManager.heroes[0].id ) || .........................checked ok....................
|-
| print heros[0] name: ( m_city.cityManager.heroes[0].name ) || cityManager.heroes[0].name ) || .........................checked ok....................
|-
| print heros[0] level: ( m_city.cityManager.heroes[0].level ) || cityManager.heroes[0].level ) || .........................checked ok....................
|-
| print heros[0] experience: ( m_city.cityManager.heroes[0].experience ) || cityManager.heroes[0].experience ) || .........................checked ok....................
|-
| print heros[0] loyalty: ( m_city.cityManager.heroes[0].loyalty ) || cityManager.heroes[0].loyalty ) || .........................checked ok....................
|-
| print heros[0] power: ( m_city.cityManager.heroes[0].power ) || cityManager.heroes[0].power ) || .........................checked ok....................
|-
| print heros[0] stratagem: ( m_city.cityManager.heroes[0].stratagem ) || cityManager.heroes[0].stratagem ) || .........................checked ok....................
|-
| print heros[0] management: ( m_city.cityManager.heroes[0].management ) || cityManager.heroes[0].management ) || .........................checked ok....................
|-
| print heros[0] itemId: ( m_city.cityManager.heroes[0].itemId ) || cityManager.heroes[0].itemId ) || .........................checked ok....................
|-
| print heros[0] itemAmount: ( m_city.cityManager.heroes[0].itemAmount ) || cityManager.heroes[0].itemAmount ) || .........................checked ok....................
|-
| print heros[0] managementAdded: ( m_city.cityManager.heroes[0].managementAdded ) || cityManager.heroes[0].managementAdded ) || .........................checked ok....................
|-
| print heros[0] managementBuffAdded: ( m_city.cityManager.heroes[0].managementBuffAdded ) || cityManager.heroes[0].managementBuffAdded ) || .........................checked ok....................
|-
| print heros[0] powerAdded: ( m_city.cityManager.heroes[0].powerAdded ) || cityManager.heroes[0].powerAdded ) || .........................checked ok....................
|-
| print heros[0] powerBuffAdded: ( m_city.cityManager.heroes[0].powerBuffAdded ) || cityManager.heroes[0].powerBuffAdded ) || .........................checked ok....................
|-
| print heros[0] stratagemAdded: ( m_city.cityManager.heroes[0].stratagemAdded ) || cityManager.heroes[0].stratagemAdded ) || .........................checked ok....................
|-
| print heros[0] stratagemBuffAdded: ( m_city.cityManager.heroes[0].stratagemBuffAdded ) || cityManager.heroes[0].stratagemBuffAdded ) || .........................checked ok....................
|-
| print heros[0] upgradeExp: ( m_city.cityManager.heroes[0].upgradeExp ) || cityManager.heroes[0].upgradeExp ) || .........................checked ok....................
|-
| print heros[0] remainPoint: ( m_city.cityManager.heroes[0].remainPoint ) || cityManager.heroes[0].remainPoint ) || .........................checked ok....................
|-
| print heros[1] logoUrl: ( m_city.cityManager.heroes[1].logoUrl ) || cityManager.heroes[1].logoUrl ) || .........................checked ok....................
|-
| print heros[1] id: ( m_city.cityManager.heroes[1].id ) || cityManager.heroes[1].id ) || .........................checked ok....................
|-
| print heros[1] name: ( m_city.cityManager.heroes[1].name ) || cityManager.heroes[1].name ) || .........................checked ok....................
|-
| print heros[1] level: ( m_city.cityManager.heroes[1].level ) || cityManager.heroes[1].level ) || .........................checked ok....................
|-
| print heros[1] experience: ( m_city.cityManager.heroes[1].experience ) || cityManager.heroes[1].experience ) || .........................checked ok....................
|-
| print heros[1] loyalty: ( m_city.cityManager.heroes[1].loyalty ) || cityManager.heroes[1].loyalty ) || .........................checked ok....................
|-
| print heros[1] power: ( m_city.cityManager.heroes[1].power ) || cityManager.heroes[1].power ) || .........................checked ok....................
|-
| print heros[1] stratagem: ( m_city.cityManager.heroes[1].stratagem ) || cityManager.heroes[1].stratagem ) || .........................checked ok....................
|-
| print heros[1] management: ( m_city.cityManager.heroes[1].management ) || cityManager.heroes[1].management ) || .........................checked ok....................
|-
| print heros[1] itemId: ( m_city.cityManager.heroes[1].itemId ) || cityManager.heroes[1].itemId ) || .........................checked ok....................
|-
| print heros[1] itemAmount: ( m_city.cityManager.heroes[1].itemAmount ) || cityManager.heroes[1].itemAmount ) || .........................checked ok....................
|-
| print heros[1] managementAdded: ( m_city.cityManager.heroes[1].managementAdded ) || cityManager.heroes[1].managementAdded ) || .........................checked ok....................
|-
| print heros[1] managementBuffAdded: ( m_city.cityManager.heroes[1].managementBuffAdded ) || cityManager.heroes[1].managementBuffAdded ) || .........................checked ok....................
|-
| print heros[1] powerAdded: ( m_city.cityManager.heroes[1].powerAdded ) || cityManager.heroes[1].powerAdded ) || .........................checked ok....................
|-
| print heros[1] powerBuffAdded: ( m_city.cityManager.heroes[1].powerBuffAdded ) || cityManager.heroes[1].powerBuffAdded ) || .........................checked ok....................
|-
| print heros[1] stratagemAdded: ( m_city.cityManager.heroes[1].stratagemAdded ) || cityManager.heroes[1].stratagemAdded ) || .........................checked ok....................
|-
| print heros[1] stratagemBuffAdded: ( m_city.cityManager.heroes[1].stratagemBuffAdded ) || cityManager.heroes[1].stratagemBuffAdded ) || .........................checked ok....................
|-
| print heros[1] upgradeExp: ( m_city.cityManager.heroes[1].upgradeExp ) || cityManager.heroes[1].upgradeExp ) || .........................checked ok....................
|-
| print heros[1] remainPoint: ( m_city.cityManager.heroes[1].remainPoint ) || cityManager.heroes[1].remainPoint ) || .........................checked ok....................
|-
| print –heroes length------- m_city.cityManager.heroes.length || cityManager.heroes.length || .........................checked ok....................
|-
| print –heroes status------- m_city.cityManager.heroes[0].status || cityManager.heroes[0].status || .........................checked ok....................
|-
| print m_city.cityManager.TrainingHeroIsHere || cityManager.TrainingHeroIsHer || .........................checked ok....................
|-
| print length ( m_city.cityManager.innHeroes.length ) || cityManager.innHeroes.length || Do not understand results
|-
| print status ( m_city.cityManager.innHeroes[0].status ) || cityManager.innHeroes[0].status || Do not understand results
|-
| print name ( m_city.cityManager.innHeroes[0].name ) || cityManager.innHeroes[0].name || Do not understand results
|-
| print management ( m_city.cityManager.innHeroes[0].management ) || cityManager.innHeroes[0].management || Do not understand results
|-
| print stratagemBuffAdded ( m_city.cityManager.innHeroes[0].stratagemBuffAdded ) || cityManager.innHeroes[0].stratagemBuffAdded || Do not understand results
|-
| print managementBuffAdded ( m_city.cityManager.innHeroes[0].managementBuffAdded ) || cityManager.innHeroes[0].managementBuffAdded || Do not understand results
|-
| print powerBuffAdded ( m_city.cityManager.innHeroes[0].powerBuffAdded ) || cityManager.innHeroes[0].powerBuffAdded || Do not understand results
|-
| print power ( m_city.cityManager.innHeroes[0].power ) || cityManager.innHeroes[0].power || Do not understand results
|-
| print level ( m_city.cityManager.innHeroes[0].level ) || cityManager.innHeroes[0].level || Do not understand results
|-
| print managementAdded ( m_city.cityManager.innHeroes[0].managementAdded ) || cityManager.innHeroes[0].managementAdded || Do not understand results
|-
| print id ( m_city.cityManager.innHeroes[0].id ) || cityManager.innHeroes[0].id || Do not understand results
|-
| print buffsArray ( m_city.cityManager.innHeroes[0].buffsArray ) || cityManager.innHeroes[0].buffsArray || Do not understand results
|-
| print upgradeExp ( m_city.cityManager.innHeroes[0].upgradeExp ) || cityManager.innHeroes[0].upgradeExp || Do not understand results
|-
| print powerAdded ( m_city.cityManager.innHeroes[0].powerAdded ) || cityManager.innHeroes[0].powerAdded || Do not understand results
|-
| print remainPoint ( m_city.cityManager.innHeroes[0].remainPoint ) || cityManager.innHeroes[0].remainPoint || Do not understand results
|-
| print logoUrl ( m_city.cityManager.innHeroes[0].logoUrl ) || cityManager.innHeroes[0].logoUrl || Do not understand results
|-
| print stratagemAdded ( m_city.cityManager.innHeroes[0].stratagemAdded ) || cityManager.innHeroes[0].stratagemAdded || Do not understand results
|-
| print itemId ( m_city.cityManager.innHeroes[0].itemId ) || cityManager.innHeroes[0].itemId || Do not understand results
|-
| print itemAmount ( m_city.cityManager.innHeroes[0].itemAmount ) || cityManager.innHeroes[0].itemAmount || Do not understand results
|-
| print stratagem ( m_city.cityManager.innHeroes[0].stratagem ) || cityManager.innHeroes[0].stratagem || Do not understand results
|-
| print loyalty ( m_city.cityManager.innHeroes[0].loyalty ) || cityManager.innHeroes[0].loyalty || Do not understand results
|-
! // Troop || ||
|-
| print troop archer: ( m_city.cityManager.troop.archer ) || cityManager.troop.archer ) || .........................checked ok....................
|-
| print troop ballista: ( m_city.cityManager.troop.ballista ) || cityManager.troop.ballista ) || .........................checked ok....................
|-
| print troop batteringRam: ( m_city.cityManager.troop.batteringRam ) || cityManager.troop.batteringRam ) || .........................checked ok....................
|-
| print troop carriage: ( m_city.cityManager.troop.carriage ) || cityManager.troop.carriage ) || .........................checked ok....................
|-
| print troop catapult: ( m_city.cityManager.troop.catapult ) || cityManager.troop.catapult ) || .........................checked ok....................
|-
| print troop heavyCavalry: ( m_city.cityManager.troop.heavyCavalry ) || cityManager.troop.heavyCavalry ) || .........................checked ok....................
|-
| print troop lightCavalry: ( m_city.cityManager.troop.lightCavalry ) || cityManager.troop.lightCavalry ) || .........................checked ok....................
|-
| print troop militia: ( m_city.cityManager.troop.militia ) || cityManager.troop.militia ) || .........................checked ok....................
|-
| print troop peasants: ( m_city.cityManager.troop.peasants ) || cityManager.troop.peasants ) || .........................checked ok....................
|-
| print troop pikemen: ( m_city.cityManager.troop.pikemen ) || cityManager.troop.pikemen ) || .........................checked ok....................
|-
| print troop scouter: ( m_city.cityManager.troop.scouter ) || cityManager.troop.scouter ) || .........................checked ok....................
|-
| print troop swordsmen: ( m_city.cityManager.troop.swordsmen ) || cityManager.troop.swordsmen ) || .........................checked ok....................
|-
| print archer ( m_city.cityManager.troopStillInProduction.archer ) || cityManager.troopStillInProduction.archer ) || .........................checked ok....................
|-
| print ballista ( m_city.cityManager.troopStillInProduction.ballista ) || cityManager.troopStillInProduction.ballista ) || .........................checked ok....................
|-
| print batteringRam ( m_city.cityManager.troopStillInProduction.batteringRam ) || cityManager.troopStillInProduction.batteringRam ) || .........................checked ok....................
|-
| print carriage ( m_city.cityManager.troopStillInProduction.carriage ) || cityManager.troopStillInProduction.carriage ) || .........................checked ok....................
|-
| print catapult ( m_city.cityManager.troopStillInProduction.catapult ) || cityManager.troopStillInProduction.catapult ) || .........................checked ok....................
|-
| print heavyCavalry ( m_city.cityManager.troopStillInProduction.heavyCavalry ) || cityManager.troopStillInProduction.heavyCavalry ) || .........................checked ok....................
|-
| print lightCavalry ( m_city.cityManager.troopStillInProduction.lightCavalry ) || cityManager.troopStillInProduction.lightCavalry ) || .........................checked ok....................
|-
| print militia ( m_city.cityManager.troopStillInProduction.militia ) || cityManager.troopStillInProduction.militia ) || .........................checked ok....................
|-
| print peasants ( m_city.cityManager.troopStillInProduction.peasants ) || cityManager.troopStillInProduction.peasants ) || .........................checked ok....................
|-
| print pikemen ( m_city.cityManager.troopStillInProduction.pikemen ) || cityManager.troopStillInProduction.pikemen ) || .........................checked ok....................
|-
| print scouter ( m_city.cityManager.troopStillInProduction.scouter ) || cityManager.troopStillInProduction.scouter ) || .........................checked ok....................
|-
! // Forts || ||
|-
| print fortification abatis: ( m_city.cityManager.fortification.abatis ) || cityManager.fortification.abatis ) || .........................checked ok....................
|-
| print fortification arrowTower: ( m_city.cityManager.fortification.arrowTower ) || cityManager.fortification.arrowTower ) || .........................checked ok....................
|-
| print fortification rockfall: ( m_city.cityManager.fortification.rockfall ) || cityManager.fortification.rockfall ) || .........................checked ok....................
|-
| print fortification rollingLogs: ( m_city.cityManager.fortification.rollingLogs ) || cityManager.fortification.rollingLogs ) || .........................checked ok....................
|-
| print fortification trap: ( m_city.cityManager.fortification.trap ) || cityManager.fortification.trap ) || .........................checked ok....................
|-
| print trap ( m_city.cityManager.fortificationsRequirement.trap ) || cityManager.fortificationsRequirement.trap ) || .........................checked ok....................
|-
| print arrowTower ( m_city.cityManager.fortificationsRequirement.arrowTower ) || cityManager.fortificationsRequirement.arrowTower ) || .........................checked ok....................
|-
| print rockfall ( m_city.cityManager.fortificationsRequirement.rockfall ) || cityManager.fortificationsRequirement.rockfall ) || .........................checked ok....................
|-
| print rollingLogs ( m_city.cityManager.fortificationsRequirement.rollingLogs ) || cityManager.fortificationsRequirement.rollingLogs ) || .........................checked ok....................
|-
| print abatis ( m_city.cityManager.fortificationsRequirement.abatis ) || cityManager.fortificationsRequirement.abatis ) || .........................checked ok....................
|-
! // Buildings || ||
|-
| print buildings[0]: ( m_city.cityManager.buildings[0] ) || cityManager.buildings[0] ) || .........................checked ok....................
|-
| print buildings[0] endTime: ( m_city.cityManager.buildings[0].endTime ) || cityManager.buildings[0].endTime ) || .........................checked ok....................
|-
| print buildings[0] level: ( m_city.cityManager.buildings[0].level ) || cityManager.buildings[0].level ) || .........................checked ok....................
|-
| print buildings[0] name: ( m_city.cityManager.buildings[0].name ) || cityManager.buildings[0].name ) || .........................checked ok....................
|-
| print buildings[0] positionId: ( m_city.cityManager.buildings[0].positionId ) || cityManager.buildings[0].positionId ) || .........................checked ok....................
|-
| print buildings[0] startTime: ( m_city.cityManager.buildings[0].startTime ) || cityManager.buildings[0].startTime ) || .........................checked ok....................
|-
| print buildings[0] status: ( m_city.cityManager.buildings[0].status ) || cityManager.buildings[0].status ) || .........................checked ok....................
|-
| print buildings[0] typeId: ( m_city.cityManager.buildings[0].typeId ) || cityManager.buildings[0].typeId ) || .........................checked ok....................
|-
| print buildings[1]: ( m_city.cityManager.buildings[1] ) || cityManager.buildings[1] ) || .........................checked ok....................
|-
| print buildings[1] endTime: ( m_city.cityManager.buildings[1].endTime ) || cityManager.buildings[1].endTime ) || .........................checked ok....................
|-
| print buildings[1] level: ( m_city.cityManager.buildings[1].level ) || cityManager.buildings[1].level ) || .........................checked ok....................
|-
| print buildings[1] name: ( m_city.cityManager.buildings[1].name ) || cityManager.buildings[1].name ) || .........................checked ok....................
|-
| print buildings[1] positionId: ( m_city.cityManager.buildings[1].positionId ) || cityManager.buildings[1].positionId ) || .........................checked ok....................
|-
| print buildings[1] startTime: ( m_city.cityManager.buildings[1].startTime ) || cityManager.buildings[1].startTime ) || .........................checked ok....................
|-
| print buildings[1] status: ( m_city.cityManager.buildings[1].status ) || cityManager.buildings[1].status ) || .........................checked ok....................
|-
| print buildings[1] typeId: ( m_city.cityManager.buildings[1].typeId ) || cityManager.buildings[1].typeId ) || .........................checked ok....................
|-
| print –Buildings 73 level------- m_city.cityManager.buildings[73].level || cityManager.buildings[73].level || .........................checked ok....................
|-
| print buildings length ( m_city.cityManager.buildings.length ) || cityManager.buildings.length || .........................checked ok....................
|-
! // Market || ||
|-
| print –buyPrice------- m_city.cityManager.buyPrice() || cityManager.buyPrice() || .........................checked ok....................
|-
| print –buyPrice------- m_city.cityManager.buyPrice(1) || cityManager.buyPrice(1) || .........................checked ok....................
|-
| print –buyPrice 2------- m_city.cityManager.buyPrice(2) || cityManager.buyPrice(2) || .........................checked ok....................
|-
| print –buyPrice 3------- m_city.cityManager.buyPrice(3) || cityManager.buyPrice(3) || .........................checked ok....................
|-
| print –sellPrice food------- m_city.cityManager.sellPrice(food) || cityManager.sellPrice(food) || .........................checked ok....................
|-
| print –tradesArray length------- m_city.cityManager.tradesArray.length || cityManager.tradesArray.length || .........................checked ok....................
|-
| print –tradesArray 0 amount------- m_city.cityManager.tradesArray[0].amount || cityManager.tradesArray[0].amount || .........................checked ok....................
|-
| print –tradesArray 1 amount------- m_city.cityManager.tradesArray[1].amount || cityManager.tradesArray[1].amount || .........................checked ok....................
|-
| print –tradesArray 2 amount------- m_city.cityManager.tradesArray[2].amount || cityManager.tradesArray[2].amount || .........................checked ok....................
|-
| print –tradesArray 6 amount------- m_city.cityManager.tradesArray[6].amount || cityManager.tradesArray[6].amount || .........................checked ok....................
|-
| print m_city.cityManager.tradesArray[0].resType || cityManager.tradesArray[0].resType || .........................checked ok....................
|-
| print m_city.cityManager.tradesArray[0].tradeType || cityManager.tradesArray[0].tradeType || .........................checked ok....................
|-
| print tradesArray 0 resourceName ( m_city.cityManager.tradesArray[0].resourceName ) || cityManager.tradesArray[0].resourceName || .........................checked ok....................
|-
| print tradesArray 0 price ( m_city.cityManager.tradesArray[0].price ) || cityManager.tradesArray[0].price || .........................checked ok....................
|-
| print tradesArray 0 id ( m_city.cityManager.tradesArray[0].id ) || cityManager.tradesArray[0].id || .........................checked ok....................
|-
| print tradesArray 0 tradeTypeName ( m_city.cityManager.tradesArray[0].tradeTypeName ) || cityManager.tradesArray[0].tradeTypeName || .........................checked ok....................
|-
| print tradesArray 0 dealedAmount ( m_city.cityManager.tradesArray[0].dealedAmount ) || cityManager.tradesArray[0].dealedAmount || .........................checked ok....................
|-
| print tradesArray 0 dealedTotal ( m_city.cityManager.tradesArray[0].dealedTotal ) || cityManager.tradesArray[0].dealedTotal || .........................checked ok....................
|-
| print transingTradesArray length ( m_city.cityManager.transingTradesArray.length ) || cityManager.transingTradesArray.length || .........................checked ok....................
|-
| print transingTradesArray 0 amount ( m_city.cityManager.transingTradesArray[0].amount ) || cityManager.transingTradesArray[0].amount || .........................checked ok....................
|-
| print transingTradesArray 0 endTime ( m_city.cityManager.transingTradesArray[0].endTime ) || cityManager.transingTradesArray[0].endTime || .........................checked ok....................
|-
| print transingTradesArray 0 resourceName ( m_city.cityManager.transingTradesArray[0].resourceName ) || cityManager.transingTradesArray[0].resourceName || .........................checked ok....................
|-
| print transingTradesArray 0 price ( m_city.cityManager.transingTradesArray[0].price ) || cityManager.transingTradesArray[0].price || .........................checked ok....................
|-
| print transingTradesArray 0 total ( m_city.cityManager.transingTradesArray[0].total ) || cityManager.transingTradesArray[0].total || .........................checked ok....................
|-
| print transingTradesArray 0 id ( m_city.cityManager.transingTradesArray[0].id ) || cityManager.transingTradesArray[0].id || .........................checked ok....................
|-
| print transingTradesArray 0 resType ( m_city.cityManager.transingTradesArray[0].resType ) || cityManager.transingTradesArray[0].resType || .........................checked ok....................
|-
| print sellPrice 0 ( m_context.sellPrice(0) ) || m_context.sellPrice(0) || .........................checked ok....................
|-
| print buyPrice 0 ( m_context.buyPrice(0) ) || m_context.buyPrice(0) || .........................checked ok....................
|-
| print sellPrice 1 ( m_context.sellPrice(1) ) || m_context.sellPrice(1) || .........................checked ok....................
|-
| print buyPrice 1 ( m_context.buyPrice(1) ) || m_context.buyPrice(1) || .........................checked ok....................
|-
| print sellPrice 2 ( m_context.sellPrice(2) ) || m_context.sellPrice(2) || .........................checked ok....................
|-
| print buyPrice 2 ( m_context.buyPrice(2) ) || m_context.buyPrice(2) || .........................checked ok....................
|-
| print sellPrice 3 ( m_context.sellPrice(3) ) || m_context.sellPrice(3) || .........................checked ok....................
|-
| print buyPrice 3 ( m_context.buyPrice(3) ) || m_context.buyPrice(3) || .........................checked ok....................
|-
! // Armies || ||
|-
| print –selfArmies length------- m_city.cityManager.selfArmies.length || cityManager.selfArmies.length || .........................checked ok....................
|-
| print –selfArmies 0 missionType ( m_city.cityManager.selfArmies[0].missionType ) || cityManager.selfArmies[0].missionType || .........................checked ok....................
|-
| print –selfArmies 0 king ( m_city.cityManager.selfArmies[0].king ) || cityManager.selfArmies[0].king || .........................checked ok....................
|-
| print –selfArmies 0 startFieldId ( m_city.cityManager.selfArmies[0].startFieldId ) || cityManager.selfArmies[0].startFieldId || .........................checked ok....................
|-
| print –selfArmies 0 targetPosName ( m_city.cityManager.selfArmies[0].targetPosName ) || cityManager.selfArmies[0].targetPosName || .........................checked ok....................
|-
| print –selfArmies 0 direction ( m_city.cityManager.selfArmies[0].direction ) || cityManager.selfArmies[0].direction || .........................checked ok....................
|-
| print –selfArmies 0 restTime ( m_city.cityManager.selfArmies[0].restTime ) || cityManager.selfArmies[0].restTime || .........................checked ok....................
|-
| print –selfArmies 0 startTime ( m_city.cityManager.selfArmies[0].startTime ) || cityManager.selfArmies[0].startTime || .........................checked ok....................
|-
| print –selfArmies 0 startPosName ( m_city.cityManager.selfArmies[0].startPosName ) || cityManager.selfArmies[0].startPosName || .........................checked ok....................
|-
| print –selfArmies 0 heroLevel ( m_city.cityManager.selfArmies[0].heroLevel ) || cityManager.selfArmies[0].heroLevel || .........................checked ok....................
|-
| print –selfArmies 0 reachTime ( m_city.cityManager.selfArmies[0].reachTime ) || cityManager.selfArmies[0].reachTime || .........................checked ok....................
|-
| print –selfArmies 0 hero ( m_city.cityManager.selfArmies[0].hero ) || cityManager.selfArmies[0].hero || .........................checked ok....................
|-
| print –selfArmies 0 targetFieldId ( m_city.cityManager.selfArmies[0].targetFieldId ) || cityManager.selfArmies[0].targetFieldId || .........................checked ok....................
|-
| print –selfArmies 0 alliance ( m_city.cityManager.selfArmies[0].alliance ) || cityManager.selfArmies[0].alliance || .........................checked ok....................
|-
| print –selfArmies 0 troop peasant------- m_city.cityManager.selfArmies[0].troop.peasants || cityManager.selfArmies[0].troop.peasants || .........................checked ok....................
|-
| print –selfArmies 0 troop militia------- m_city.cityManager.selfArmies[0].troop.militia || cityManager.selfArmies[0].troop.militia || .........................checked ok....................
|-
| print –selfArmies 0 troop scouter------- m_city.cityManager.selfArmies[0].troop.scouter || cityManager.selfArmies[0].troop.scouter || .........................checked ok....................
|-
| print –selfArmies 0 troop pikemen------- m_city.cityManager.selfArmies[0].troop.pikemen || cityManager.selfArmies[0].troop.pikemen || .........................checked ok....................
|-
| print –selfArmies 0 troop swordsmen------- m_city.cityManager.selfArmies[0].troop.swordsmen || cityManager.selfArmies[0].troop.swordsmen || .........................checked ok....................
|-
| print –selfArmies 0 troop archer------- m_city.cityManager.selfArmies[0].troop.archer || cityManager.selfArmies[0].troop.archer || .........................checked ok....................
|-
| print –selfArmies 0 troop lightCavalry------- m_city.cityManager.selfArmies[0].troop.lightCavalry || cityManager.selfArmies[0].troop.lightCavalry || .........................checked ok....................
|-
| print –selfArmies 0 troop heavyCavalry------- m_city.cityManager.selfArmies[0].troop.heavyCavalry || cityManager.selfArmies[0].troop.heavyCavalry || .........................checked ok....................
|-
| print –selfArmies 0 troop carriage------- m_city.cityManager.selfArmies[0].troop.carriage || cityManager.selfArmies[0].troop.carriage || .........................checked ok....................
|-
| print –selfArmies 0 troop ballista------- m_city.cityManager.selfArmies[0].troop.ballista || cityManager.selfArmies[0].troop.ballista || .........................checked ok....................
|-
| print –selfArmies troop batteringRam------- m_city.cityManager.selfArmies[0].troop.batteringRam || cityManager.selfArmies[0].troop.batteringRam || .........................checked ok....................
|-
| print –selfArmies troop catapult------- m_city.cityManager.selfArmies[0].troop.catapult || cityManager.selfArmies[0].troop.catapult || .........................checked ok....................
|-
| Print gold ( m_city.cityManager.selfArmies[0].resource.gold ) || cityManager.selfArmies[0].resource.gold || .........................checked ok....................
|-
| Print food ( m_city.cityManager.selfArmies[0].resource.food ) || cityManager.selfArmies[0].resource.food || .........................checked ok....................
|-
| Print wood ( m_city.cityManager.selfArmies[0].resource.wood ) || cityManager.selfArmies[0].resource.wood || .........................checked ok....................
|-
| Print iron ( m_city.cityManager.selfArmies[0].resource.iron ) || cityManager.selfArmies[0].resource.iron || .........................checked ok....................
|-
| print 0-----------------------------------stone ( m_city.cityManager.selfArmies[0].resource.stone ) || cityManager.selfArmies[0].resource.stone || .........................checked ok....................
|-
| print castle goOutForBattle ( m_city.cityManager.castle.goOutForBattle ) || cityManager.castle.goOutForBattle || .........................checked ok....................
|-
| print missionType ( m_city.cityManager.friendlyArmies[0].missionType ) || cityManager.friendlyArmies[0].missionType ) || .........................checked ok....................
|-
| print king ( m_city.cityManager.friendlyArmies[0].king ) || cityManager.friendlyArmies[0].king ) || .........................checked ok....................
|-
| print startFieldId ( m_city.cityManager.friendlyArmies[0].startFieldId ) || cityManager.friendlyArmies[0].startFieldId ) || .........................checked ok....................
|-
| print targetPosName ( m_city.cityManager.friendlyArmies[0].targetPosName ) || cityManager.friendlyArmies[0].targetPosName ) || .........................checked ok....................
|-
| print direction ( m_city.cityManager.friendlyArmies[0].direction ) || cityManager.friendlyArmies[0].direction ) || .........................checked ok....................
|-
| print restTime ( m_city.cityManager.friendlyArmies[0].restTime ) || cityManager.friendlyArmies[0].restTime ) || .........................checked ok....................
|-
| print startTime ( m_city.cityManager.friendlyArmies[0].startTime ) || cityManager.friendlyArmies[0].startTime ) || .........................checked ok....................
|-
| print startPosName ( m_city.cityManager.friendlyArmies[0].startPosName ) || cityManager.friendlyArmies[0].startPosName ) || .........................checked ok....................
|-
| print heroLevel ( m_city.cityManager.friendlyArmies[0].heroLevel ) || cityManager.friendlyArmies[0].heroLevel ) || .........................checked ok....................
|-
| print reachTime ( m_city.cityManager.friendlyArmies[0].reachTime ) || cityManager.friendlyArmies[0].reachTime ) || .........................checked ok....................
|-
| print hero ( m_city.cityManager.friendlyArmies[0].hero ) || cityManager.friendlyArmies[0].hero ) || .........................checked ok....................
|-
| print targetFieldId ( m_city.cityManager.friendlyArmies[0].targetFieldId ) || cityManager.friendlyArmies[0].targetFieldId ) || .........................checked ok....................
|-
| print alliance ( m_city.cityManager.friendlyArmies[0].alliance ) || cityManager.friendlyArmies[0].alliance ) || .........................checked ok....................
|-
| print trooppeasants ( m_city.cityManager.friendlyArmies[0].troop.peasants ) || cityManager.friendlyArmies[0].troop.peasants ) || .........................checked ok....................
|-
| print troopmilitia ( m_city.cityManager.friendlyArmies[0].troop.militia ) || cityManager.friendlyArmies[0].troop.militia ) || .........................checked ok....................
|-
| print troopscouter ( m_city.cityManager.friendlyArmies[0].troop.scouter ) || cityManager.friendlyArmies[0].troop.scouter ) || .........................checked ok....................
|-
| print trooppikemen ( m_city.cityManager.friendlyArmies[0].troop.pikemen ) || cityManager.friendlyArmies[0].troop.pikemen ) || .........................checked ok....................
|-
| print troopswordsmen ( m_city.cityManager.friendlyArmies[0].troop.swordsmen ) || cityManager.friendlyArmies[0].troop.swordsmen ) || .........................checked ok....................
|-
| print trooparcher ( m_city.cityManager.friendlyArmies[0].troop.archer ) || cityManager.friendlyArmies[0].troop.archer ) || .........................checked ok....................
|-
| print trooplightCavalry ( m_city.cityManager.friendlyArmies[0].troop.lightCavalry ) || cityManager.friendlyArmies[0].troop.lightCavalry ) || .........................checked ok....................
|-
| print troopheavyCavalry ( m_city.cityManager.friendlyArmies[0].troop.heavyCavalry ) || cityManager.friendlyArmies[0].troop.heavyCavalry ) || .........................checked ok....................
|-
| print troopcarriage ( m_city.cityManager.friendlyArmies[0].troop.carriage ) || cityManager.friendlyArmies[0].troop.carriage ) || .........................checked ok....................
|-
| print troopballista ( m_city.cityManager.friendlyArmies[0].troop.ballista ) || cityManager.friendlyArmies[0].troop.ballista ) || .........................checked ok....................
|-
| print troopbatteringRam ( m_city.cityManager.friendlyArmies[0].troop.batteringRam ) || cityManager.friendlyArmies[0].troop.batteringRam ) || .........................checked ok....................
|-
| print troopcatapult ( m_city.cityManager.friendlyArmies[0].troop.catapult ) || cityManager.friendlyArmies[0].troop.catapult ) || .........................checked ok....................
|-
| print resourcegold ( m_city.cityManager.friendlyArmies[0].resource.gold ) || cityManager.friendlyArmies[0].resource.gold ) || .........................checked ok....................
|-
| print resourcefood ( m_city.cityManager.friendlyArmies[0].resource.food ) || cityManager.friendlyArmies[0].resource.food ) || .........................checked ok....................
|-
| print resourcewood ( m_city.cityManager.friendlyArmies[0].resource.wood ) || cityManager.friendlyArmies[0].resource.wood ) || .........................checked ok....................
|-
| print resourceiron ( m_city.cityManager.friendlyArmies[0].resource.iron ) || cityManager.friendlyArmies[0].resource.iron ) || .........................checked ok....................
|-
| print resourcestone ( m_city.cityManager.friendlyArmies[0].resource.stone ) || cityManager.friendlyArmies[0].resource.stone ) || .........................checked ok....................
|-
| print estResource food: ( m_city.cityManager.estResource.food ) || cityManager.estResource.food || .........................checked ok....................
|-
| print estResource gold: ( m_city.cityManager.estResource.gold ) || cityManager.estResource.gold || .........................checked ok....................
|-
| print estResource iron: ( m_city.cityManager.estResource.iron ) || cityManager.estResource.iron || .........................checked ok....................
|-
| print estResource stone: ( m_city.cityManager.estResource.stone ) || cityManager.estResource.stone || .........................checked ok....................
|-
| print reservedResource food: ( m_city.cityManager.reservedResource.food ) || cityManager.reservedResource.food || .........................checked ok....................
|-
| print reservedResource gold: ( m_city.cityManager.reservedResource.gold ) || cityManager.reservedResource.gold || .........................checked ok....................
|-
| print reservedResource iron: ( m_city.cityManager.reservedResource.iron ) || cityManager.reservedResource.iron || .........................checked ok....................
|-
| print reservedResource stone: ( m_city.cityManager.reservedResource.stone ) || cityManager.reservedResource.stone || .........................checked ok....................
|-
! // General || ||
|-
| print id: ( m_city.cityManager.id ) || cityManager.id ) || .........................checked ok....................
|-
| print name: ( m_city.cityManager.name ) || cityManager.name ) || .........................checked ok....................
|-
| print –heros Queen stratagem------- m_city.cityManager.heros(Queen).stratagem || cityManager.heros(Queen).stratagem || line 231 Invalid Reference: m_city.cityManager.heros(Queen).stratagem Error #1069
|-
| Print timeSlot ( m_city.cityManager.timeSlot ) // int; || m_city.cityManager.timeSlot || .........................checked ok....................
|-
| Print directionChange ( m_city.cityManager.directionChange ) // Boolean = false; || m_city.cityManager.directionChange || .........................checked ok....................
|-
| Print furtherInitNeeded ( m_city.cityManager.furtherInitNeeded ) // Boolean = true; || m_city.cityManager.furtherInitNeeded || .........................checked ok....................
|-
| Print mapInitState ( m_city.cityManager.mapInitState ) // int; // 0 - ok, 1 - pending, 2 - init needed || m_city.cityManager.mapInitState || .........................checked ok....................
|-
| Print checkFeastingHallSpace ( m_city.cityManager.checkFeastingHallSpace ) // Boolean; || m_city.cityManager.checkFeastingHallSpace || .........................checked ok....................
|-
| Print innStatus ( m_city.cityManager.innStatus ) // int; || m_city.cityManager.innStatus || .........................checked ok....................
|-
| Print troopQueueStatus ( m_city.cityManager.troopQueueStatus ) // int; || m_city.cityManager.troopQueueStatus || .........................checked ok....................
|-
| Print fortificationQueueStatus ( m_city.cityManager.fortificationQueueStatus ) // int; || m_city.cityManager.fortificationQueueStatus || .........................checked ok....................
|-
| Print pendingProductionRates ( m_city.cityManager.pendingProductionRates ) // Array = new Array; || m_city.cityManager.pendingProductionRates || .........................checked ok....................
|-
| Print distanceSettings ( m_city.cityManager.distanceSettings ) // Array = new Array(0, 0, 0, 0, 0); || m_city.cityManager.distanceSettings || .........................checked ok....................
|-
| print name ( m_city.cityManager.name ) || cityManager.name || .........................checked ok....................
|-
| print castle allowAlliance ( m_city.cityManager.castle.allowAlliance ) || cityManager.castle.allowAlliance || .........................checked ok....................
|-
| print id ( m_city.cityManager.id ) || cityManager.id || .........................checked ok....................
|-
| print Player currentTime ( m_context.Player.currentTime ) || m_context.Player.currentTime || .........................checked ok....................
|-
| print serverMinutes ( m_context.serverMinutes ) || m_context.serverMinutes || .........................checked ok....................
|-
| print serverHours ( m_context.serverHours ) || m_context.serverHours || .........................checked ok....................
|-
| print serverDate ( m_context.serverDate ) || m_context.serverDate || .........................checked ok....................
|-
| print serverMonth ( m_context.serverMonth ) || m_context.serverMonth || .........................checked ok....................
|-
| print serverYear ( m_context.serverYear ) || m_context.serverYear || .........................checked ok....................
|-
| print Player currentDateTime ( m_context.Player.currentDateTime ) || m_context.Player.currentDateTime || .........................checked ok....................
|-
| print Player currentTime ( m_context.Player.currentTime ) || m_context.Player.currentTime || .........................checked ok....................
|-
| print Player playerInfo lastLoginTime ( m_context.Player.playerInfo.lastLoginTime ) || m_context.Player.playerInfo.lastLoginTime || .........................checked ok....................
|-
| print Player playerInfo createrTime ( m_context.Player.playerInfo.createrTime ) || m_context.Player.playerInfo.createrTime || .........................checked ok....................
|-
| print Player playerInfo office ( m_context.Player.playerInfo.office ) || m_context.Player.playerInfo.office || .........................checked ok....................
|-
| print Player playerInfo castleCount ( m_context.Player.playerInfo.castleCount ) || m_context.Player.playerInfo.castleCount || .........................checked ok....................
|-
| print Player playerInfo honor ( m_context.Player.playerInfo.honor ) || m_context.Player.playerInfo.honor || .........................checked ok....................
|-
| print Player playerInfo levelId ( m_context.Player.playerInfo.levelId ) || m_context.Player.playerInfo.levelId || .........................checked ok....................
|-
| print Player playerInfo medal ( m_context.Player.playerInfo.medal ) || m_context.Player.playerInfo.medal || .........................checked ok....................
|-
| print Player playerInfo sex ( m_context.Player.playerInfo.sex ) || m_context.Player.playerInfo.sex || .........................checked ok....................
|-
| print Player playerInfo accountName ( m_context.Player.playerInfo.accountName ) || m_context.Player.playerInfo.accountName || .........................checked ok....................
|-
| print Player playerInfo faceUrl ( m_context.Player.playerInfo.faceUrl ) || m_context.Player.playerInfo.faceUrl || .........................checked ok....................
|-
| print Player playerInfo id ( m_context.Player.playerInfo.id ) || m_context.Player.playerInfo.id || .........................checked ok....................
|-
| print Player playerInfo allianceLevel ( m_context.Player.playerInfo.allianceLevel ) || m_context.Player.playerInfo.allianceLevel || .........................checked ok....................
|-
| print Player playerInfo bdenyotherplayer ( m_context.Player.playerInfo.bdenyotherplayer ) || m_context.Player.playerInfo.bdenyotherplayer || .........................checked ok....................
|-
| print Player playerInfo population ( m_context.Player.playerInfo.population ) || m_context.Player.playerInfo.population || .........................checked ok....................
|-
| print Player playerInfo flag ( m_context.Player.playerInfo.flag ) || m_context.Player.playerInfo.flag || .........................checked ok....................
|-
| print Player playerInfo prestige ( m_context.Player.playerInfo.prestige ) || m_context.Player.playerInfo.prestige || .........................checked ok....................
|-
| print Player playerInfo userName ( m_context.Player.playerInfo.userName ) || m_context.Player.playerInfo.userName || .........................checked ok....................
|-
| print Player playerInfo userId ( m_context.Player.playerInfo.userId ) || m_context.Player.playerInfo.userId || .........................checked ok....................
|-
| print Player playerInfo titleId ( m_context.Player.playerInfo.titleId ) || m_context.Player.playerInfo.titleId || .........................checked ok....................
|-
| print Player playerInfo ranking ( m_context.Player.playerInfo.ranking ) || m_context.Player.playerInfo.ranking || .........................checked ok....................
|-
| print Player playerInfo alliance ( m_context.Player.playerInfo.alliance ) || m_context.Player.playerInfo.alliance || .........................checked ok....................
|-
| print m_city.cityManager.distanceSettings[0] || cityManager.distanceSettings[0 || .........................checked ok....................
|-
| print m_city.cityManager.distanceSettings[1] || cityManager.distanceSettings[1 || .........................checked ok....................
|-
| print m_city.cityManager.distanceSettings[2] || cityManager.distanceSettings[2 || .........................checked ok....................
|-
| print m_city.cityManager.distanceSettings[3] || cityManager.distanceSettings[3 || .........................checked ok....................
|-
| print m_city.cityManager.distanceSettings[4] || cityManager.distanceSettings[4 || .........................checked ok....................
|-
| print ( m_context.maintenanceStart ) || m_context.maintenanceStar || .........................checked ok....................
|-
| print m_city.cityManager.CityHasGoalErrors || cityManager.CityHasGoalError || .........................checked ok....................
|-
| print m_city.cityManager.GateControl || cityManager.GateContro || .........................checked ok....................
|-
| print m_city.cityManager.trainingHeroName || cityManager.trainingHeroNam || .........................checked ok....................
|-
! // Research || ||
|-
| print avalevel ( m_city.cityManager.researches[0].avalevel ) || cityManager.researches[0].avalevel || .........................checked ok....................
|-
| print endTime ( m_city.cityManager.researches[0].endTime ) || cityManager.researches[0].endTime || .........................checked ok....................
|-
| print upgradeing ( m_city.cityManager.researches[0].upgradeing ) || cityManager.researches[0].upgradeing || .........................checked ok....................
|-
| print level ( m_city.cityManager.researches[0].level ) || cityManager.researches[0].level || .........................checked ok....................
|-
| print startTime ( m_city.cityManager.researches[0].startTime ) || cityManager.researches[0].startTime || .........................checked ok....................
|-
| print castleId ( m_city.cityManager.researches[0].castleId ) || cityManager.researches[0].castleId || .........................checked ok....................
|-
| print typeId ( m_city.cityManager.researches[0].typeId ) || cityManager.researches[0].typeId || .........................checked ok....................
|-
| print permition ( m_city.cityManager.researches[0].permition ) || cityManager.researches[0].permition || .........................checked ok....................
|-
| print m_city.cityManager.isSafeFarming || cityManager.isSafeFarmin || .........................checked ok....................
|}

Contact Us

2012-08-19T15:49:56Z

Inanna:

If you need help with your bot, you can contact us...

----

'''On the forums at'''

[http://forum.neatportal.com/ http://forum.neatportal.com/]

Hero Goals

2012-08-16T23:37:27Z

Inanna: /* HeroString */

==Hero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config hero:[switch]
|-
! style="text-align:left;" | Example:
|
config hero:10
|-
! style="text-align:left;" | Switch:
|
0 - Disable Hero Management 
1 - Level up & reward heroes only 
10 - Hire 1 good Politics hero all other attack heroes 
11 - Hire 1 good Politics and 1 good Intel hero all others attack heroes 
12 - Hire 1 good Politics and 2 good Intel heroes all others attack heroes 
20 - Hire 2 good Politics heroes all others attack heroes 
21 - Hire 2 good Politics and 1 good Intel hero all others attack heroes 
22 - Hire 2 good Politics and 2 good Intel heroes all others attack heroes
|}

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 10+ in order for fasthero to function.

 

==Fasthero==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config fasthero:[base]
|-
! style="text-align:left;" | 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 base 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+ base politics hero and the rest 65+ base attack heroes. Having a level 1 inn in the city is recommended for this goal to save gold.

A hero may be fired if it's base stat is lower than fasthero setting AND it's level is lower than herofirelimit setting. When selecting which hero to fire, the bot will only choose from idle heroes. This means a better hero may be fired if a worse one is off farming.

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.

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.

 

==HeroString==

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,

valleyheroes Biggy ''this would allow only hero Biggy to attack valleys & flats'' 
npcheroes any,!Smarty,!Biggy ''this would allow any hero except Smarty and except Biggy to hit npcs'' 
npcheroes 10 Biggy,Polly,Smarty ''this would allow heroes Biggy, Polly, and Smarty to hit npc10s'' 
reinforce 123,456 none c:100000 ''this would allow you to reinforce 123,456 with cav but not to include a hero''

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,

valleyheroes any:attack>180 ''this would allow any hero with an attack over 180 to attack valleys & flats'' 
valleyheroes any:politics<200 ''this would allow any hero with politics under 200 to attack valleys & flats'' 
npcheroes 8 any:politics=best ''this would allow the best politics hero to hit npc8s'' 
npcheroes 10 any:attack>300,base>60 ''this would allow any attack hero with both an attack over 300 AND a base over 60 to hit npc10s'' 
attack 111,222 !Biggy,any:attack>180 c:99k,s:1k ''this would attack coordinates 111,222 with any hero over 180 attack other than hero Biggy with 99k cavs, 1k scouts'' 
attack 111,222 !Polly,any:attack<100 w:5k ''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,

npcheroes 5 any:base>60 
npcheroes 5 any:attack<300

The above lines mean that npc5s can be farmed with any hero that has greater than 60 base, OR any hero that has less than 300 attack. Multiple lines can be concatenated into a single line with the | symbol. For example,

npcheroes 5 any:base>60|any:attack<300

The above line means exactly the same thing as the 2 before it.

npcheroes 5 any:base>60,attack<300

If you were to instead use the line above, it would mean npc5s can be farmed with any hero that has both greater than 60 base, AND is less than 300 attack.

All possible filters for use in hero strings are:

attack or att 
politics or pol 
intel or int 
loyalty or loy 
level or lvl 
experience or exp 
points or pts 
base or bse 

All possible comparisons to use in filters are:

< (less than) 
> (greater than) 
= (equal to) 
!= (not equal to) 
<> (not equal to) 
<= (less than or equal to) 
>= (greater than or equal to)

"Best" and "Worst" can be used in place of values for comparisons, example:

npcheroes 10 any:attack=best ''would allow npc10s to be farmed with the best attack hero.'' 
npcheroes 5 any:attack<best ''would allow npc5s to be farmed with any hero lower than the best attack hero.''

Stats can be compared to other stats in place of values, example:

npcheroes 5 any:attack>politics ''would allow any hero with an attack score greater than it's politics score.''
npcheroes 5 any:politics>level ''would allow any hero with a politics score greater than it's level.''

Wildcards can be used for the hero list. * will represent 1 or more characters, ? will represent 1 character. For example,

npcheroes 5 att*:attack>200 ''would allow npc5s to be farmed with any hero over 200 attack that has att in it's name.'' 
npcheroes 5 *:base>60 ''would allow npc5s to be farmed with any hero that has a base over 60.''

When using attributes as conditions, the bot will consider buffs as part of the value. For example, an attack hero with an unbuffed 100 attack and excaliber applied would be treated as a 125 attack hero in hero selection. Expiration time of buffs is not taken into account for an attack. Make sure your excaliber isn't going to run out before you smack that npc10 with a little hero ;)

 

==Npcheroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| npcheroes [optional level] hero-string
|-
! style="text-align:left;" | Example:
|
npcheroes 10 hero-string 
npcheroes 9 hero-string 
npcheroes 5 hero-string 
npcheroes 4 hero-string 
npcheroes hero-string
|}

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.

See [[Hero_Goals#HeroString|Hero String]] for details on how to setup the hero string for this goal.

NOTE: You must still enable farming of these levels of npcs via the [[NPC_Goals#Npc|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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| npc10heroes hero-string
|-
! style="text-align:left;" | Example:
|
npc10heroes hero-string
|}

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.

See [[Hero_Goals#HeroString|Hero String]] for details on how to setup the hero string for this goal.

NOTE: You must still enable farming of level 10 npcs via the [[NPC_Goals#Npc10limit|npc10limit]] goal. Simply setting which heroes to use will not make the bot hit level 10 npcs.

 

==Valleyheroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| valleyheroes hero-string
|-
! style="text-align:left;" | Example:
|
valleyheroes AttackDude,ValleyGuy
|}

This directive will tell the bot which heroes it may or may not use to acquire flats for holding or npc building, as well as heroes for valley acquisition, hunting, valleyfarming, and safevalleyfarming. In the example above, only the heroes named AttackDude and ValleyGuy would be allowed to perform any march against a valley or flat.

Another example, using advanced hero strings: ''valleyheroes !trainingheroname,any:attack>60''. This would allow any hero with 60+ attack other than the traininghero. I've found safevalleyfarm will often lose troops if a politics or intel hero with very low attack are sent. Since adding this to my goals, I have no more losses on safevalleyfarming and much lower losses on everything else.

See [[Hero_Goals#HeroString|Hero String]] for details on how to setup the hero string for this goal. 

 

==Training==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config training:[switch]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config training10:[switch]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config trainpol:[switch]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config trainint:[switch]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config keepatthome:[switch]
|-
! style="text-align:left;" | 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 highest attack hero home in the city for defensive purposes.

 

==Feastinghallspace==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config feastinghallspace:[spaces]
|-
! style="text-align:left;" | 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.

Note - if you're running this goal alongside fasthero, fasthero will reserve these spaces in addition to a space for the traininghero.
 

==Nomayor==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config nomayor:[switch]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| homeheroes [amount]
|-
! style="text-align:left;" | 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 [[Hero_Goals#Npcheroes|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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| traininghero heroname [[minstay [maxstay [npchits]]]
|-
! style="text-align:left;" | Example:
|
traininghero BigGuy 
traininghero BigGuy 120 
traininghero BigGuy 120 2400 10
|}

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.

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.

The traininghero will farm npcs level 1-5 if the city is configured to farm them, unless he is told not to. You can exclude the traininghero from farming those npcs by adding or modifying the [[Hero_Goals#npcheroes|npcheroes]] goal:
<pre>
npcheroes !BigGuy,any
or
npcheroes 5 !BigGuy,any
</pre>

In the absense of any traininghero goal for a city, the best attack score hero in that city will be used as the traininghero.

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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| spamheroes hero-string
|-
! style="text-align:left;" | Example:
|
spamheroes hero-string
|}

This directive will tell the bot which heroes it may or may not use with [[Deployment_Scripts#LoyaltyAttack|loyaltyattack]] or [[Deployment_Scripts#SpamAttack|spamattack]].

See [[Hero_Goals#HeroString|Hero String]] for details on how to setup the hero string for this goal.

 

==Nolevelheroes==

{| class="wikitable"
! style="text-align:left;" | Usage:
| nolevelheroes hero-string
|-
! style="text-align:left;" | 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 increased persuasion costs and requirements. Setting this will allow ForBob to gain experience without being levelled up by the bot.

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. :)

 

==Herofirelimit==

{| class="wikitable"
! style="text-align:left;" | Usage:
| herofirelimit [level]
|-
! style="text-align:left;" | 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==

{| class="wikitable"
! style="text-align:left;" | Usage:
| capturedfirelimit [level]
|-
! style="text-align:left;" | Example:
|
capturedfirelimit 100
|}

This directive will tell the bot not to automatically fire any captured hero of the level specified.

A) you have config hero set to something other than 0 (eg. config hero:1) ...''' AND'''

B) you have a captured hero of a level below the capturedfirelimit ... '''AND'''

C) the captured hero is the lowest attack ... '''OR''' 
D) the feasting hall is full and the traininghero is not in the city

General Goals

2012-08-16T23:03:37Z

Inanna: /* Extrafood */

=Main City Goals=

The bot will recognize your oldest city as your main city. The one with an asterix (*) by the name is the main city. There are a few config settings that are only placed in the main city.

 

==ResetFarmingHistoryOnStartup==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config resetfarminghistoryonstartup:[switch]
|-
! style="text-align:left;" | Example:
|
config resetfarminghistoryonstartup:1
|}

This goal will tell the bot to reset it's farming history, and begin again anew, each time you restart the bot. By default the bot will remember where it left off in the farming cycle when it's restarted.

 

==Schedulepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| schedulepolicy start_time end_time [start_time end_time start_time end_time]
|-
! style="text-align:left;" | Example:
|
schedulepolicy 06:00 12:00
|}
This policy will tell the bot to start and stop performing actions during certain times of the day. In the example above, the bot would run from 6 to 12, and stop the rest of the time. You can add multiple start and end times to this policy, eg: schedulepolicy 06:00 12:00 17:00 23:00.

 

=Every City Goals=

 

==ProcessingPolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| processignpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy-list
|-
! style="text-align:left;" | Example:
|
processingpolicy t b r a n 
processingpolicy buildnpc valleyacquisition npcfarming 
processingpolicy /start:13:00:00 /end:13:59:59 medalhunting
|-
! style="text-align:left;" | 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 order in which it will perform it's functions. 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. 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. 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 use of ! is also allowed to deny a certain process from happening, eg: ''processingpolicy /start:13:00:00 /end:13:59:59 !medalhunting'' to disallow medal farming between 1PM and 2PM.

 

==Comfort==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config comfort:[switch]
|-
! style="text-align:left;" | Example:
|
config comfort:1
|}
Enable the comfort goal and the bot will automagiclly perform comforting on your city as it is required.
This goal along with config gate:[time], config hiding:[time], config npc:[level] all working together can make it so your cities are virtually impossible to capture.
With comforting activated the bot will raise loyalty, reduce grievance, adjust tax rates to prevent riots, and perform misc. comforting actions as specified in compfortpolicy. This goal is required in order to use comfortpolicy.

 

==Comfortpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| comfortpolicy min_time max_time [options]
|-
! style="text-align:left;" | Example:
|
comfortpolicy 15 20 popraise pray
|-
! style="text-align:left;" | Arguements:
|
gold, go 
stone, st 
iron, ir 
food, fo 
wood, lumber, wo, lu 
popraise, po 
bless, bl 
pray, pr 
relief, dr 
|}
This policy will tell the bot to, in the example above, perform population raising if needed every 15-20 minutes, and if not needed then pray every 15-20 minutes. You may include any levying or comforting option in this, eg: ''comfortpolicy 15 20 popraise food pray'', to have the bot perform population raising if needed every 15-20 minutes, and if not then levy food every 15-20 minutes and follow with a prayer every 15-20 minutes.

Multiple types of resources can be listed for levying, it will cycle through them each time.
 

==Distancepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| distancepolicy npc_farming npc_building medal_farming valley_capturing map_scanning
|-
! style="text-align:left;" | Example:
|
distancepolicy 10 20 5 25 25
|}
This policy will tell the bot how far, in miles, it may go from your city to perform these actions in order. This number must be a whole number between 5 and 50.

The valley capturing distance also specifies how far the bot may go to [[Valley_Goals#SafeValleyFarm|farm valleys safely]].

 

==Rallypolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| rallypolicy policytype:[level:]:maximumslots [policytype:[level:]:maximumslots]
|-
! style="text-align:left;" | Example:
|
rallypolicy n:10:1 n:8 v:1
|-
! style="text-align:left;" | Arguments:
|
n = npc farming 
b = buildnpc 
v = valleyfarming 
m = medal hunting 
t = troop transfer 
r = resource transfer (non-emergency) 
a = valley acquisition 
|}

This policy will allow you to instruct the bot how many of each mission can be done at the rally. This does not reserve rally spots for these tasks, it merely limits how many it can do at one time. Rallypolicy counts both returning and marching missions in it's total.

You could, for example, do ''rallypolicy n:10:1 n:6 v:5 b:2'', which would instruct your bot that it may use up to 1 slot for npc10s, 6 slots total for npcs (which would count the npc10 as one of them), 5 slots for valley farming/medal hunting, and 2 slots for npc building. You won't need a lvl 13 rally spot for this to work. Whichever task is performed first can use UP TO that many slots, then the next task will use UP TO it's limit or the rally spot limit, so on and so forth until your rally spots are all in use, the rallypolicy limit is reached for every task, or your tasks are all in progress.

 

==Taxpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| taxpolicy min_rate max_rate
|-
! style="text-align:left;" | Example:
|
taxpolicy 20 100
|}
This policy will tell the bot the range of tax you want set. The example above would maintain a minimum 20% tax rate and 100% maximum rate. If the bot detects that additional gold is necessary to prevent a revolt, it will increase the tax rate as necessary, up to "max_rate". The default values are 0 (min) and 100 (max). A default of 0 (min) allows the bot to maintain maximum population. Players with established accounts will probably wish to use the defaults.

 

==Nohealing==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config nohealing:[switch]
|-
! style="text-align:left;" | Example:
|
config nohealing:1
|}

When this goal is turned on, it will tell your bot that you do not want it to heal injured troops in the medic camp.

 

==ReportsToKeep==

{| class="wikitable"
! style="text-align:left;" | Usage:
| reportstokeep <nowiki>items(0|1)</nowiki> valley.HighLoss npc5.HighLoss npc10.LowLoss npc10.HighLoss
|-
! style="text-align:left;" | Example:
|
reportstokeep 1 a:500 b:1 a:3800 a:6000
|}

This directive will tell the bot which reports you want it to keep. In the above example, any report with a treasure acquired will be kept because the first number is set to "1". Any valley attack report will be kept if the archers lost in it are 500 or more. Any npc5 attack report will be kept if 1 or more ballista are lost. Any npc10 report will be kept if the archers lost are lower than 3.8k or higher than 6k. All other reports will be read and deleted by the bot. You can set these numbers to 0 in order to have it keep every report, eg: reportstokeep 1 a:0 b:0 a:0 a:0.

 

==Excludelist==

{| class="wikitable"
! style="text-align:left;" | Usage:
| excludelist coord1 coord2 [...] coordX
|-
! style="text-align:left;" | Example:
|
excludelist 111,222 111,333 111,444
|}

This directive will tell the bot to exclude anything at those coordinates. No npc farming runs, valley acquisition runs, valley farming runs, npc building missions, or flat acquisition runs will be sent to these coordinates. This single goal can (and in the future will completely) replace [[General_Goals#NoAbandonFlats|noabandonflats]], [[NPC_Goals#Npcexcludelist|npcexcludelist]], and [[NPC_Goals#Npc10excludelist|npc10excludelist]].

 

==NoAbandonFlats==

{| class="wikitable"
! style="text-align:left;" | Usage:
| noabandonflats flat1 flat2 [...] flatX
|-
! style="text-align:left;" | Example:
|
noabandonflats 111,222 111,333 111,444
|}

This directive is now obsolete. Please use [[General_Goals#Excludelist|excludelist]] instead.

 

==Abandon==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config abandon:[switch]
|-
! style="text-align:left;" | Example:
|
config abandon:1
|}

This goal tells the bot that you are planning to abandon this city. The bot will destroy all troops, wall defenses, and queues in the city and will lower loyalty by levying and adjusting the tax rate upwards. The bot will not perform comforting actions on the city with this goal set. This is useful when you plan to give a city away or abandon it. The bot will not automatically abandon the city once it reaches 0 loyalty.

WARNING!!! You should run [[City_Scripts#evacuatetown | evacuatetown]] in the scripts window before you set this goal!

General Goals

2012-08-16T22:09:25Z

Inanna: /* Maintenance */

=Main City Goals=

The bot will recognize your oldest city as your main city. The one with an asterix (*) by the name is the main city. There are a few config settings that are only placed in the main city.

 

==ResetFarmingHistoryOnStartup==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config resetfarminghistoryonstartup:[switch]
|-
! style="text-align:left;" | Example:
|
config resetfarminghistoryonstartup:1
|}

This goal will tell the bot to reset it's farming history, and begin again anew, each time you restart the bot. By default the bot will remember where it left off in the farming cycle when it's restarted.

 

==Schedulepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| schedulepolicy start_time end_time [start_time end_time start_time end_time]
|-
! style="text-align:left;" | Example:
|
schedulepolicy 06:00 12:00
|}
This policy will tell the bot to start and stop performing actions during certain times of the day. In the example above, the bot would run from 6 to 12, and stop the rest of the time. You can add multiple start and end times to this policy, eg: schedulepolicy 06:00 12:00 17:00 23:00.

 

=Every City Goals=

 

==ProcessingPolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| processignpolicy [/start:hh:mm[:ss] [/end:hh:mm[:ss]] policy-list
|-
! style="text-align:left;" | Example:
|
processingpolicy t b r a n 
processingpolicy buildnpc valleyacquisition npcfarming 
processingpolicy /start:13:00:00 /end:13:59:59 medalhunting
|-
! style="text-align:left;" | 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 order in which it will perform it's functions. 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. 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. 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 use of ! is also allowed to deny a certain process from happening, eg: ''processingpolicy /start:13:00:00 /end:13:59:59 !medalhunting'' to disallow medal farming between 1PM and 2PM.

 

==Comfort==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config comfort:[switch]
|-
! style="text-align:left;" | Example:
|
config comfort:1
|}
Enable the comfort goal and the bot will automagiclly perform comforting on your city as it is required.
This goal along with config gate:[time], config hiding:[time], config npc:[level] all working together can make it so your cities are virtually impossible to capture.
With comforting activated the bot will raise loyalty, reduce grievance, adjust tax rates to prevent riots, and perform misc. comforting actions as specified in compfortpolicy. This goal is required in order to use comfortpolicy.

 

==Comfortpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| comfortpolicy min_time max_time [options]
|-
! style="text-align:left;" | Example:
|
comfortpolicy 15 20 popraise pray
|-
! style="text-align:left;" | Arguements:
|
gold, go 
stone, st 
iron, ir 
food, fo 
wood, lumber, wo, lu 
popraise, po 
bless, bl 
pray, pr 
relief, dr 
|}
This policy will tell the bot to, in the example above, perform population raising if needed every 15-20 minutes, and if not needed then pray every 15-20 minutes. You may include any levying or comforting option in this, eg: ''comfortpolicy 15 20 popraise food pray'', to have the bot perform population raising if needed every 15-20 minutes, and if not then levy food every 15-20 minutes and follow with a prayer every 15-20 minutes.

Multiple types of resources can be listed for levying, it will cycle through them each time.
 

==Distancepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| distancepolicy npc_farming npc_building medal_farming valley_capturing map_scanning
|-
! style="text-align:left;" | Example:
|
distancepolicy 10 20 5 25 25
|}
This policy will tell the bot how far, in miles, it may go from your city to perform these actions in order. This number must be a whole number between 5 and 50.

The valley capturing distance also specifies how far the bot may go to [[Valley_Goals#SafeValleyFarm|farm valleys safely]].

 

==Rallypolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| rallypolicy policytype:[level:]:maximumslots [policytype:[level:]:maximumslots]
|-
! style="text-align:left;" | Example:
|
rallypolicy n:10:1 n:8 v:1
|-
! style="text-align:left;" | Arguments:
|
n = npc farming 
b = buildnpc 
v = valleyfarming 
m = medal hunting 
t = troop transfer 
r = resource transfer (non-emergency) 
a = valley acquisition 
|}

This policy will allow you to instruct the bot how many of each mission can be done at the rally. This does not reserve rally spots for these tasks, it merely limits how many it can do at one time. Rallypolicy counts both returning and marching missions in it's total.

You could, for example, do ''rallypolicy n:10:1 n:6 v:5 b:2'', which would instruct your bot that it may use up to 1 slot for npc10s, 6 slots total for npcs (which would count the npc10 as one of them), 5 slots for valley farming/medal hunting, and 2 slots for npc building. You won't need a lvl 13 rally spot for this to work. Whichever task is performed first can use UP TO that many slots, then the next task will use UP TO it's limit or the rally spot limit, so on and so forth until your rally spots are all in use, the rallypolicy limit is reached for every task, or your tasks are all in progress.

 

==Taxpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| taxpolicy min_rate max_rate
|-
! style="text-align:left;" | Example:
|
taxpolicy 20 100
|}
This policy will tell the bot the range of tax you want set. The example above would maintain a minimum 20% tax rate and 100% maximum rate. If the bot detects that additional gold is necessary to prevent a revolt, it will increase the tax rate as necessary, up to "max_rate". The default values are 0 (min) and 100 (max). A default of 0 (min) allows the bot to maintain maximum population. Players with established accounts will probably wish to use the defaults.

 

==Extrafood==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config extrafood:[days]
|-
! style="text-align:left;" | Example:
|
config extrafood:5
|}

By default the bot will attempt to keep 1 day worth of food for each city, but you can change this amount with this goal. The bot will not queue troops, queue wall fortifications, or sell food if it would bring it below this number of days. Less than 1 day is also possible, eg: config extrafood:0.5.

This goal is removed in rev1847 and later.

 

==Nohealing==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config nohealing:[switch]
|-
! style="text-align:left;" | Example:
|
config nohealing:1
|}

When this goal is turned on, it will tell your bot that you do not want it to heal injured troops in the medic camp.

 

==ReportsToKeep==

{| class="wikitable"
! style="text-align:left;" | Usage:
| reportstokeep <nowiki>items(0|1)</nowiki> valley.HighLoss npc5.HighLoss npc10.LowLoss npc10.HighLoss
|-
! style="text-align:left;" | Example:
|
reportstokeep 1 a:500 b:1 a:3800 a:6000
|}

This directive will tell the bot which reports you want it to keep. In the above example, any report with a treasure acquired will be kept because the first number is set to "1". Any valley attack report will be kept if the archers lost in it are 500 or more. Any npc5 attack report will be kept if 1 or more ballista are lost. Any npc10 report will be kept if the archers lost are lower than 3.8k or higher than 6k. All other reports will be read and deleted by the bot. You can set these numbers to 0 in order to have it keep every report, eg: reportstokeep 1 a:0 b:0 a:0 a:0.

 

==Excludelist==

{| class="wikitable"
! style="text-align:left;" | Usage:
| excludelist coord1 coord2 [...] coordX
|-
! style="text-align:left;" | Example:
|
excludelist 111,222 111,333 111,444
|}

This directive will tell the bot to exclude anything at those coordinates. No npc farming runs, valley acquisition runs, valley farming runs, npc building missions, or flat acquisition runs will be sent to these coordinates. This single goal can (and in the future will completely) replace [[General_Goals#NoAbandonFlats|noabandonflats]], [[NPC_Goals#Npcexcludelist|npcexcludelist]], and [[NPC_Goals#Npc10excludelist|npc10excludelist]].

 

==NoAbandonFlats==

{| class="wikitable"
! style="text-align:left;" | Usage:
| noabandonflats flat1 flat2 [...] flatX
|-
! style="text-align:left;" | Example:
|
noabandonflats 111,222 111,333 111,444
|}

This directive is now obsolete. Please use [[General_Goals#Excludelist|excludelist]] instead.

 

==Abandon==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config abandon:[switch]
|-
! style="text-align:left;" | Example:
|
config abandon:1
|}

This goal tells the bot that you are planning to abandon this city. The bot will destroy all troops, wall defenses, and queues in the city and will lower loyalty by levying and adjusting the tax rate upwards. The bot will not perform comforting actions on the city with this goal set. This is useful when you plan to give a city away or abandon it. The bot will not automatically abandon the city once it reaches 0 loyalty.

WARNING!!! You should run [[City_Scripts#evacuatetown | evacuatetown]] in the scripts window before you set this goal!

Main Page

2012-08-16T11:18:13Z

Inanna:

'''NeatBot is an Evony helper.'''

* NeatBot can build npcs for you, and do your npc farming.
* NeatBot can manage your heroes for you.
* NeatBot can queue troops for you.
* NeatBot can acquire, farm, and hunt medals for you from valleys.
* NeatBot can manage your resources via market trading and shipping them city to city.
* NeatBot can build your city and do your research for you on new accounts.
* NeatBot has powerful defensive features for your city such as comforting, defensepolicy, and gatecontrol...
* NeatBot can build fortifications for defense on your walls.

'''NeatBot is not a replacement for you.'''

* NeatBot cannot decide what is the best defense for your city.
* NeatBot cannot do what you forget to tell it to do.
* NeatBot cannot fix your poorly written goals or scripts to prevent you from doing something stupid.
* NeatBot cannot teach you how to use itself, please read the forums/guide.
* NeatBot cannot teach you game mechanics or make you a good player, it just gives you the foundation to be able to be that.
* NeatBot cannot ever be as good as you - so don't forget to PLAY your account in between all the botting.

----
'''''Disclaimer by Inanna'''''

This wiki is, quite obviously, used from sources ranging as far back as Evobot's Wiki and as recent as YAEB's Wiki (which I also wrote). No infringement upon anyone's copywrites or intellectual property is intended. YAEB was branched from the AutoEvony project, AutoEvony came from Evobot, and I'm sure in the future some other bot will be taken from NeatBot. Such is the way of the internet. Thank you to all who came in the past to bring this bot and this wiki into the present, and will take it into the future. Credit freely given where credit is due.

Captcha Setup

2012-08-16T11:15:47Z

Inanna: Replaced content with " = Captcha Pricing Chart = = Setup Your Bot to Autosolve Captchas ="

= Captcha Pricing Chart =

 

= Setup Your Bot to Autosolve Captchas =

Global Settings

2012-08-16T11:15:05Z

Inanna: Replaced content with "When You click on this button a sperate dialogue box will open with 5 separate configurable settings ==Map Colors== ==Log Colors== ==Auto Use Items== ==..."

When You click on this button a sperate dialogue box will open with 5 separate configurable settings

==Map Colors==

 

==Log Colors==

 

==Auto Use Items==

 

==Misc==

 

==Captcha==

 

==Binary==

 

==About==

Mac App Setup

2012-08-16T11:12:35Z

Inanna: Replaced content with "=Basic Setup= =Advanced Tips= =Mac OSX Binary Manager= ==Basic Setup== ==Usage== ==Comments=="

=Basic Setup=

=Advanced Tips=

=Mac OSX Binary Manager=

==Basic Setup==

==Usage==
==Comments==

Mac App Setup

2012-08-16T11:12:03Z

Inanna: /* Basic Setup */

=Basic Setup=

=Advanced Tips=

'''Thank you to DarioJames for this guide!'''

So you do not want to have multiple copies of the YAEB.app but want to run multiple instances?

How you ask?

I will tell you a method.

Open up Terminal. Application > Utilities > Terminal. 
[[File:Mac_bot_7.png|700px]]

Enter an open command. e.g. open /path/to/your/bot/YAEB.app --args -u your_info@your_email.net -s 158. The --args argument passes the rest of the options on to the YAEB.app. 
[[File:Mac_bot_8.png|700px]]

To run another instance you need on use the -n argument of the open command. e.g. open /path/to/your/bot/YAEB.app -n --args -u your_info_for_2nd_bot@your_email.net -s 158. 
[[File:Mac_bot_9.png|700px]]

Those of you who are script savy should be able to figure out how to make a pseudo instance manager for at least starting up your bots.

=Mac OSX Binary Manager=

'''Thank you to Dismayed for this guide and Qualan for the open source Mac OSX Binary Manager'''

You can find the download for this open source Manager at: https://github.com/mquinnv/Java-Binary-Manager 
You can find the forum post for help with this Manager at: http://forum.duelingelectrons.com/viewtopic.php?f=13&t=11607

''YAEB did not create this program, but can attest that we have had no complaints about it killing their mothers or eating their dogs from users. As always with third party programs, use at your own risk.''

==Basic Setup==

To begin, download the latest version of YAEB Mac OSX .app bot from the forum. You can save this anywhere you like - I have installed it like this:

[[File:Mac_setup_1.png|700px]]

Now download the Mac Binary Manager linked above.

[[File:Mac_setup_2.png|700px]]

Click on the Downloads, and download a zip.

[[File:Mac_setup_3.png|700px]]

Copy the download to your YAEB application directory

[[File:Mac_setup_4.png|700px]]

Now unpack the archive

[[File:Mac_setup_5.png|700px]]

For convenience I copied the app into main directory and closed the branches and i looks like this

[[File:Mac_setup_6.png|700px]]

Thats it, you have the Mac Manager.

==Usage==

Each time that download a new version of the YAEB.app you will need to run it direct - e.g. Double Click on YAEB.app above. This will pause and will bring up the usual message that you are running an application from the internet - click ok and close.
If you do not do this every instance that the Mac Binary Manager opens will come up with the same message.

Now run the Binary Manager.app

[[File:Mac_setup_7.png|700px]]

I have clicked Change and selected the YAEB.app and added 3 accounts.

As you can see the first Combo Box is for Groups. My usual Groups are: 
Group 1 - Mine 
Group 2 - Friends 
Group 3 - Alliance 
For this demo I have created a group - YAEB WIKI

Execute by selecting an account - or many accounts - and click start button which will bring up the YAEB login screen/screens.

==Comments==

YAEB (on my machine) saves its login data in: 
Macintosh HD/
Users/
MyUserName/
Library/
Preferences/
Macromedia/
Flash Player/
#SharedObjects/
9748QH3Q/
localhost/
#YAEB/
server name

Clearing Cache and Cookies does not delete these files.
I have not been able to find where the Binary Manager saves its data,clearing cache and cookies retains the groups and the login names but does not retain the information of login and password. Result - clear cache and cookies - you will need to enter the login info but having sdone so then your cities goals will still be there.

Windows Setup

2012-08-16T11:11:11Z

Inanna: /* FAQ for the Manager and Director */

== Setup ==

 

 

== Binary Director ==

You can find a nice video tutorial on the official website for the director here: http://sumrandomguy.com/

 

 

== Binary Manager ==

 

 

== FAQ for the Manager and Director ==

'''Q: What are the Binary Manager and Director? Are they bots?'''

A ''binary'' is just a program compiled to run on your computer... NeatBot.exe is a binary - or binary bot, as we like to call it. Both the Binary Manager and the Binary Director are programs that will allow you to setup profiles for each binary bot you would normally run. With these profiles you can start, stop, restart, and even set the bots to auto-run. The Manager/Director itself is not a bot, you will need to download the binary bot also.

'''Q: Is the Binary Manager or Director required to use the binary bots?'''

No. You are free to run and use the bots without either of them, but if you run multiple accounts or servers, this will be very helpful to you. If you're not going to use the Manager or Director, you should keep a seperate folder for each account and/or server, so that when you run the NeatBot.exe you will not have to type in the login details each time. If using the Manager or Director, you're able to keep only 1 folder for all accounts to share.

'''Q: Can I use the Binary Manager or Director on my Linux or Mac OSX machine?'''

No. At this time they only work for Windows operating systems. You should be able to emulate it with WINE or similar Windows emulators on another OS. The menu links to your left will take you to a guide for setting up multiple bots with Mac OSX written by DarioJames.

'''Q: What is .NET Framework 4 and why do I need it?'''

If you're getting a message from the Binary Manager that it needs .NET Framework 4 installed, go to [http://www.microsoft.com/download/en/details.aspx?id=17851 http://www.microsoft.com/download/en/details.aspx?id=17851] and download it. The Manager needs the files from that in order to run on your computer. The Binary Director will not need these files.

'''Q: How do I update the Manager or Director? Or the bots I use with it?'''

This is super easy and why they are a great idea to use with multiple accounts. For the Manager or Director, download the new version and drop it into the folder where the old one is, allow the new version to overwrite the old one, restart it. For the Manager only you can also opt to run the auto-updater to allow it to download the updates for you. Future versions of the Manager are planned to update themselves automatically.

To update to a new NeatBot.exe, download the new version, shutdown all your currently running bots, and drop it in the folder. Run the Binary Manager or Director and click the "Change" button at the bottom [see Setup above] and select the new NeatBot.exe you just downloaded. Now restart your bots and they'll be using this new one.

'''Q: Will I lose my goals if I start using this?'''

Maybe, but not because of the Manager or the Director. The Manager and Director themselves do not save your goals, all they do is help you to manage the bots you run.

'''Q: Do I need to keep the Binary Manager or Director running while using my bots?'''

You need to turn on the Manager or Director in order to launch your bots if they're not currently running. Afterwards you can close it or leave it running, your choice. You can close bots by clicking the "x" on the top right corner of their windows if you wish, or you can close them through the Manager or Director interface.

However, both the Manager and Director have options to automatically restart your bots on a schedule, and the Director has an option to automatically restart your bots if they begin using too much computer RAM. These restart options require the Manager or Director to be running.

'''Q: Can the binary manager be used for anything other than bots?'''

The Binary Manager opens the selected exe with the name you added as a parameter. As long as you know what this means, you can use it on what ever file you like.

Windows Setup

2012-08-16T11:10:56Z

Inanna: /* FAQ for the Manager and Director */

== Setup ==

 

 

== Binary Director ==

You can find a nice video tutorial on the official website for the director here: http://sumrandomguy.com/

 

 

== Binary Manager ==

 

 

== FAQ for the Manager and Director ==

'''Q: What are the Binary Manager and Director? Are they bots?'''

A ''binary'' is just a program compiled to run on your computer... NeatBot.exe is a binary - or binary bot, as we like to call it. Both the Binary Manager and the Binary Director are programs that will allow you to setup profiles for each binary bot you would normally run. With these profiles you can start, stop, restart, and even set the bots to auto-run. The Manager/Director itself is not a bot, you will need to download the binary bot also.

'''Q: Is the Binary Manager or Director required to use the binary bots?'''

No. You are free to run and use the bots without either of them, but if you run multiple accounts or servers, this will be very helpful to you. If you're not going to use the Manager or Director, you should keep a seperate folder for each account and/or server, so that when you run the NeatBot.exe you will not have to type in the login details each time. If using the Manager or Director, you're able to keep only 1 folder for all accounts to share.

'''Q: Can I use the Binary Manager or Director on my Linux or Mac OSX machine?'''

No. At this time they only work for Windows operating systems. You should be able to emulate it with WINE or similar Windows emulators on another OS. The menu links to your left will take you to a guide for setting up multiple bots with Mac OSX written by DarioJames.

'''Q: What is .NET Framework 4 and why do I need it?'''

If you're getting a message from the Binary Manager that it needs .NET Framework 4 installed, go to [http://www.microsoft.com/download/en/details.aspx?id=17851 http://www.microsoft.com/download/en/details.aspx?id=17851] and download it. The Manager needs the files from that in order to run on your computer. The Binary Director will not need these files.

'''Q: How do I update the Manager or Director? Or the bots I use with it?'''

This is super easy and why they are a great idea to use with multiple accounts. For the Manager or Director, download the new version and drop it into the folder where the old one is, allow the new version to overwrite the old one, restart it. For the Manager only you can also opt to run the auto-updater to allow it to download the updates for you. Future versions of the Manager are planned to update themselves automatically.

To update to a new YAEB.exe, download the new version, shutdown all your currently running bots, and drop it in the folder. Run the Binary Manager or Director and click the "Change" button at the bottom [see Setup above] and select the new NeatBot.exe you just downloaded. Now restart your bots and they'll be using this new one.

'''Q: Will I lose my goals if I start using this?'''

Maybe, but not because of the Manager or the Director. The Manager and Director themselves do not save your goals, all they do is help you to manage the bots you run.

'''Q: Do I need to keep the Binary Manager or Director running while using my bots?'''

You need to turn on the Manager or Director in order to launch your bots if they're not currently running. Afterwards you can close it or leave it running, your choice. You can close bots by clicking the "x" on the top right corner of their windows if you wish, or you can close them through the Manager or Director interface.

However, both the Manager and Director have options to automatically restart your bots on a schedule, and the Director has an option to automatically restart your bots if they begin using too much computer RAM. These restart options require the Manager or Director to be running.

'''Q: Can the binary manager be used for anything other than bots?'''

The Binary Manager opens the selected exe with the name you added as a parameter. As long as you know what this means, you can use it on what ever file you like.

Windows Setup

2012-08-16T11:10:34Z

Inanna:

== Setup ==

 

 

== Binary Director ==

You can find a nice video tutorial on the official website for the director here: http://sumrandomguy.com/

 

 

== Binary Manager ==

 

 

== FAQ for the Manager and Director ==

'''Q: What are the Binary Manager and Director? Are they bots?'''

A ''binary'' is just a program compiled to run on your computer... NeatBot.exe is a binary - or binary bot, as we like to call it. Both the Binary Manager and the Binary Director are programs that will allow you to setup profiles for each binary bot you would normally run. With these profiles you can start, stop, restart, and even set the bots to auto-run. The Manager/Director itself is not a bot, you will need to download the binary bot also.

'''Q: Is the Binary Manager or Director required to use the binary bots?'''

No. You are free to run and use the bots without either of them, but if you run multiple accounts or servers, this will be very helpful to you. If you're not going to use the Manager or Director, you should keep a seperate folder for each account and/or server, so that when you run the YAEB.exe you will not have to type in the login details each time. If using the Manager or Director, you're able to keep only 1 folder for all accounts to share.

'''Q: Can I use the Binary Manager or Director on my Linux or Mac OSX machine?'''

No. At this time they only work for Windows operating systems. You should be able to emulate it with WINE or similar Windows emulators on another OS. The menu links to your left will take you to a guide for setting up multiple bots with Mac OSX written by DarioJames.

'''Q: What is .NET Framework 4 and why do I need it?'''

If you're getting a message from the Binary Manager that it needs .NET Framework 4 installed, go to [http://www.microsoft.com/download/en/details.aspx?id=17851 http://www.microsoft.com/download/en/details.aspx?id=17851] and download it. The Manager needs the files from that in order to run on your computer. The Binary Director will not need these files.

'''Q: How do I update the Manager or Director? Or the bots I use with it?'''

This is super easy and why they are a great idea to use with multiple accounts. For the Manager or Director, download the new version and drop it into the folder where the old one is, allow the new version to overwrite the old one, restart it. For the Manager only you can also opt to run the auto-updater to allow it to download the updates for you. Future versions of the Manager are planned to update themselves automatically.

To update to a new YAEB.exe, download the new version, shutdown all your currently running bots, and drop it in the folder. Run the Binary Manager or Director and click the "Change" button at the bottom [see Setup above] and select the new NeatBot.exe you just downloaded. Now restart your bots and they'll be using this new one.

'''Q: Will I lose my goals if I start using this?'''

Maybe, but not because of the Manager or the Director. The Manager and Director themselves do not save your goals, all they do is help you to manage the bots you run.

'''Q: Do I need to keep the Binary Manager or Director running while using my bots?'''

You need to turn on the Manager or Director in order to launch your bots if they're not currently running. Afterwards you can close it or leave it running, your choice. You can close bots by clicking the "x" on the top right corner of their windows if you wish, or you can close them through the Manager or Director interface.

However, both the Manager and Director have options to automatically restart your bots on a schedule, and the Director has an option to automatically restart your bots if they begin using too much computer RAM. These restart options require the Manager or Director to be running.

'''Q: Can the binary manager be used for anything other than bots?'''

The Binary Manager opens the selected exe with the name you added as a parameter. As long as you know what this means, you can use it on what ever file you like.

Contact Us

2012-08-16T10:52:43Z

Inanna:

If you need help with your bot, you can contact us...

----

'''On the forums at'''

[http://forum.neatportal.com/ http://forum.neatportal.com/]

'''VIP Donators only skype at'''

skype:?chat&blob=DIPlJqN1tHvGKWOUebZcbrwhcbAMyT2bghfemu4E0tf2JDjyxpYNVZmiP3bVHQ (just copy/paste this into your browser)

Contact Us

2012-08-16T10:47:57Z

Inanna:

MediaWiki:Sidebar

2012-08-16T10:45:09Z

Inanna:

MediaWiki:Sidebar

2012-08-16T10:44:30Z

Inanna:

2012-08-16T10:21:26Z

Inanna: /* UpdateAllData */

2012-08-16T09:49:27Z

Inanna: /* Warrules */

==Gate==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config gate:[minutes]
|-
! style="text-align:left;" | Example:
|
config gate:1 
config gate:0.1
|}

With this option activated the bot will open and close the gates depending on the type of attack waves approaching the city. Town defence is quite complex, Y.A.E.B. can defend your city when it is strong, weak, or extremely weak. In general, if you have 300,000 archers Y.A.E.B. will allow scout bombs to hit, below 100,000 archers the bot will close the gate when attacked but will open the gate to deal with small loyalty attacks. When used along with [[Combat_Goals#Gatepolicy|gatepolicy]], you can instruct the bot what types of attacks to open for, and what to close for.

Note that the bot cannot properly work your gates if there is a time desync between your computer and the server, or server lag causing a delay. Split second timing is only possible with split second synchronization. In the 1st example above, the bot would open or close gates 1 minute before an incoming attack. In the 2nd example, the bot would open or close gates 0.1 minutes, or 6 seconds, before an incoming attack.

When you first log into the server with the bot, or when you click Refresh on the bot, it will show you the time delay:

<blockquote><pre>
14:18:48 Logged in successfully, server time difference: -23.756s
14:18:48 Your current computer time: 02:19:11 PM
14:18:48 PLEASE AVOID ADJUSTING YOUR COMPUTER CLOCK WHILE THE BOT IS RUNNING. IF YOU DO ADJUST, BE SURE TO CLICK ON REFRESH.
</pre></blockquote>

If this number is higher than your config gate setting, then the bot will open/close the gates too early or too late. You should adjust your computer clock to match the server time more closely.

 

==Gatepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| gatepolicy <no attack> <regular attack> <scout bomb> <mixed attack> <maintenance>
|-
! style="text-align:left;" | Example:
|
gatepolicy 2 1 2 0 1
|-
! style="text-align:left;" | Switch:
|
0 - Y.A.E.B.'s Choice 
1 - Open Gate 
2 - Close Gate
|}

This policy sets the actions to be taken by your bot in controlling the gate when your city is under attack. In order for gatepolicy to operate, you must use [[Combat_Goals#Gate|config gate]]. The bot can respond by deciding on it's own if it should open/close, always opening, or always closing the gates for each type of scenario: no attack, regular attack, scout bomb, mixed attack, and maintenance with this policy. In the example above: with no incoming attacks the bot will always keep gates closed, with regular incoming attacks will always keep gates open, with an incoming scout bomb will always close gates, with a mixed attack (some scout bombs, some regular attacks) will decide on it's own whether to open or close, and for maintenance it will always open gates.

 

==Defensepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| defensepolicy [/switches]
|-
! style="text-align:left;" | Example:
|
defensepolicy /junktroop:500 /usespeech:5 /usetruce:2 /usewarhorn:1 /usecorselet:1 /usepenicillin:0
|-
! style="text-align:left;" | Switch:
|
/junktroop:[quantity] 
/usecorselet:[0/1] 
/usewarhorn:[0/1] 
/usepenicillin:[0/1] 
/usetruce:[loyalty] 
/usespeech:[loyalty]
|}

This policy allows the player to control various defensive capabilities of the bot. Additional options will be added to this command in future revisions.

The /junktroop switch allows the player to set the number of troops under which an attack is considered junk. The default is 1000 if not specified. 
The /usespeech and /usetruce switches allow the player to designate the use of truce agreements or speech texts at the specified loyalty. 
The /usepenicillin, /usewarhorn, and /usecorselet switches allow the player to have the bot automatically apply these items when under attack.

 

==Embassy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config embassy:[value]
|-
! style="text-align:left;" | Example:
|
config embassy:1
|}

This goal allows you to instruct the bot how you want your embassy box checked. 1 will keep the embassy always open, 0 will keep the embassy always closed, and 2 will open the embassy only during an attack and shortly after an attack based on the [[Combat_Goals#Defensecooldown|config defensecooldown]] setting. Default is '1' for always open.

 

==Defensecooldown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config defensecooldown:[minutes]
|-
! style="text-align:left;" | Example:
|
config defensecooldown:30
|}

This goal allows you to instruct how long after an attack hits you or is recalled for it to keep the embassy open when using [[Combat_Goals#Embassy|config embassy:2]]. Junk attacks are ignored for this goal. The default is 30 minutes.

 

==Attackgap==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config attackgap:[seconds]
|-
! style="text-align:left;" | Example:
|
config attackgap:3
|}

This goal allows you to instruct the bot how many seconds in between attacking waves constitutes as a seperate attack for purposes of evasion. With the example above,the bot will consider all attacks at least 3 seconds apart as seperate attacks, and try to evade each of them. If the time between is less, it will evade them together only once. The default attackgap is 6 seconds, if this goal is not set.

 

==Hiding==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config hiding:[minutes]
|-
! style="text-align:left;" | Example:
|
config hiding:1.5
|}

When enabled, the hiding goal will attempt to hide resources and excess troop when under attack by moving a rainbow and resources. This will ensure you have sufficient resources and troops to continue defending. This goal is very useful when your city is still weak, if there are a lot of archers in your city hiding is not effective. The bot requires a hero available in the town to send the evasion attack for the rainbow. If all heroes are out farming or the rally spots are all full, hiding will fail.

In the example above, the bot will attempt to hide troops and resources 1.5 minutes prior to the attack landing.

 

==Warrules==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config warrules:[minutes]
|-
! style="text-align:left;" | Example:
|
config warrules:1
|}

Activating this goal will send a message in alliance chat to your alliance giving them minimal information regarding an incoming attack on your city.

When the first non-junk attack is sent, the bot will send the message to alliance chat. It will send updates with changes in attacks or new attacks every X minutes as specified in the goal. If no new attacks are added, or current attacks are changed, then it will only send a reminder every X*5 minutes as specified in the goal.

 

==Wartown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config wartown:[switch]
|-
! style="text-align:left;" | Example:
|
config wartown:1
|}

With this goal enabled, the bot will "lockdown" most troop movements in preparation of war. No npc farming runs, keepresource/sendresource, or keeptroop/sendtroop goals will be performed with this enabled. The bot will also recall all marching farm runs back to the city. When this goal is set to 1, the traininghero may move freely into and out of the city. When this goal is set to 2, the traininghero will remain in the city if/when it lands there.

 

==Monitorarmy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config monitorarmy:[switch]
|-
! style="text-align:left;" | Example:
|
config monitorarmy:1
|}

This goal will instruct Y.A.E.B. to check the target to make sure it's the same as it was when you launched the attack.. if not recall.

 

==Wartownpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| wartownpolicy start_time end_time [start_time end_time start_time end_time]
|-
! style="text-align:left;" | Example:
|
wartownpolicy 06:00 12:00
|}

This policy will tell the bot to cease attacks on npcs, valleys, etc. and keep all resource and troop transport missions home in preparation of war at a set schedule. In the example above, the bot would halt all farming attacks and troop/resource transport missions from 6 to 12, and perform as normal the rest of the time. You can add multiple start and end times to this policy, eg: wartownpolicy 06:00 12:00 5:00 23:00. This policy may be wise to use in conjunction with [[General_Goals#Schedulepolicy|schedulepolicy]] so that you can ensure your farm runs are completed and home (and therefore troops healed) before the bot shuts down at a set schedule.

'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''

Combat Goals

2012-08-16T09:48:52Z

Inanna: /* Gatepolicy */

==Gate==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config gate:[minutes]
|-
! style="text-align:left;" | Example:
|
config gate:1 
config gate:0.1
|}

With this option activated the bot will open and close the gates depending on the type of attack waves approaching the city. Town defence is quite complex, Y.A.E.B. can defend your city when it is strong, weak, or extremely weak. In general, if you have 300,000 archers Y.A.E.B. will allow scout bombs to hit, below 100,000 archers the bot will close the gate when attacked but will open the gate to deal with small loyalty attacks. When used along with [[Combat_Goals#Gatepolicy|gatepolicy]], you can instruct the bot what types of attacks to open for, and what to close for.

Note that the bot cannot properly work your gates if there is a time desync between your computer and the server, or server lag causing a delay. Split second timing is only possible with split second synchronization. In the 1st example above, the bot would open or close gates 1 minute before an incoming attack. In the 2nd example, the bot would open or close gates 0.1 minutes, or 6 seconds, before an incoming attack.

When you first log into the server with the bot, or when you click Refresh on the bot, it will show you the time delay:

<blockquote><pre>
14:18:48 Logged in successfully, server time difference: -23.756s
14:18:48 Your current computer time: 02:19:11 PM
14:18:48 PLEASE AVOID ADJUSTING YOUR COMPUTER CLOCK WHILE THE BOT IS RUNNING. IF YOU DO ADJUST, BE SURE TO CLICK ON REFRESH.
</pre></blockquote>

If this number is higher than your config gate setting, then the bot will open/close the gates too early or too late. You should adjust your computer clock to match the server time more closely.

 

==Gatepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| gatepolicy <no attack> <regular attack> <scout bomb> <mixed attack> <maintenance>
|-
! style="text-align:left;" | Example:
|
gatepolicy 2 1 2 0 1
|-
! style="text-align:left;" | Switch:
|
0 - Y.A.E.B.'s Choice 
1 - Open Gate 
2 - Close Gate
|}

This policy sets the actions to be taken by your bot in controlling the gate when your city is under attack. In order for gatepolicy to operate, you must use [[Combat_Goals#Gate|config gate]]. The bot can respond by deciding on it's own if it should open/close, always opening, or always closing the gates for each type of scenario: no attack, regular attack, scout bomb, mixed attack, and maintenance with this policy. In the example above: with no incoming attacks the bot will always keep gates closed, with regular incoming attacks will always keep gates open, with an incoming scout bomb will always close gates, with a mixed attack (some scout bombs, some regular attacks) will decide on it's own whether to open or close, and for maintenance it will always open gates.

 

==Defensepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| defensepolicy [/switches]
|-
! style="text-align:left;" | Example:
|
defensepolicy /junktroop:500 /usespeech:5 /usetruce:2 /usewarhorn:1 /usecorselet:1 /usepenicillin:0
|-
! style="text-align:left;" | Switch:
|
/junktroop:[quantity] 
/usecorselet:[0/1] 
/usewarhorn:[0/1] 
/usepenicillin:[0/1] 
/usetruce:[loyalty] 
/usespeech:[loyalty]
|}

This policy allows the player to control various defensive capabilities of the bot. Additional options will be added to this command in future revisions.

The /junktroop switch allows the player to set the number of troops under which an attack is considered junk. The default is 1000 if not specified. 
The /usespeech and /usetruce switches allow the player to designate the use of truce agreements or speech texts at the specified loyalty. 
The /usepenicillin, /usewarhorn, and /usecorselet switches allow the player to have the bot automatically apply these items when under attack.

 

==Embassy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config embassy:[value]
|-
! style="text-align:left;" | Example:
|
config embassy:1
|}

This goal allows you to instruct the bot how you want your embassy box checked. 1 will keep the embassy always open, 0 will keep the embassy always closed, and 2 will open the embassy only during an attack and shortly after an attack based on the [[Combat_Goals#Defensecooldown|config defensecooldown]] setting. Default is '1' for always open.

 

==Defensecooldown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config defensecooldown:[minutes]
|-
! style="text-align:left;" | Example:
|
config defensecooldown:30
|}

This goal allows you to instruct how long after an attack hits you or is recalled for it to keep the embassy open when using [[Combat_Goals#Embassy|config embassy:2]]. Junk attacks are ignored for this goal. The default is 30 minutes.

 

==Attackgap==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config attackgap:[seconds]
|-
! style="text-align:left;" | Example:
|
config attackgap:3
|}

This goal allows you to instruct the bot how many seconds in between attacking waves constitutes as a seperate attack for purposes of evasion. With the example above,the bot will consider all attacks at least 3 seconds apart as seperate attacks, and try to evade each of them. If the time between is less, it will evade them together only once. The default attackgap is 6 seconds, if this goal is not set.

 

==Hiding==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config hiding:[minutes]
|-
! style="text-align:left;" | Example:
|
config hiding:1.5
|}

When enabled, the hiding goal will attempt to hide resources and excess troop when under attack by moving a rainbow and resources. This will ensure you have sufficient resources and troops to continue defending. This goal is very useful when your city is still weak, if there are a lot of archers in your city hiding is not effective. The bot requires a hero available in the town to send the evasion attack for the rainbow. If all heroes are out farming or the rally spots are all full, hiding will fail.

In the example above, the bot will attempt to hide troops and resources 1.5 minutes prior to the attack landing.

 

==Warrules==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config warrules:[minutes]
|-
! style="text-align:left;" | Example:
|
config warrules:1
|}

Activating this goal will send a message in alliance chat to your alliance giving them minimal information regarding an incoming attack on your city.

When the first non-junk attack is sent, the bot will send the message to alliance chat. It will send updates with changes in attacks or new attacks every X minutes as specified in the goal. If no new attacks are added, or current attacks are changed, then it will only send a reminder every X*5 minutes as specified in the goal.

Builds prior to Nov 9, 2011 do not have the option of user-defined minutes between notifications. The config is simply "1" to enable it, and it will update all attacks, changed or otherwise, every 1 minute.

 

==Wartown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config wartown:[switch]
|-
! style="text-align:left;" | Example:
|
config wartown:1
|}

With this goal enabled, the bot will "lockdown" most troop movements in preparation of war. No npc farming runs, keepresource/sendresource, or keeptroop/sendtroop goals will be performed with this enabled. The bot will also recall all marching farm runs back to the city. When this goal is set to 1, the traininghero may move freely into and out of the city. When this goal is set to 2, the traininghero will remain in the city if/when it lands there.

 

==Monitorarmy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config monitorarmy:[switch]
|-
! style="text-align:left;" | Example:
|
config monitorarmy:1
|}

This goal will instruct Y.A.E.B. to check the target to make sure it's the same as it was when you launched the attack.. if not recall.

 

==Wartownpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| wartownpolicy start_time end_time [start_time end_time start_time end_time]
|-
! style="text-align:left;" | Example:
|
wartownpolicy 06:00 12:00
|}

This policy will tell the bot to cease attacks on npcs, valleys, etc. and keep all resource and troop transport missions home in preparation of war at a set schedule. In the example above, the bot would halt all farming attacks and troop/resource transport missions from 6 to 12, and perform as normal the rest of the time. You can add multiple start and end times to this policy, eg: wartownpolicy 06:00 12:00 5:00 23:00. This policy may be wise to use in conjunction with [[General_Goals#Schedulepolicy|schedulepolicy]] so that you can ensure your farm runs are completed and home (and therefore troops healed) before the bot shuts down at a set schedule.

'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''

Combat Goals

2012-08-16T09:48:40Z

Inanna: /* Gate */

==Gate==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config gate:[minutes]
|-
! style="text-align:left;" | Example:
|
config gate:1 
config gate:0.1
|}

With this option activated the bot will open and close the gates depending on the type of attack waves approaching the city. Town defence is quite complex, Y.A.E.B. can defend your city when it is strong, weak, or extremely weak. In general, if you have 300,000 archers Y.A.E.B. will allow scout bombs to hit, below 100,000 archers the bot will close the gate when attacked but will open the gate to deal with small loyalty attacks. When used along with [[Combat_Goals#Gatepolicy|gatepolicy]], you can instruct the bot what types of attacks to open for, and what to close for.

Note that the bot cannot properly work your gates if there is a time desync between your computer and the server, or server lag causing a delay. Split second timing is only possible with split second synchronization. In the 1st example above, the bot would open or close gates 1 minute before an incoming attack. In the 2nd example, the bot would open or close gates 0.1 minutes, or 6 seconds, before an incoming attack.

When you first log into the server with the bot, or when you click Refresh on the bot, it will show you the time delay:

<blockquote><pre>
14:18:48 Logged in successfully, server time difference: -23.756s
14:18:48 Your current computer time: 02:19:11 PM
14:18:48 PLEASE AVOID ADJUSTING YOUR COMPUTER CLOCK WHILE THE BOT IS RUNNING. IF YOU DO ADJUST, BE SURE TO CLICK ON REFRESH.
</pre></blockquote>

If this number is higher than your config gate setting, then the bot will open/close the gates too early or too late. You should adjust your computer clock to match the server time more closely.

 

==Gatepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| gatepolicy <no attack> <regular attack> <scout bomb> <mixed attack> <maintenance>
|-
! style="text-align:left;" | Example:
|
gatepolicy 2 1 2 0 1
|-
! style="text-align:left;" | Switch:
|
0 - Y.A.E.B.'s Choice 
1 - Open Gate 
2 - Close Gate
|}

This policy sets the actions to be taken by Y.A.E.B. in controlling the gate when your city is under attack. In order for gatepolicy to operate, you must use [[Combat_Goals#Gate|config gate]]. The bot can respond by deciding on it's own if it should open/close, always opening, or always closing the gates for each type of scenario: no attack, regular attack, scout bomb, mixed attack, and maintenance with this policy. In the example above: with no incoming attacks the bot will always keep gates closed, with regular incoming attacks will always keep gates open, with an incoming scout bomb will always close gates, with a mixed attack (some scout bombs, some regular attacks) will decide on it's own whether to open or close, and for maintenance it will always open gates.

 

==Defensepolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| defensepolicy [/switches]
|-
! style="text-align:left;" | Example:
|
defensepolicy /junktroop:500 /usespeech:5 /usetruce:2 /usewarhorn:1 /usecorselet:1 /usepenicillin:0
|-
! style="text-align:left;" | Switch:
|
/junktroop:[quantity] 
/usecorselet:[0/1] 
/usewarhorn:[0/1] 
/usepenicillin:[0/1] 
/usetruce:[loyalty] 
/usespeech:[loyalty]
|}

This policy allows the player to control various defensive capabilities of the bot. Additional options will be added to this command in future revisions.

The /junktroop switch allows the player to set the number of troops under which an attack is considered junk. The default is 1000 if not specified. 
The /usespeech and /usetruce switches allow the player to designate the use of truce agreements or speech texts at the specified loyalty. 
The /usepenicillin, /usewarhorn, and /usecorselet switches allow the player to have the bot automatically apply these items when under attack.

 

==Embassy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config embassy:[value]
|-
! style="text-align:left;" | Example:
|
config embassy:1
|}

This goal allows you to instruct the bot how you want your embassy box checked. 1 will keep the embassy always open, 0 will keep the embassy always closed, and 2 will open the embassy only during an attack and shortly after an attack based on the [[Combat_Goals#Defensecooldown|config defensecooldown]] setting. Default is '1' for always open.

 

==Defensecooldown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config defensecooldown:[minutes]
|-
! style="text-align:left;" | Example:
|
config defensecooldown:30
|}

This goal allows you to instruct how long after an attack hits you or is recalled for it to keep the embassy open when using [[Combat_Goals#Embassy|config embassy:2]]. Junk attacks are ignored for this goal. The default is 30 minutes.

 

==Attackgap==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config attackgap:[seconds]
|-
! style="text-align:left;" | Example:
|
config attackgap:3
|}

This goal allows you to instruct the bot how many seconds in between attacking waves constitutes as a seperate attack for purposes of evasion. With the example above,the bot will consider all attacks at least 3 seconds apart as seperate attacks, and try to evade each of them. If the time between is less, it will evade them together only once. The default attackgap is 6 seconds, if this goal is not set.

 

==Hiding==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config hiding:[minutes]
|-
! style="text-align:left;" | Example:
|
config hiding:1.5
|}

When enabled, the hiding goal will attempt to hide resources and excess troop when under attack by moving a rainbow and resources. This will ensure you have sufficient resources and troops to continue defending. This goal is very useful when your city is still weak, if there are a lot of archers in your city hiding is not effective. The bot requires a hero available in the town to send the evasion attack for the rainbow. If all heroes are out farming or the rally spots are all full, hiding will fail.

In the example above, the bot will attempt to hide troops and resources 1.5 minutes prior to the attack landing.

 

==Warrules==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config warrules:[minutes]
|-
! style="text-align:left;" | Example:
|
config warrules:1
|}

Activating this goal will send a message in alliance chat to your alliance giving them minimal information regarding an incoming attack on your city.

When the first non-junk attack is sent, the bot will send the message to alliance chat. It will send updates with changes in attacks or new attacks every X minutes as specified in the goal. If no new attacks are added, or current attacks are changed, then it will only send a reminder every X*5 minutes as specified in the goal.

Builds prior to Nov 9, 2011 do not have the option of user-defined minutes between notifications. The config is simply "1" to enable it, and it will update all attacks, changed or otherwise, every 1 minute.

 

==Wartown==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config wartown:[switch]
|-
! style="text-align:left;" | Example:
|
config wartown:1
|}

With this goal enabled, the bot will "lockdown" most troop movements in preparation of war. No npc farming runs, keepresource/sendresource, or keeptroop/sendtroop goals will be performed with this enabled. The bot will also recall all marching farm runs back to the city. When this goal is set to 1, the traininghero may move freely into and out of the city. When this goal is set to 2, the traininghero will remain in the city if/when it lands there.

 

==Monitorarmy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| config monitorarmy:[switch]
|-
! style="text-align:left;" | Example:
|
config monitorarmy:1
|}

This goal will instruct Y.A.E.B. to check the target to make sure it's the same as it was when you launched the attack.. if not recall.

 

==Wartownpolicy==

{| class="wikitable"
! style="text-align:left;" | Usage:
| wartownpolicy start_time end_time [start_time end_time start_time end_time]
|-
! style="text-align:left;" | Example:
|
wartownpolicy 06:00 12:00
|}

This policy will tell the bot to cease attacks on npcs, valleys, etc. and keep all resource and troop transport missions home in preparation of war at a set schedule. In the example above, the bot would halt all farming attacks and troop/resource transport missions from 6 to 12, and perform as normal the rest of the time. You can add multiple start and end times to this policy, eg: wartownpolicy 06:00 12:00 5:00 23:00. This policy may be wise to use in conjunction with [[General_Goals#Schedulepolicy|schedulepolicy]] so that you can ensure your farm runs are completed and home (and therefore troops healed) before the bot shuts down at a set schedule.

'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''