Tribalwars Bot / Attack planner
Tribal Wars automation
Plan the operation once. Every command leaves on time.
Nukes, noble trains, fakes and support across all your villages in one plan. Build it yourself or let the bot draft one for you to review. Approve it and the bot sends every command at its scheduled moment.
From targets to an operation plan
A Tribal Wars attack planner has to connect three decisions: which village can supply the troops, which target those troops should reach, and when they need to arrive. A target list alone does not tell you whether a village can make the timing or whether its troops are already needed elsewhere.
Tribalwars Bot brings fakes, fangs, nukes, noble trains and follow up support into an operation plan. You can build the plan yourself or use automatic planning, then inspect the individual legs before approving it.
What to check before approving
Targets and sources. Check the destination coordinates and the village assigned to each attack. Make sure the proposed targets match the operation you want to run.
Troops and purpose. Review the unit composition of each leg. Fakes, clearing attacks, noble trains and support do different jobs; check that the proposed sequence matches your plan.
Arrival and departure times. Review the landing order and the sends required to achieve it. A source that cannot reach the target in time needs a different assignment or a later arrival.
Approval. Generating a plan is the review stage. Approve it only after checking the sources, units, targets and timing; approval makes it eligible for scheduled execution.
Noble trains and supporting attacks
A noble train needs more than a count of noblemen. The escort, preceding attacks and follow up support have to fit the operation as well. Tribalwars Bot plans these legs together and works their departure times back from their intended landings.
The noble planner can account for noblemen still in production when deciding what is available for a plan. That does not make an unfinished unit available now: the production and travel times still need to fit the intended arrival.
Review the resulting order for each target. A generated schedule is a proposed operation, not a promise that a target will be conquered.
How planning connects to sending
After approval, Tribalwars Bot schedules the operation against the server clock and holds its source villages so other modules do not spend the assigned troops. This connects the plan to the same bot that handles your routine village work.
Execution still depends on your PC, browser session, connection and game state. Keep the machine awake and monitor the operation; a plan cannot guarantee a successful send or a battle result.
For repeated resource collection rather than a coordinated operation, use the separate Tribal Wars farm bot guide. For resources and minting, see market automation.
Try it with your account
Seven day trial with all features
Tribalwars Bot runs on Windows 10 or 11 with Google Chrome. Keep your PC awake and the bot running while it works. Start your seven free days after validating your game account. No card is required. Sending planned operations is part of the Full plan: $29.99 USD per 30 days, paid manually in Bitcoin or by PayPal with no automatic renewal. On the Basic plan you can still build and review a plan.