Welcome to MyBot

Register now to gain access to all of our forums and to download the latest version of MyBot for Clash of Clans. Once registered, you will be able to download our FREE bot.

  • 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
    • Fliegerfaust

      v6.5.3 Released [Fully working with December Update]   01/11/2017

      New Version which fully works with this years December Update can be found here:  

monkeyhunter

MyBot Developer
  • Content count

    2,266
  • Avg. Content Per Day

    4.7
  • Joined

  • Last visited

Community Reputation

1,350 Legendary

About monkeyhunter

Profile Information

  • Gender Not Telling
  • Location in Tree 100m next U with rifle

Clash of Clans

  • My number of bots setup: 0

Recent Profile Visitors

22,205 profile views
  1. MBR does not support Clash Royale. Best search internet for another web source. Best Luck.
  2. Old suggestion - comments: - Community user was working on a "CSV creation/edit via GUI" tool, and posted the work in MOD section. Not sure status? Development team usually does not duplicate work being done by community. Typically wait for a useful/stable release by MOD author, and then merge it into an official release. Exceptional authors get added to development team so they can personally integrate the work. - Adding a recording function is practically impossible due image capture limitations during attack. Bot On!
  3. Older versions of BS/Memu do not support new larger display resolutions. Maximum used to be WQXGA (2560×1600). Have not tested latest v2.4 BS supported display resolutions, so they may support now? Beyond using proper 1:1 DPI WIN OS setting for bot to work; you also might need to set emulator to use 160 DPI for android OS due newest versions default to 240 DPI to enable bot to "see" the emulator window properly on high resolution displays. BS internal DPI is set via registry value, Memu via its settings menu. Best Luck.
  4. ForumBot Reply: We are sorry you are having issues. Since it appears you failed to follow posting requirements for bug reports and/or help requests, we don't have enough information to help you. Note that it can take several days, maybe even a week or more before developers are able to analyze debug data and provide a response. Next time you want to post a help request or bug report, please remember to use Forums SEARCH feature, plus read the "How To" section, and the "Help & Support" section, and even the "Bug Reports" section BEFORE posting, to avoid duplicate threads Thanks for supporting your community, and Have a Bot Day!
  5. Discord has been suggested in past (especially when various PokemonGo bots had hundreds of Discord channels active). At that time, most of team was against idea of adding another communication medium? Have been inactive for last couple of months, so not sure if is still true with all new staff additions? Biggest negative is it requires a high level of moderation to be useful in organization of chaos, and we have trouble finding/keeping active moderators already? Needing to add more moderators or force current staff to support both forums and Discord would be extremely difficult. @Fliegerfaust can add more details? BTW - If you look carefully at Chat box rules, will learn chat is not intended to be organized place for discussion on Bot problems/solutions, that IS purpose of forums? Hence creating another parallel chat communication method in Discord would create more chaos for community and not less. Bot On!
  6. Another member that needs to learn/understand purpose of "Start Search IF" settings: skip down to section titled: " Trophy Drop is not working or MyBot never attacks (v6+) "
  7. MOD not really needed? Probably one of easiest code edits possible... Drop order for standard attack (non-csv) attack is located in file called "algorithm_AllTroops.au3 The drop order is found in array named "ListInfoDeploy". You can easily change the order for standard attack types. Just remember to recompile bot .exe, or run from .au3 file after changes so they are used. Best Luck.
  8. depends on TH level? Look and discuss here: https://mybot.run/forums/index.php?/forum/16-bot-settings-sharing-discussion/
  9. https://mybot.run/forums/index.php?/forum/16-bot-settings-sharing-discussion/ and
  10. This thread looks like same question/issue reported by others? My guess is a bug still exists where bot is not detecting when emulator crashes during attack search, or it is not detecting the crash issue earlier enough. Unsuccessfully attempted to get more data from another user in this thread:
  11. Current MBR OCR is part of closed source DLL that is custom code using OpenCV libraries, and there is no public usage documentation on it. (License information) Much information on OCR used by bot can be found via forums search. It has been discussed many times. Used to have AutoIt based OCR code in bot, but it was replaced with custom DLL for faster speeds in v4. Couple of foreign language troop donate MOD's were using the old method in v5? You also can find the old AutoIt "GetDigit" OCR code archived in the Github v3/v4 release archives. Best Luck.
  12. hmm.. @TripleM has error in history of Smartzap? Feature was started by developer @knowjack back in v3, but never officially released as image detection challenges resulted in only ~60-70% accuracy (wasted spells 30% time). @knowjackworked with @didipe on closed source DLL image find and provided the alpha code to @drei3000, who release 1st Smartzap feature as MOD in July 2015. Mod wasted spells on near empty drills roughly 30% of time, but it was still used by community. @LunaEclipse rewrote the code using different image find library (ImgLoc), created/tuned new drill images, and re-released several versions of the MOD. Key is @LunaEclipse version had more conditional logic to reduce the number of spells used when drills were not full. While this version almost never used spells without returning Dark Elixir, it was considered too conservative by some - leaving 1/2 full drills behind during an attack when it had spells available. Even when @LunaEclipse joined the development team, Smartzap was never officially released by development team due goal that official releases be 99% bug free and work reliably. In this developers opinion, Smartzap will likely never reach 99% reliability like dead base searching for many reasons. Biggest problems are; the small size of DE container on the drill, drill animation is constantly moving canister, and troops/heroes can block image. The creation of NoobZap is relatively new MOD to SmartZap code. Noobzap is hilarious concept for those that know the above history. It primarily removed all the reliability enhancements added since 2015 to reduce number of wasted spells, returning feature to original elixir wasting poor accuracy available back in v3. Bot On!
  13. ForumBot Reply: We are sorry you are having issues. Since it appears you failed to follow posting requirements for bug reports and/or help requests, we don't have enough information to help you. Note that it can take several days, maybe even a week or more before developers are able to analyze debug data and provide a response. Next time you want to post a help request or bug report, please remember to use Forums SEARCH feature, plus read the "How To" section, and the "Help & Support" section, and even the "Bug Reports" section BEFORE posting, to avoid duplicate threads Thanks for supporting your community, and Have a Bot Day!
  14. @HArchH The AutoIt recursion error is secondary error. Have seen this kind of strange error before. There is an earlier error that started the chain of events to lead to code recursion fault and never recover. Based on log; initial problem may have been failure to detect reload message, it could of been just before it got stuck in the failed detection loop, or it could be problem that code is not waiting for CoC restart before it continues? Need: 1- SEE the image of emulator window (captured with photo button in .png format) to help figure out why the reload error message was not detected, or what was forcing code into the recursive loop? 2- Full debug log that shows all the extra Android log messages during restart process. Bot On!
  15. in my humble opinion, need to find and fix bug related to bot not properly detecting when CoC has randomly closed? This "bug" is happening everywhere, not just when stuck in clouds searching in higher leagues. Log snippet above is not enough to tell the story and leads one to a false conclusion based on what I have experienced? Does your log show waiting 1, 2, and/or 3 minutes; THEN finally begin the CoC restart process? How long does it take for CoC to reset/start, another 3.5+ minutes? or more? The only reason one would want to reset earlier, is if they have the dreaded "Random closing CoC" issue, and the CoC app restart time is not less than 5 minutes, and your base is getting attacked? Hmm...Maybe need a bug report, and not a MOD request? FWIW - Waitforclouds is fairly complex process in code: - every 250ms it checks screen for one of common error reload messages - every minute it reports total waiting time - every random 2-3.5 minutes it does a full set of checks of emulator window to determine if CoC app is still active: -- Looks for proper text on screen during search via OCR -- Looks to see if clouds are gone -- Looks for Personal Break message text -- Looks for 30 minute search has failed text message -- AND Looks for chat tab, opens chat window, closes it, and then keeps waiting. : If tab is found and window open/closed properly (which is checked by verification of OCR on screen text) then all is well. : If there is an error during this keep alive check, then it should reset the search, and restart CoC app. Since there is 5 minute grace timer, the 2-4 minute wait time for keep alive should be ok, and when CoC randomly closes it gets detected during the keep alive check process. So what is problem? Not completely sure, yet. There are a combination of "random" items creating the problem: CoC closing unexpectedly, searching in clouds, and app restart process...... One ugly band-aid fix is to shorten the random wait times, or use hard coded value of 1 minute? Another band -aid fix is to add another OCR check for screen text to the code as part of the 1 minute reporting loop? Change WaitForClouds: If chkAttackSearchFail() = 2 Or chkAttackSearchPersonalBreak() = True Then to: If chkAttackSearchFail() = 2 Or chkAttackSearchPersonalBreak() = True Or chkSearchText() = False Then This patch will catch if CoC has closed a little bit sooner at cost of adding 1/2 second to loop time. NOTE - will likely find that it still takes a long time to restart CoC and you still get attacked? The real problem appears to be in emulator/CoC restart process? Team is in process of tracking down the reason for late detection of "CoC closing randomly" event. Hopefully, this can be improved/fixed soon. Bot On!