The following behaviors may be seen as bugs by some. The bot is actually supposed to behave this way. So, in an effort to avoid repeating ourselves, we will list them here with an explanation on why the bot behaves this way. This list is subject to updates.
Do not report these bugs! If you do, your thread will be deleted and you may get a forum warning.
Bot Window restores sometimes from minimized state, also when hiding another window it appears again.
Caused by new bot option: "Updating when minimized" (by cosote) that is by default on:
That's a tricky one, sorry for the inconvenience... This feature was introduced in MBR 6.2 and required for dock mode and Windows 7 when screen capture is done the original (still good) winapi fashion way. But also nice to watch the bot and android in taskbar's preview thumbnail window. It's like the hide Android button, just for the bot. Problem is new code and how to restore the bot window that I couldn't make any better. Two options are now available to get rid of the annoying reappearing bot window when minimized:
1. Use also the new "Hide when minimized" option (and use tray icon to show bot window again)
2. Disable the "Updating when minimized" option
Bot trains archers when not set to
This is one of the most often reported "bugs" (mostly from users who want to make the bot only donate). Simple answer: bot not designed to donate constantly, or you have wrong settings. When farming, the bot needs to keep troops training, even if the army composition is slightly incorrect. Having a couple extra archers is better than being stuck for days and losing out on millions of resources while it tries to train Giants when army camps are 239/240. If not using donate only mode; then users attempt to use 0% for total of all arch, barb, and goblin. This must equal 100% or the bot will add 20 archers to each barrack to keep the camps full. This can also happen when users force the bot to get stuck when using troops with large space, and setting the army capacity to 100%. If using GiBARCH, set the army camp to 96-97% and it will not add archers when missing one giant and you only have 4 spaces open.
Bot trains Wall Breakers or Healers or other troops not set in GUI randomly
This "bug" is almost ALWAYS due user action or PC configuration!
Are you using PC while bot is running when this happens?
Yes: When using BlueStacks or any emulator with active foreground window, bot is constantly capturing images of BS Window and sending mouse clicks or keystrokes to BS window. If you try to use PC when it needs to have control of keyboard/mouse there will be conflicts. Most time bot will take active window focus from user, and do what is needed. BUT: it can not take control if Control key is pressed, doing operations such as cut/paste or control dragging sliders with mouse. When control key is pressed you stop bot from operating.
No: You need to make sure that BS and the bot aren't overlapping. Also the Windows taskbar cannot cover BS or the bot, so users with a screen resolution lower or equal to 1366x768 must hide taskbar! You must keep your mouse out of the emulator window when it is visible. If mouse cursor is in window, clicks/keystrokes are applied to where mouse is sitting and not where they are intended.
Solution: This can not be fixed in BS even running in background mode. Use MEmu/Droid4x in true background mode, or use virtual machine like VMWare player.
Bot does not collect Loot Cart, or all obstacles even when enabled
There are some areas of display where collect code is prevented from clicking to remove loot cart or obstacles. These areas are too close to game buttons, or areas like opening of chat window. Collection of these items is disabled to stop creating other bugs. Please collect/remove manually.
Bot suddenly stopped Zooming out properly
Assuming Bot was working fully without error before, and bot shows error that zoom out is not working, AND screen is zoomed out:
Bot looks for full zoom out condition by checking for a few black pixels at very top of emulator window that are only visible when base is fully zoomed out. Zoom out detection can have problems if you base has spawned tall trees near top of your base that cover the black line expected. Solution is to remove these trees.
Assuming Bot was working fully without error before, and it is suddenly not zooming out at all:
It is possible for base layout to have black pixels in exact same location as those used to verify zoom out condition. It is rare, but it can happen. Solution: Try a different base layout. Do not forget to delete building.ini file when you change layouts to retrain new building locations.
If you are new to bot and Zoom out never worked,
Need to check/adjust your emulator installation. BlueStacks may need to have "inputmapper" file edited. Check "How To" forum for instructions. Other conditions above may also be happening, so verify