How does the auto attack cycle work?
After village maintenance, GameBotOps opens attack search, reads the loot on screen and attacks an opponent that meets the thresholds. It uses visible troop, hero, siege and spell cards according to the current battle state, then returns home after the result and supported event rewards.
The account does not change after every attack. Collection and upgrade checks continue on the same account; handover depends on the working mode, resources and turn limits.
Target search and loot thresholds
A target must meet all minimum gold, elixir and dark elixir values. Unsuitable opponents are skipped and the change of opponent is verified on screen. Unreadable loot is not treated as sufficient. See the farm bot page for details.
Heroes, siege machines and troops
Deployment starts with heroes other than the Grand Warden, followed by siege machines, army and event cards, then the Grand Warden. The bot rescans visible active troop cards and verifies that a card is depleted or gone before moving on.
Temporary event troops and high-quantity cards are included. Deployment is not considered complete after a fixed number of taps per card. Cards off screen or hidden behind horizontal scrolling are outside the visible-card guarantee.
How are spells used?
Spells can begin after the first verified troop deployment. Rage targets a dense live army cluster in the current image; Freeze targets defences identified during scouting and verified again at the moment of casting.
Other visible spell cards also require a verified target. A spell may remain unused if no reliable target is found, and that state is reported in the live feed. Battle outcomes and three stars are not guaranteed.
Battle speed and post-battle rewards
When the 1x speed control becomes visible in a live attack, the bot attempts to switch to 4x and checks the result on screen. It then handles the return home or supported reward flow when the battle ends.
Chest openings, card packs, three-choice rewards and temporary event armies are described on the event support page.
Attack automation coverage
The bot works with attack cards that are present and visible in the game. Automatic army production, barracks or spell factory production queues, and a separate trophy-focused target mode are not current features.
A recognised shield or confirmation dialog may be accepted when entering an attack. A separate shield-preservation plan should not be assumed.
Updates and interruptions
When a required game update is detected at startup, the bot follows the update and return-to-game flow on the official Google Play listing. Recognised introductory dialogs are dismissed and the village view is prepared. This does not mean completing every training task on a new account.
If search fails to open, the bot can retry and recover the game on the same account. If game and emulator shutdown cannot be verified during handover, the fleet waits. These states are visible in multi-account management.
Account-use limitations are explained on the ban risk page.