Below you can find the basic instructions for configure the bot in order to properly function for 1 account.
The configuration spectrum is virtually limited only by your imagination/creativity but it obviously has some requirements and syntax needed.
In order to be able to configure the script you have to first understand how it works and from there on is quite simple.
The configuration is not a menu , but a folder with files that are configured with written text. This leaves the user freedom and power , in comparing with a graphical menu/interface , which would limit very much the possibilities.
The configuration older is called /config and there are all the files that needs to be configured.
Do not scare if you see to many, not all of them are needed to be configured for 1 account , but rather few.
I.[What are your REQUIRED to configure?]
General files needed to be configured as general parameters for whole script
– config/certificate.txt – This is the file where your access key is stored .
On the first line of this file you have to fill in the access key , in order to use this program. A test key you can always find here. Remember that you can only use the test key for very limited time on a certain machine. The key can be reused on a different machine. An access key for a longer period of time can be acquired by emailing to trav.monro
gmail.com
The file looks like below:
– config/params.txt
Here are the parameters that you need to configure for the super script , travbot061.exe , in this case .
On the 1st line there is the time in seconds before the script actually begins to cycle through the accounts.
This is useful especially if you schedule your script to start when the computer starts. You may not want that the computer to be slowed down at startup , by the script. Also if your internet connection initializes slowly , you may wanna give it upto 120-120 seconds of delay before starting.
On the 2nd line there is the state of the balancer with 3 options : yes , no , and half.
–yes means that the script is very aggressive checking when any unbalance it is in a village and trying to balance it with resources from /to other villages.
–half means that the script only checks if the warehouses and granaries are about to be exceeded and if the troops are about to starve and take the necessary measures for this not to happen.
–no is still checking if the troops are about to starve and tries to treat this , but that’s all. [You cannot disable this last action as it is critical]
On the 3rd line there’s the option waitacc with possible values: yes, no , half.
-this is about the time that the next cycle should be delayed with. If you play with just an account you should set it to yes , or half. No is just for lots of accounts.
On the 4th line there is the verbose with options : yes, no.
–yes means that the script is writing a very comprehensive log in logs/travlog.txt. You should use this only if your script does not work as expected and you want to see why, or i you gather information to be sent to developer , or if you are the developer (no chance:) ). Also this option increases the number of informational pop-ups shown in tray bar .
–no reduced logs and only base informational pop-ups. Just to play quiet undisturbed
The 5th line is PreventIE2DownloadPictures with options : no, yes
this is tricky as it establishes if your browser will download or not the pictures when the script is running. If you have a bad internet link and you want fast response times or if you have small ammount of RAM memory installed , you may set this to yes, which means that the pictures from the site won’t be downloaded. However , you won’t be able to access internet explorer in the same time when script is running as you won’t see any pictures.
This is recommended only if you know what you’re doing. If your IE remains blocked on not displaying pictures , you should use the program FixInternetExplorer.exe to revert it.
Below you can see how this files looks like in the default configuration.
– config/turn.txt should be configured as follows , if you are only using 1 account.
a
config/a.txt
config/a1.txt
config/a1b.txt
config/a1a.txt
See also the picture below:
Specific files that need to be configured per account
- The text file that holds login data and the identification data of the account:
config/a.txt
- On 1st line, there must be the username without any spaces ( other than those that may exist in the actual username)
- On 2nd line, there must be the password of the account
- On the 3rd line there must be the login link.
- On the 4th line there must be the link to the outer village ( dorf1)
- On the 5th line there must be the build link.
- On the 6th line there must be the attack link.
- On the 7th line there must be the language. For now leave there the fixed link that is: ltrav/english.txt
- On the 8th line there must be the home address of the server you’re playing.
- On the 9th line there must be the kind chosen by the user at the start of the server. Possible values: roman , gaul, teuton.
Even though there could be complicated the example beow id very relevant and simple to follow as pattern , unless the user is retarded, or he does not understand any |English .
2. The text file that holds the IDs of the villages from this account. This is particularly important as it differentiates the villages for the internal calculations. If the user has only one village , any number can be passed on 2nd line.
– /config/a1.txt
- On the 1st line there is the standard text :****Towns IDs************* ( this should not be removed or replaced)
- On the next lines starting with the 2nd , there must be the IDs of the villages , one per line.
Check below , how you should get the IDs from the account. [In the future this will be filled in automatically]
The ID of this village is obtained by clicking the village and taking the ID from the address bar of your browser
3. The file that schedules the attacks. This file has any attack defined as a group of 5 lines. Multiple attacks can be scheduled.
– /config/a1a.txt
The description of the lines composing an attack is as follows:
- 1st line describes the ID of the village FROM which the attack is started by the syntax: $ID , where $ is an identifier and ID is the village id from a.txt.
- 2nd line describes the time and the type of the attack as follows:
Time is described in format >hh:mm|ss:type_of _attack. Hours are in the format 0-24.
The possible types of attack are:
x – ignores the time of attack and triggers the attack at each pass , as long as there are enough troups to attack with.
f – this is the intelligent farming attack. The attack is triggered at a pass, when the current time is later than the time configured in the time line. Then the time is updated in this line to a future time, taking account of the distance till target and of the time that troops are taking to go there and back. [Act with caution]
p – is the post attack, by that meaning the attack is given if the configured time is earlier than current time when passing through account. The time is updated with the time that troops is taking to go there and back.
s – is the sharp mode. In this mode only one attack will be released if the current time is exactly the one configured. Therefore if a pass is made and there are less than 5 minutes until the time configured for a sharp attack, the script is blocked until that time and the attack is launched at the specified time. The time won’t be updated in config file so another attack will not be attempted ( until next day same hour). [Act with caution].
- The 3rd line o the group is describing the necessary troops to attack with. If there aren’t enough of them available in the village , the attack will fail.
The shape of this line is as follows:
a#0b#0c#100d#0e#0f#0g#0h#0i#0j#3#
This attack line means 100 – Imperians and 3 colonists ( if you’re roman). Ofcourse it makes little sense to attack with colonists , but it can mean something if you send them as reinforcement. anyway this is other story,
- The 4th line is describing the type of troops movement and is represented by a single number that can be 2 , 3 or 4.
2 is for reinforcements
3 is for normal attack
4 is for raid attack.
- The 5th line is describing the x, y coords by the following pattern:
x=3;y=-222;
See below how the attack file should look like .
——————————————————————–
1. The file that schedules the building queue.
– /config/a1b.txt
The basic principle in configuring this file is simple. On a distinct line there should be the village’s id in the shape : $ID
afterwards , below there shoud be the buildings list for that village , on a single or multiple lines.
You can specify a building to be built be its location ID ( which must be placed alone in the line). The location ID it can be taken by clicking that building place and reading the id from the address bar.
The tags that can be used besides the building spot id are:
The name of the building in English or Romanian language . This allows you to build even level 0 of a building.
The expression auto resources or resurse auto. this must be alone on a line and automatically builds up the lowest level mine.
The expression need base resources from [village_id] , or send resources from [village_id] or, trimite resurse de la [village_id]
The result of the last expression is that towards this village , resources are being sent from the village that has the id village_id.
(The village_id must exist and belong to you and the resources must be available with also free carriers)
