• My Pages
  • Comments
  • Add Link
  • Subscribe
  • Subscribe User
  • Edit (GUI)
  • Edit (Text)
  • Rename Page
  • Copy Page
  • Load Page
  • Save Page
  • Delete Page
  • Attachments
  • Check Spelling
  • Diffs
  • Info
  • Revert to this revision
  • XML
  • Render as Docbook
  • Print View
  • Raw Text
  • Delete Cache
  • Like Pages
  • Local Site Map
  • Remove Spam
  • Package Pages
  • Sync Pages

    Revision 1 as of 2012-09-24 20:53:57

    Clear message

    Usage: train <type:quantity> <hero> <barracks_id|all|idle> <minquantity> Example: train w:25000 atk Train 25,000 warriors with the best availible attack hero as mayor.

    Troop types cannot be combined. 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 available attack hero), or named. 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' 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 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

    Training via script will train in the same manner as the client. The 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 barracks.

    In all instances training via script uses no more than 1 barracks slot per barrack per train command.