This bot farms barbarian villages in Tribal Wars 2. It automatically detects barbarian villages, available troops and configured army presets to attack.
- Automatically reads the required information from the game: Locations of farms, available units, army presets, current attacks per village, etc.
- Use the in-game army presets to configure which villages should attack and which units to use.
- Requires no input focus: You can continue using your PC as usual while the bot runs in the background.
- Fast enough to send 800 attacks per hour.
- Supports multiple army presets per village to make the best use of your troops.
- Takes into account the limit of 50 attacks per village.
- Option to avoid barbarian villages under a certain amount of points.
- Avoid having your troops die at remaining walls: Option to avoid barbarian villages with specific coordinates.
- Supports running on multiple accounts simultaneously on a single PC.
- Supports random breaks between farming cycles.
- Uses a normal web browser to interact with the game server for maximum security.
- Stops the farming when the configured time limit is met to avoid perpetual activity on your account.
This video shows the process of starting the farmbot and setting up your Tribal Wars 2 account:
To start the farmbot, download the executable file from https://botlabs.blob.core.windows.net/blob-library/by-name/tribal-wars-2-farmbot-2021-08-23.exe and then run it.
The first time you start the bot, it will download a web browser component. This can take some time, depending on your internet connection.
When the browser download is finished, the bot opens a 'chromium' web browser window, which is a variant of googles chrome web browser. In the Windows taskbar, it appears with an icon that is a blueish version of the google chrome logo:
In the browser window opened by the bot, navigate to the Tribal Wars 2 website and log in to your world so that you see your villages. Then the browsers address bar will probably show an URL like https://es.tribalwars2.com/game.php?world=es77&character_id=12345
Now the bot will probably display a message like this:
Found no army presets matching the filter 'farm'.
Or, in case your account has no army presets configured at all, it shows this message:
Did not find any army presets. Maybe loading is not completed yet.
In any case, we need to configure at least one army preset before the bot can start farming.
The bot only uses an army preset if it matches the following three criteria:
- The preset name contains the string 'farm'.
- The preset is enabled for the currently selected village.
- The village has enough units available for the preset.
If multiple army presets match these criteria, it uses the first one by alphabetical order.
If no army preset matches this filter, it switches to the next village.
You can use the in-game user interface to configure an army preset and enable it for villages:
Besides the army presets, no configuration is required. The bot searches for barbarian villages and then attacks them using the matching presets. You can also see it jumping to the barbarian villages on the map.
In the console window, you can read about the number of sent attacks and what the bot is currently doing:
[...]
Session performance: attacks sent: 129, coordinates read: 1478, completed farm cycles: 1
---
Sent 129 attacks in the current cycle.
Checked 1413 unique coordinates and found 364 villages, 129 of wich are barbarian villages.
Found 3 own villages.
Current activity:
+ Currently selected village is 871 (482|523 'Segundo pueblo de skal'. Last update 6 s ago. 537 available units. 11 outgoing commands.)
++ Best matching army preset for this village is 'farm beta'.
+++ Farm at 567|524.
++++ Send attack using preset 'Farm 1'.
[...]
When all your villages are out of units or at the attack limit, the bot stops with this message:
Finish session because I finished all 1 configured farm cycles.
All settings are optional; you only need them in case the defaults don't fit your use-case. Following is a list of available settings:
number-of-farm-cycles: Number of farm cycles before the bot stops. The default is only one (1) cycle.break-duration: Duration of breaks between farm cycles, in minutes. You can also specify a range like60-120. The bot then picks a random value in this range.farm-barb-min-points: Minimum points of barbarian villages to attack.farm-barb-max-distance: Maximum distance of barbarian villages to attack.farm-avoid-coordinates: List of village coordinates to avoid when farming. Here is an example with two coordinates: '567|456 413|593'. This filter applies to both target and sending villages.farm-player: Name of a player/character to farm. By default, the bot only farms barbarians, but this setting allows you to also farm players.farm-army-preset-pattern: Text for filtering the army presets to use for farm attacks. Army presets only pass the filter when their name contains this text.limit-outgoing-commands-per-village: The maximum number of outgoing commands per village before the bot considers the village completed. By default, the bot will use up all available 50 outgoing commands per village. You can also specify a range like45-48. The bot then picks a random value in this range.
To configure settings, open the configuration page at https://catalog.botlab.org/8881e86b0ce82d9da6b4a5f89234a6406cc0c067ca2666f4c31f0982029e25ee in a web browser.
On this page, scroll down to the button Configure bot.
Click this button to navigate into the configuration interface:
Here we have multiple input fields, but to use any of the bot settings mentioned above, we only need the input field right of the --bot-settings label.
When using more than one setting, start a new line for each setting in the text input field.
Here is an example of bot-settings for three farm cycles with breaks of 20 to 40 minutes in between:
number-of-farm-cycles = 3
break-duration = 20 - 40
Use the button Download script with this command line to run the bot to download a script to run the bot with the entered settings.
When you have applied settings for multiple farm cycles, the bot displays this message during the breaks between farm cycles:
Next farm cycle starts in 17 minutes. Last cycle completed 16 minutes ago.
You can test the bot for free. When you want the bot to run more than 15 minutes per session, use an online session as explained at https://to.botlab.org/guide/online-session
Online sessions cost 2000 credits per hour. To add credits to your account, follow the instructions at https://reactor.botlab.org/billing/add-credits
For more about purchasing and using credits, see the guide at https://forum.botlab.org/t/purchasing-and-using-botlab-credits-frequently-asked-questions-faq/837
To make it remember the farm locations, configure the number of farm cycles to be at least two. The bot automatically remembers all locations of barbarian villages within the same session, so it can reuse this knowledge, starting with the second farm cycle. It sends only one attack per target per farm cycle, so the remembering does not affect the first farm cycle. If you don't use any configuration, the bot only performs one farm cycle and then stops.
Sending one attack takes less than four seconds. The bot can cover 800 farms per hour. The first farm cycle per session is a special case: For the first cycle, it needs additional time to find the farm villages. The game limits us to 50 concurrent attacks per village, and the bot switches to the next village when the currently selected village hits that limit. One farm cycle is complete when all your villages are at the limit, either because of the attack limit or because no matching units are remaining.
To select multiple player characters for farming, use the character-to-farm setting name multiple times. Here is an example of a complete bot-settings string with multiple character-to-farm:
number-of-farm-cycles = 36
break-duration = 30 - 60
character-to-farm = player character one
character-to-farm = player character two
character-to-farm = player character three
There is no limit to the number of characters here, you can add as many character-to-farm as you want.
Start a new instance of the bot for each account. This separation also means the instance configurations are separate. For example, you could assign each instance another break duration.
To use multiple instances simultaneously, you need to expand the bot-settings in the configuration of each instance. When the bot starts, it opens a new browser window and will also close other browser windows. To avoid it closing the browser window of another instance, we need to assign it a scope of browser instances in bot-settings explicitly.
To configure this scope, use the new web-browser-user-profile-id bot-setting like this:
web-browser-user-profile-id = profile-beta
While running, the bot displays the profile ID, so you can check that each running instance has a unique value:
Note that browser state like bookmarks and cookies belong to that web browser profile. That means you need to log in to the game for each new profile that you create.
If you have any questions, the BotLab forum is a good place to learn more. You can also contact me at support@botlab.org
When asking for help with the bot, include the complete text from the console window or a screenshot. Make sure screenshots are well readable. Don't try to insert a screenshot directly into the forum, as it will be compressed and unreadable. When posting on the forum, you can link screenshots hosted at other sites like Github or imgur.