Jump to content
  • Announcements

    • Fliegerfaust

      Malicious and Banned Links   10/09/2016

      Please be careful of downloading ANY LINKS that are not originating from a MyBot.Run URL or another trusted URL (such as apkmirror.com, bluestacks, memu, xda-developers, etc).   We have banned ALL telegram links and other verified malicious links we have come across already. Users attempting to do this or get around this ban will be banned permanently.   Please report ANY suspicious links to MyBot Staff or pm me directly
    • monkeyhunter

      MyBot.run V7.3.1 RELEASED!   11/03/2017

      MyBot.run continues the legacy again with release of V7.3.1!!   This release supports the May 22 SC game update & August 4th Graphic Update, and has some new features hidden inside as well   Get your copy in thread below!!   Click here to get to the release thread MyBot.run v7.3.1 Release


MyBot Developer
  • Content count

  • Avg. Content Per Day

  • Joined

  • Last visited

Community Reputation

1,497 Legendary

About cosote

Profile Information

  • Gender

Clash of Clans

  • My Town Hall Level(s):
    Town Hall 11
  • My number of bots setup:
  • Botting since:

Recent Profile Visitors

14,949 profile views
  1. Usually bios virtualization setting, Hyper-V support enabled in boot config or Anti-Virus messing with virtualization... Just check those and you likely find the one causing it One question: are you running also as many bots as Android, like 30/40 per system? In normal bot GUI mode, or mini mode? Clash ON ! ! ! Cosote.
  2. BS 3.50.x is supported in next version
  3. Damn BS3 should run fine with bot, testing latest version right now Cheers - Cosote.
  4. Bot doesn't work with Nox when computer screen size is low, like 768 pixel of height... sorry couldn't find a solution yet Even the fixed size option in Nox is not preventing Nox to be too small. I will add a work-a-round in one of next version of the bot, where bot will use screencap mode and "translated" mouse coordinates for clicks. Cheers - Cosote.
  5. Memu annoying trending app running

    Also my advise: Use bot Android option to install Nova Launcher
  6. I saw multiple reports like that, but could not reproduce. Very important is you report the exact, detailed Android version with your problem. Also, include the log file (and if screen related, the png of the Android screen using bot's photo button). Soon, bot will get more & better "GUI" support to select, verify existing/installed Android emulators and its available instances... Till then use @Fliegerfaust's tool to select the right Android/Instance or simply use command line parameter as described with calling MyBot.run.exe /? or in many other sources here. Most likely newer Android versions are not detected (though that happens very rare), but the bot is supposed to be relaxed with these settings... let me try to explain how Android detection and choosing the one bot uses works... Be warned, it's a little complex If you do specify the 2 or 3 bot parameter: VillageName AndroidEmulator InstanceKey, e.g. MyVillage MEmu MEmu_1 or MyVillage BlueStacks2 or ... no Android validation is done and the specified Android Emulator and Instance is used. If the 3rd parameter is not specified the default is used, see more details in file COCBot\functions\Android\Android Status & Information.txt If you have no existing profiles (like a fresh new bot install) and run the bot without any Android parameter, the bot detects any supported installed emulator and uses first found in this sequence if no support Android is currently running!!! 1. MEmu 2. BlueStacks2 (that includes also BlueStacks3) 3. BlueStacks 4. KOPLAYER 5. LeapDroid 6. iTools 7. Droid4X 8. Nox (This sequence will change soon to Nox, MEmu, BlueStacks2, BlueStacks, iTools, KOPLAYER, Droid4X, LeapDroid) Once a profile exists, bot saved the Android and Instance also in its config.ini file, so if you launch bot again without parameter, it will use the same as before. Now, if any support Android is running in a new bot without any profiles, bot checks if it can use it and does so (reboots Android if sth. isn't right). New version of bot will detect not only existing Android Emulator but also checks for available instances and helps you in that part and also tells you more/better information when it cannot be used. Hope this helps a little bit - Cheers, Cosote.
  7. Memu keep restart

    hmm, looks like a bug in the mod ... try using the DirectX (WinAPI) mode of Android and bot Android options... Then no screencap images are created... only works with newer version of MEmu (and of course in Nox, BS/BS2/3 and some others)... Cheers - Cosote.
  8. Waiting for main screen error looping

    Please post/send me your log file when that happens including a png of the android screen using the bot photo button. Then I can immediately check and include fix in next release, if it's a bug or relatively easy to "improve" If you don't want to post it here - just send me a PM with details / logs / image. Sure to fix it quickly with you help Cheers - Cosote.
  9. v7.3 : Window z-order issue?

    Thx, that's a new thing - will be fixed in next release... Cosote.
  10. alright, then simply use these commands to persist Nova Launcher as default: mount -o rw,remount /system for f in /system/app/launcher_*_en_signed.apk; do mv $f $f.bak; done Cheers, Cosote.