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.5.3 RELEASED!   06/14/2018

      MyBot.run continues the legacy again with release of V7.5.3!!   This release supports the June 2018 game 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.5 Release


  • Content count

  • Avg. Content Per Day

  • Joined

  • Last visited

Community Reputation

9 Decent


About darwinian

  1. +1 this would be a big help.
  2. Some anti-virus software blocks modifications to this folder. If you have AV software, add exclusion for C:\Users\Pictures\MEmu Photo
  3. Same for me, but it does work. It's a little buggy and trains 1 extra troop sometimes, messing up the army comp. But it does work.
  4. ** Update 2 ** I managed to get the bot working after reinstalling Windows a second time and using fresh emulator instances instead of importing instances from other PC's. I don't know if it is related or not, but I have a new issue. Now bot can only see MEmu and MEmu_1 instances. MEmu_2, MEmu_3 and higher instance numbers are not detected.
  5. Having the same issue as some other peeps in here. Trying to troubleshoot this now, but bot isn't able to see any MEmu instances greater than Memu_1.
  6. SelectBot will open the bot, but only for default emulator (any emulator instance SelectBot tried to pass to bot is ignored) and only with last used profile (any profile SelectBot tried to pass to bot is ignored). So basically, it's the same as opening the bot directly. I seem to have no way to open the bot for an emulator instance or for a specific profile. I can change the profile once bot is opened, but can't find any way to attach it to an emulator instance. I tried MEmu and also Memu in the commands, both produce the same results as SelectBot above. ** Update ** I thought maybe something was wrong with my Windows install so I just wiped the drive and did a fresh install of Windows 10 and everything else. New bot download, new MEmu, new SelectBot download. This time with almost zero other software installed on the PC. I'm getting the same result. Nothing I try works to open the bot attached to an emulator instance or with a specific profile. This is a really strange one, I've ran the exact same setup on multiple PC's without issues. First time I've ever encountered this. Anyone else ever seen this issue?
  7. Issues with Opening Specific Profile / Emulator Instance Recently added a new PC for running multiple bots. I have 2 other PC's where everything works fine, but having some issues with the new one that I need help troubleshooting. Setup: - Win 10 x64 - Fresh AutoIT install - Running script, not compiled exe. Problem: - Bot will only open last used profile. None of the known methods for opening bot with a specific profile are working. - Bot will only open running default emulator instance (MEmu) - all known commands to open bot to run additional instances (Memu_1, Memu_2 etc.) not working. - Tried the SelectBot.exe tool. No luck. This is what I use on my other PC's without issue. - Tried command line C:\MBR_path\MyBot.run.au3 ProfileName MEmu MEmu_1 - Tried creating shortcut with target "C:\MBR_path\MyBot.run.au3" ProfileName MEmu MEmu_1 All of the above will open the bot, but only with the default MEmu instance and the last used profile. Tried with the original bot and also AIO compilation mod, both have same issues. Any tips on how to troubleshoot this?
  8. This has been happening to all my Lavaloon bots since 7.2. Sometimes it uses up a huge amount of DE before I catch it. I do not think it's an issue with any particular CSV, just some bug in the bot itself. I've seen this happen many times, but it's rare and I don't know what conditions trigger it. Closing and restarting the bot usually fixes it.
  9. Any plans to add CSV deploy speed mod again?