Jump to content

Donsch

Official Tester
  • Content Count

    15
  • Avg. Content Per Day

    0.1
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Donsch

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Weird issues running multiple bots at the same time The symptom: The running bot seems to interact with all other windows, especially if background mode is checked. To be sure if this is your symptom, while running the bot in docked mode, the attached bot screen would constantly flicker between folded into the emulator and out to the side again. I couldn't use any other program while the bot was running, because the cursor was constantly being hijacked. However, in the end, the conflict was most likely a conflict with emulators. I suspect people experiencing this issue have installed many other emulators over a long period of time. The solution: (that worked for me) I also had Oracle's Virtualbox installed, so went to C:\Program Files\Oracle\VirtualBox from a command prompt and ran ".\vboxmanage list vms" which showed some VM's with an "unavailable" status. Then I ran .\virtualbox unregister [uuid] where uuid was each VM that showed to be unavailable from the previous command. A uuid looks like this: da298e62-d6f6-4e83-a8ca-918d5b9b6f00 At this point, my Memu VM's disappeared (but should have been unrelated to above), so now to get Memu's showing up again, go into C:\Program Files\Microvirt\MEmuHyperv and run MemuHyperV.exe This may be in another Memu folder, and if you don't have it, you can download it separately. Also known as MemuManager. From this utility, you select ADD Existing, and navigate to where the Memu VM's are stored, mine were at: "C:\Program Files\Microvirt\MEmu\MemuHyperv VMs" in folders named Menu, Memu_1, Memu_2, etc... After adding Memu VM's back, you need to log out of Windows and back in, a reboot was not required. The above steps removed what I believe was a conflict between Memu and Vbox, which probably stemmed from trying so many things in the past. I hope this helps someone else.
  2. Donsch

    Memu loses Wifi on a predictable pattern

    I finally got this fixed and it had nothing to do with the bot, but was probably caused by trying many versions of Menu and other emulators. I'm not sure if this will help, but here is what I did. I also had Oracle's Virtualbox installed, so went to C:\Program Files\Oracle\VirtualBox from a command prompt and ran ".\vboxmanage list vms" which showed some that were "unavailable" status. Then I ran .\virtualbox unregister [uuid] where uuid was each VM that showed to be unavailable. A uuid looks like this: da298e62-d6f6-4e83-a8ca-918d5b9b6f00 At this point, my Memu VM's disappeared, so now, go into C:\Program Files\Microvirt\MEmuHyperv and run MemuHyperV.exe This may be in another Memu folder, and if you don't have it, you can download it separately. Also known as MemuManager. From this utility, you navigate to where the Memu VM's are stored, mine were at: C:\Program Files\Microvirt\MEmu\MemuHyperv VMs in folders named Menu, Memu_1, Memu_2, etc... After added VM's back, you need to log out of Windows and back in, a reboot was not required. The above steps removed what I believe was a conflict between Memu and Vbox, which probably stemmed from trying so many things in the past. I hope this helps someone else.
  3. Same here, still get the error after the VillageSearch.au3 edit and recompile.
  4. Donsch

    ANY Siege Machine option

    ANY Siege Machine option Currently, there are options to use only CC troops, or to select a siege machine to use. It would be great to add one more option to use ANY siege machine. As it is now, if you have it set to wall wrecker, but get donated something else, it will not use that siege machine locking it into your CC until you discover what happened and either manually burn the siege or switch the bot to use the donated siege, only to switch it back again. This option would also play well into the requests that our clan tries to do during non war time, which is to ask for "any/any/any" , for troop./spell/siege thus, whatever is in stock and no waiting for a special order. Thanks
  5. Donsch

    Memu loses Wifi on a predictable pattern

    Background mode is checked and has always been checked. It is the default mode for the bot. Mitch, you got me to thinking. what would happen if I UNCHECK the background mode and guess what? That fixed it. maybe the logic of the check box got messed up in the update? In fact, I was doing several things at once without any problems and the problem started again after a while. However, when I looked at the bot, it switched accounts and the profile for that account still had the background box checked. I unchecked it and like magic, the interference stopped again. Another pattern emerges.
  6. Donsch

    Memu loses Wifi on a predictable pattern

    I have more to add that might be related to this issue. It took me a while to figure this one out. When running the bot, it is affecting every other window open on the computer. It flickers Excel so I can't type in cells, it affects the web browser, where I had to stop the bot just to type this message. This now make sense as to why running multiple bots is causing so much grief. Each instance of the bot is affecting the other instance, they get confused and I've seen a bot issue commands to the other bots VM, the other bot detects an unexpected action and restarts the VM again. When I run in docked mode, the bot constantly slides in and out of the VM like a flicker, probably related to anything it tries to do. Even in docked mode, all other windows are still being acted upon. If I have NOTHING open but the bot, it definitely works better, but as soon as I start using the computer for other things, weird things start happening to every open window. If I stop the bot, ALL the weirdness also stops. I can reboot my computer and it seems fine for a little bit, but doesn't take long to revert to the behavior described above.
  7. Memu loses Wifi on a predictable pattern First let me preface with, I'm not sure what is causing this. But I have observed a solid pattern and at least have something to report. Secondly, I never had this problem before the update, and third, I blew away all the Memu VM's and remade them from a known good backup that is several months old. Importing this master ova has fixed past problems with Memu, but nothing is working this time. Here is the pattern. The bot skips bases until it finds a target, it is after the target is found that some zooming operation happens and all of a sudden the flashing wifi bars appear on the screen. There is no recovery from this, the only way out is to stop the bot, close Memu, and restart the bot. It doesn't do it every time the bot finds a base to attack, but EVERYTIME this happens, the bot just found a base to attack. If I had to guess, I'd say the bot probably runs find for an hour or two before this happens, while I have it setup to switch between 2 or 3 accounts per bot. I actually blew away all the VM's a few times now thinking something is wrong with the VM, but with a solid pattern identified, I'm started to think the bot is causing this somehow. I also found a post about putting in a known good DNS entry instead of using AUTO, and I did that as well, which had no effect on the issue. Regards,
  8. Donsch

    Cloud Rant... and solution.

    My account that is over 5500 trophies is not one that I use the bot on. I use the bot to farm on TH8 - TH10 villages. It does work on the TH11 okay, but out of all my villages the TH12 is the one I can't risk losing, so just don't bot with it..
  9. Donsch

    new to MyBot

    new to MyBot Hello fellow botters, I'm pretty new and I just got everything setup and running before the update hit. Oh well, it was bound to happen to somebody and I'm probably not the only one. This seems like a nice community. I have one question about the chat. It says I don't have permission to chat. Is there something I need to read to activate the chat? Thanks,
  10. Donsch

    Cloud Rant... and solution.

    The kicker is, when you finally get a base to attack and get over-zealous (and win), you make your problem even worse. You can't get to 6000 trophies fast, and you sure can't come down from that level fast. It could take a couple days to get back down to 5000, lol I'm currently stuck @ around 5600, no attack all day.
  11. Donsch

    New collector lvls

    I would second this. I have watched the bot pass over bases with 800k+ E and G, and 7k DE, saying base is not dead, when all collectors are completely full. The pattern seems to be that the bases that are being passed over have the upgraded collectors to level 13. Another interesting thing about this, is that the bot seems to know there is a problem. It said something to the effect of taking a debug screenshot because of high resources and not expecting it to be a dead base. The folder called skipped zombies has lots of screenshots in it, most of which have pretty full collectors. I can upload one if that will help, but the idea is that the bot probably doesn't seem to be recognizing level 13 collectors.
×