Combat Goals - Revision history

Inanna: /* Gatepolicy */

2012-08-16T09:50:30Z

‎Gatepolicy

Inanna: /* Gate */

2012-08-16T09:50:16Z

‎Gate

Inanna: /* Monitorarmy */

2012-08-16T09:49:39Z

‎Monitorarmy

Inanna: /* Warrules */

2012-08-16T09:49:27Z

‎Warrules

Inanna: /* Gatepolicy */

2012-08-16T09:48:52Z

‎Gatepolicy

Inanna: /* Gate */

2012-08-16T09:48:40Z

‎Gate

Anonymous: Just removed extra vertical space in one place

2012-05-12T08:47:36Z

Just removed extra vertical space in one place

Inanna at 19:31, 2 February 2012

2012-02-02T19:31:33Z

Anonymous: /* Wartownpolicy */ added note on config.

2011-11-16T22:44:01Z

‎Wartownpolicy: added note on config.

Inanna: /* Attackgap */

2011-10-19T18:28:29Z

‎Attackgap

@@ Line 39: / Line 39: @@
 ! style="text-align:left;" | Switch:
+|
-<font size="2" face="courier" color="#A43900">0</font> - Y.A.E.B.'s Choice<br>
+<font size="2" face="courier" color="#A43900">0</font> - Bot's Choice<br>
 <font size="2" face="courier" color="#A43900">1</font> - Open Gate<br>
 <font size="2" face="courier" color="#A43900">2</font> - Close Gate

@@ Line 11: / Line 11: @@
 |}
-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.
+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, the bot can defend your city when it is strong, weak, or extremely weak. In general, if you have 300,000 archers the bot 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.

@@ Line 181: / Line 181: @@
 |}
-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.
+This goal will instruct your bot to check the target to make sure it's the same as it was when you launched the attack.. if not recall.
 <br>

← Older revision		Revision as of 09:49, 16 August 2012
Line 152:		Line 152:

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

	<br>		<br>

@@ Line 44: / Line 44: @@
 |}
-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.
+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.
 <br>

← Older revision		Revision as of 08:47, 12 May 2012
Line 200:		Line 200:
	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.		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.

−	~~<br>~~
	'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''		'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''

← Older revision		Revision as of 19:31, 2 February 2012
Line 135:		Line 135:

	In the example above, the bot will attempt to hide troops and resources 1.5 minutes prior to the attack landing.		In the example above, the bot will attempt to hide troops and resources 1.5 minutes prior to the attack landing.
		+
		+	<br>
		+
		+	==Warrules==
		+
		+	{\| class="wikitable"
		+	! style="text-align:left;" \| Usage:
		+	\| config warrules:[minutes]
		+	\|-
		+	! style="text-align:left;" \| Example:
		+	\|
		+	<font size="2" face="courier" color="#0000FF">config </font><font size="2" face="courier" color="#6699CC">warrules</font><font size="2" face="courier" color="#000000">:</font><font size="2" face="courier" color="#A43900">1</font>
		+	\|}
		+
		+	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.

	<br>		<br>

@@ Line 182: / Line 182: @@
 <br>
+'''Note: This policy has no effect unless config wartown:1 or config wartown:2 is set.'''
 <br>

@@ Line 114: / Line 114: @@
 ! style="text-align:left;" | Example:
+|
-<font size="2" face="courier" color="#0000FF">config </font><font size="2" face="courier" color="#6699CC">attackgap</font><font size="2" face="courier" color="#000000">:</font><font size="2" face="courier" color="#A43900">30</font>
+<font size="2" face="courier" color="#0000FF">config </font><font size="2" face="courier" color="#6699CC">attackgap</font><font size="2" face="courier" color="#000000">:</font><font size="2" face="courier" color="#A43900">3</font>
 |}
-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 30 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 60 seconds, if this goal is not set.
+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.
 <br>