Troop Scripts - Revision history

Anonymous: /* ClearWallQueue */

2012-04-02T19:27:41Z

‎ClearWallQueue

Anonymous: /* ClearWallQueue */

2012-04-02T19:27:22Z

‎ClearWallQueue

Inanna: /* ClearWallQueue */

2012-03-02T17:27:23Z

‎ClearWallQueue

Inanna at 16:22, 15 December 2011

2011-12-15T16:22:45Z

Anonymous: table format

2011-06-13T06:29:43Z

table format

Inanna: /* Train */

2011-06-02T00:25:31Z

‎Train

Inanna: /* Train */

2011-06-02T00:25:12Z

‎Train

Anonymous: /* Train */ added a bit

2011-06-01T16:20:41Z

‎Train: added a bit

Anonymous: /* Train */ lol, hero called atk??

2011-06-01T16:09:42Z

‎Train: lol, hero called atk??

Inanna at 15:13, 1 June 2011

2011-06-01T15:13:34Z

@@ Line 122: / Line 122: @@
 Used to cancel fortifications queues, leaving remain_count batches.
 If no remain_count is provided, all batches except the first are removed.
 (this may be outdated, try cancelfortifications instead)

@@ Line 122: / Line 122: @@
 Used to cancel fortifications queues, leaving remain_count batches.
 If no remain_count is provided, all batches except the first are removed.
 ==EndKeepTroop==

@@ Line 117: / Line 117: @@
+|
 clearwallqueue<br>
-clearwallqueue
+clearwallqueue 2
 |}
 Used to cancel fortifications queues, leaving remain_count batches.
 If no remain_count is provided, all batches except the first are removed.
 ==EndKeepTroop==

@@ Line 76: / Line 76: @@
 Dump 20,000 archers and 15,000 scouts to 111,222 when there are at least 99,000 archers and 50,000 scouts in the city.
-==ClearTroopQueues==
+==CancelTroopQueues==
 {| class="wikitable"
 ! style="text-align:left;" | Usage:
-| cleartroopqueues [remain_count]
+| canceltroopqueues [remain_count]
 |-
 ! style="text-align:left;" | Example:
+|
-cleartroopqueues<br>
+canceltroopqueues<br>
-cleartroopqueues 2
+canceltroopqueues 2
 |}

@@ Line 3: / Line 3: @@
 {| class="wikitable"
 ! style="text-align:left;" | Usage:
-| train <type:quantity> <hero> <barracks_id|all|idle> <minquantity>
+|width="400pt" | train <type:quantity> <hero> <barracks_id|all|idle> <minquantity>
 |-
 ! style="text-align:left;" | Example:

@@ Line 19: / Line 19: @@
 Not all parameters are required. Setting production before and after is recommended, but there is no need to manually change the mayor. The bot will temporarily assign the hero indicated to train, then reassign the original mayor when done.
-'''train a:5000''' will train up to 5k arch in all barx.
+'''train a:5000''' will train up to 5k arch in all barracks.
 '''train a:999999 ace idle 20000''' will train as many as possible, but not less than 20k, in all idle barracks with ace as mayor

@@ Line 3: / Line 3: @@
 {| class="wikitable"
 ! style="text-align:left;" | Usage:
-| train troop hero
+| train <type:quantity> <hero> <barracks_id|all|idle> <minquantity>
 |-
 ! style="text-align:left;" | Example:
@@ Line 10: / Line 10: @@
 Train 25,000 warriors with the best availible attack hero as mayor.
 *Troop types cannot be combined.
-*if the qty is more than you can actually build based on res or pop, it will build as many as it can.
+*If the quantity is more than you can actually build based on res or pop, it will build as many as it can.
-*The hero can be "any", "atk" (for the best availible attack hero), or named.
+*The hero can be "any", "atk" (for the best available attack hero), or named.
-*You can specify a barx (the #s can be found in the production tab), use "all" or "idle" barx only.
+*You can specify a barrack (the #s can be found in the production tab), use "all" or "idle" barracks only.
-::The last value says: 'if I can't train this many, don't train any'
+::The last value says: 'If I can't train this many, don't train any'
-Not all parameterers are required. Setting production before and after is recommended, but there is no need to manually change the mayor. The bot will temporarily assign the hero indicated to train, then reassign the original mayor when done.
+Not all parameters are required. Setting production before and after is recommended, but there is no need to manually change the mayor. The bot will temporarily assign the hero indicated to train, then reassign the original mayor when done.
 '''train a:5000''' will train up to 5k arch in all barx.
-'''train a:999999 ace idle 20000''' will train as many as possible, but not less than 20k, in all idle barx with ace as mayor
+'''train a:999999 ace idle 20000''' will train as many as possible, but not less than 20k, in all idle barracks with ace as mayor
-Training via script will train in the same manner as the client. Values set in goals like
+Training via script will train in the same manner as the client. The values set in goals like...
 *config troopqueuetime:.25
@@ Line 33: / Line 30: @@
 *config troopincrement:.15
-will be ignored.
+...will be ignored.
 '''train w:25000 atk 18 25000''' will train 25k warrior in one slot.
-using ''all'' or ''idle'' will perform the same as the client, not distribute blocks of 500 warriors into 9 slots of 8 different barx.
+Using ''all'' or ''idle'' will perform the same as the client, not distribute blocks of 500 warriors into 9 slots of 8 different barracks.
-In all instances training via script uses no more than 1 barx slot per barx per train command
+In all instances training via script uses no more than 1 barracks slot per barrack per train command.
 ==Disband==

← Older revision		Revision as of 16:20, 1 June 2011
Line 10:		Line 10:

	Train 25,000 warriors with the best availible attack hero as mayor.		Train 25,000 warriors with the best availible attack hero as mayor.
		+
		+
		+	'''train <type:qty> <hero> <barxid\|all\|idle> <minqty>'''
		+
		+	*Troop types cannot be combined.
		+	*if the qty is more than you can actually build based on res or pop, it will build as many as it can.
		+	*The hero can be "any", "atk" (for the best availible attack hero), or named.
		+	*You can specify a barx (the #s can be found in the production tab), use "all" or "idle" barx only.
		+	::The last value says: 'if I can't train this many, don't train any'
		+
		+	Not all parameterers are required. Setting production before and after is recommended, but there is no need to manually change the mayor. The bot will temporarily assign the hero indicated to train, then reassign the original mayor when done.
		+
		+	'''train a:5000''' will train up to 5k arch in all barx.
		+
		+	'''train a:999999 ace idle 20000''' will train as many as possible, but not less than 20k, in all idle barx with ace as mayor
		+
		+	Training via script will train in the same manner as the client. Values set in goals like
		+
		+	*config troopqueuetime:.25
		+	*config troopsusepopmax:0.99
		+	*config troopsusereserved:.75
		+	*config troopincrement:.15
		+
		+	will be ignored.
		+
		+	'''train w:25000 atk 18 25000''' will train 25k warrior in one slot.
		+
		+	using ''all'' or ''idle'' will perform the same as the client, not distribute blocks of 500 warriors into 9 slots of 8 different barx.
		+
		+	In all instances training via script uses no more than 1 barx slot per barx per train command

	==Disband==		==Disband==

@@ Line 1: / Line 1: @@
 ==Train==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | train troop hero
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | train w:25000 atk
 |}
@@ Line 14: / Line 14: @@
 ==Disband==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | disband troop
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | disband w:25
 |}
@@ Line 27: / Line 27: @@
 ==HealTroops==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | healtroops
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | healtroops
 |}
@@ Line 40: / Line 40: @@
 ==DumpTroop==
-{| style="width: 45%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | dumptroop xxx,yyy condition troops
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | dumptroop 111,222 a:99000,s:50000 a:20000,s:15000
 |}
@@ Line 52: / Line 52: @@
 ==ClearTroopQueues==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | cleartroopqueues [remain_count]
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | cleartroopqueues<br>
 cleartroopqueues 2
 |}
@@ Line 68: / Line 69: @@
 ==WallDefense==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | walldefense DefType Qty [BuildType]
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | walldefense at 1000<br>
 walldefense ab 1000 demo
 |}
@@ Line 82: / Line 84: @@
 ==ClearWallQueue==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | clearwallqueue [remain count]
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | clearwallqueue<br>
 clearwallqueue
 |}
@@ Line 97: / Line 100: @@
 ==EndKeepTroop==
-{| style="width: 25%; text-align:center" border="1"
+{| class="wikitable"
-! scope="row" | Usage:
+! style="text-align:left;" | Usage:
 | EndKeepTroop
 |-
-! scope="row" | Example:
+! style="text-align:left;" | Example:
 | EndKeepTroop
 |}
 Cancel the KeepTroop command.