monkeyhunter

What is "Best" Emulator? There is constant debate about "What is best emulator?" Even among developers! "Best" is relative question and depends on many factors: with hardware available and actual use requirements being dominate factors. More useful questions to ask are: What emulator is: - best for limited resource PC? - best for multi-instance? or maybe - easiest to setup and use by newbie? First: Easiest to install and setup by Newbie! ALL emulators are packaged by creators to be easy with auto installation! For majority of PC hardware, MyBot.run will auto set the required emulator window size for image detection to run as designed and use does not need to change anything. The challenges occur when PC hardware or configuration require changes for emulator to work with MyBot.run farming bot. So there can a couple problems with easy setup, that are easy to solve: [and are well documented in these forums] >> Memory limitations: >Running ANY emulator without lag requires about 2GB system RAM per instance. Some require less, but you still need RAM for OS to run without lag too. Anyone with less 4GB of system ram may have lag issues. : Solution: Set limit on memory use allowed by emulator, recommend 512-640MB maximum. Bluestacks requires editing registry, Memu requires custom settings on config panel. >> Display size limitations: >Bluestacks does not support full background mode, like other virtual box based emulators. [fakes BG mode by hiding window off screen, hehe] This means NOTHING is allowed to overlap the BS window (mouse, other windows, etc), or bot fails to operate as designed. : Solution: Use a minimum display resolution of 1366x768 with task bar hidden, or minimum standard resolution of 1440x900 with task bar always visible. Plus keep mouse out of BS window even when using Background mode, or use Dock mode. > Memu has internal feature to auto-size the window which will attempt to over ride MBR display size settings on PC with display resolution of less 1366x768. : Solution: Include hide the Windows task bar to stop Memu resize, and/or change Memu internal settings and force window resolution. >> Anti-Virus (AV) Program Compatibility: >All emulators store large virtual disk (VDisk) files on PC. Any installed AV program with real time scanning will constantly be checking these files and can slow emulator performance. :Solution: Exclude the emulator VDisk files from within AV program. > Some AV hook into the virtualization and significantly reduce Android performance. :Solution: Avast users may have problems, unless you disable hardware-assisted virtualization in troubleshooting section of Avast. >> Hyper-V virtualization Compatibility: Hyper-V virtualization support must be disabled with bcdedit. If Hyper-V is enabled, Virtual Box based emulators (all except BS1) will have lag issues, or may not even install/run. Second: What emulator uses least amount of resources? (and which run's best on MY PC) Here are typical rankings of resources required by supported emulators based on miscellaneous pile of random developer data: A >> PC more than 3 year old, SINGLE instance: #1 = BS v0.10.7 un-rooted set to 512MB memory >> lowest resources, fastest running, fewest issues #2 = Memu v2.5 - v2.86 >> if PC is more than 5 years old, may not support required virtualization and will have lag, v2.5 recently started having random wifi issues with CoC servers Note: If Memu runs without lag on your older PC, difference in resources required between #1 & 2 is less than 15%. #3 = BS v2.2 rooted set to 512MB memory or Nox or Droid4x >> About same, all work, but amount of lag depends on hardware when above have issues B >> PC less than 3 years old, SINGLE instance: #1 = BS v0.10.7 un-rooted set to 512MB memory >> lowest resources, fastest running #2 = iTools >> if you can get past Chinese only setup, works well #3 = LeapDroid >> not recommended due being discontinued, no new versions, future support limited #4 = Memu v2.86+ >> requires proper BIOS Vtx virtualization setting for best performance, older versions started having CoC server wifi issues lately. Note: difference in resources required between each of above is less than 10% overall. #5 = BS v2.2+ >> Easiest install/setup, higher resources than above #6 = Droid4x >> supported, but not recommended due overall speed, and various random issues with version updates #7 = NOX >> Supported, but not recommended as it has minor annoying problems due different control mechanisms than other emulators supported. C >> Less than ~3 year old PC with multi-instance required: #1 = iTools >> if you can get past Chinese only setup, lowest resources for multi-instance #2 = LeapDroid >> not recommended due being discontinued, no new versions, future support limited #3 = Memu v2.5 thru v2.86 >> fewest issues with setup/config, v2.5 recently started having random wifi issues with CoC servers Difference in resources required between 1, 2, & 3; is small, well less than 10% between 1 & 3. #10 = Nox or Droid4x > both will run multi-instance, but require significantly more resources than above. Note: resources required are higher when using more than 1 brand of emulator with multi-instance. Try to use all same brand. D >> Multi-instance with PC older than 4 years old: #1 = Run one native BS v0.10.7 un-rooted set to 512MB memory and run other instances inside VMWare Player v7.1.2+ (not workstation product which uses more resources) with Tiny7, each running same BS v.010.7 #2 = Run different emulators - BS v0.10.7 un-rooted set to 512MB memory >> lowest resources, fastest running, fewest issues - Plus up to one each of Memu, Nox, Or Droid4x that runs on the older PC If having lag issues with multi-instance set up, read this post to learn areas that may need optimization in your system. Final comments: #1 - If you need information about one of the emulators listed above, or want information on how to optimize performance for them; please search the forum for answers. This thread is not for discussing how to use different emulators. There are specific threads for each emulator type where this is discussed! #2 - This rank list has averaged data in it. There will always be hardware configurations that will use more/less resources to run specific emulator version, and can be more highly optimized to run one emulator better than others. For emulators where resource requirements are very similar, the ranking on highly optimized hardware may be little different. But, the top 2-3 will still be the top emulator choices. #3 - The rank order list is constantly being attacked from every direction, and comparing data on it can be like comparing apples to oranges. - Every time a new emulator version is released, it can be faster/slower which will change ranking slightly. - Development team is constantly working to improve and optimize emulator management to get best performance from each one. #4 - Above ranking is subject to change without notice and change at random times as decided by magic leprechauns that make up these lists.

How To Download MyBot.run Clash of Clans Farming Bot Thank you for asking how to download MyBot.run!! Current official bot release and download links can always be found in Official Releases forum section. Having problems? If you have issues and the GitHub links in current release thread do not work for you, then you may have a local network or PC issue that needs to be fixed? 1) Have you used another CoC bot before finding MyBot.run? Oops. No problem! Some copy cat bots that steal MBR code, and offer it for sale will perform a HOSTS file HIJACK. This will block your PC from reaching GitHub (and sometimes MBR forums). Your favorite search engine can show you how to check and edit your HOSTS file for your Windows OS version, here is one example site. While very rare, some older web browsers can also be hijacked to block websites. To fix this you need to clear your entire browser history (only works after other CoC bot is removed from system). 2) Do you have internet filter or firewall at your location? Since GitHub is public site, and there can be any kind of software available for download (including hacking tools); Some countries and corporations will block GitHub. If you are trying to reach GitHub behind one of these firewalls, then either need to use VPN, or some other internet location to bypass the blocking filters. 3) Is download blocked by Anti-Virus (AV) program? The bot is not a virus. It is made with a scripting language named AutoIt, which is sometimes used by people to create malware. This causes antivirus programs to mark ALL AutoIt programs as viruses, even if they don't harm your system. The AutoIt code of the bot is freely available; you can look through it and compile it yourself if you are worried. Need more information? Read this from people who make AutoIt language used to create MBR: https://www.autoitscript.com/wiki/AutoIt_and_Malware If the bot is detected by your antivirus software: create new folder to store MBR download zip file, add the folder to your antivirus exception list/whitelist and download/extract the bot to that same folder. 4) Are files missing from your download? When visiting GitHub site to download MyBot.run and not using the .zip download links in our release thread, beware that you may not be downloading the proper branch of repository. Our master branch is only used to store version files to notify users for new releases. A zip file with latest release can always be found on releases page of GitHub. Another missing file issue can be your Anti-virus software removing files from zip file, or deleting them when extracted. Read #3 for more information regarding AV problems. General Information: MyBot.run uses GitHub software sharing site for all software releases with community. Our GitHub repository top level is here > https://github.com/MyBotRun/MyBot On this site, you find newest and all past releases by development team. Our repository even has a Wiki with installation, licensing, and History of MyBot.run. The Github repository is primarily used as our download library and is not open for public editing. All problems/issues/bug reports are only supported via this web forum. Thanks for supporting your community!

There is only 1 reason: Android game CoC has graphics display problems after it has been running successfully for awhile and/or Android emulator display is completely Black when first started and/or Android emulator has black squares/blobs where buildings or troops are supposed to be: Not enough memory available inside Android emulator OS to render the display!!! There are several items that can create these "out of memory" problems: 1) You have OLD graphics drivers. Intel internal HD graphics and Nvidia GPU have most problems reported. You must have the latest hardware drivers for your GPU. If using Intel HD graphics, then must have latest motherboard chip set drivers downloaded directly from Intel site also. Sometimes updating drivers will completely fix the display issue and do not need make any further changes. (see possible problem #2) 2) PC has limited resources. Any PC with less than 4GB RAM AND 1GB video RAM (on separate GPU card) may experience this issue. PC with Internal GPU usually see this problem more frequently due a portion of system RAM is allocated to GPU and you have less RAM available for programs. Solution: Edit the maximum RAM setting inside emulator to 500MB. Editing BS RAM value is shown here: https://mybot.run/forums/index.php?/topic/15222-tutorial-how-to-mod-bluestacks/ Memu users need to edit settings in Memu control pane 3) Bot version you are use has memory leak. There were several issues with improper use of _screecapture2() in V5 code, that were fixed in V5.3. There are still some MOD bots using this bugged code (problem was constantly increasing GDI handle counts in system due improper deletion of no longer used memory). There are some MOD authors even creating new code with new memory leaks. Note - Users with more than 6-8GB of free memory, may not witness the memory leak for several days or week+ of running bugged code, so MOD author that is constantly closing and restarting his bot may never see the problem and know to fix it. Solution: Use the latest original developer release. 4) Emulator Bug. Emulators are programs written by humans, that can have bugs. Some emulator bugs are configuration dependent (CPU type/GPU type/BIOS/drivers/etc). If you are using an Android emulator inside a simulated OS (such as a rented Virtual Private Server, or Virtual Machine like VmWare Player), there is an extra layer of software between emulator and your PC. This extra translation layer can create bugs/issues, and these can be configuration dependent also. Example - I have one 7+ year old Intel Quad Core PC with an old Nvidia 400 series GPU that has memory leaks in BS when inside a VM, but normal instance in OS has no issues. Another PC of same type/vintage has a Radeon GPU and has no problems? All of these "emulator" memory leaks are very difficult to diagnose. Only solution is to try a different configurations (hardware/software), or a different version of your favorite emulator, or a different emulator. This special sub-forum has discussion on emulator options. If none of the above is your problem? Sorry was unable to help. Try Google? They have thousands of links to different solutions for solving graphics display issues in Bluestacks, and a few hundred for Memu/Droid4x. Miscellaneous Additional Notes: Occasionally, some COC or emulator software versions have more sensitivity to low memory conditions: Not ALL versions of SC or emulator release work properly with MyBot.run. SC is constantly pushing non-mandatory updates. Android emulator software is constantly being updated. Developers do best they can to adapt to changes, but some versions may have weird unexplained problems without a solution. MyBot.run staff gets the new software the exact same time you do. Hence, the very latest updated version of XXX not work without changes to bot code. So do not update versions without checking forums. Suggest everyone turn off automatic updates for CoC in Google Play Store. If you are having issues with Bluestacks; please use one of these recommended versions where we have most experience and know they work! Black Screen and Windows Server OS Issues: Windows Server OS do not natively support required OpenGL v2.0+ graphics libraries for Bluestacks to work properly. Windows Server 2008 will not run any Android emulators without a video card installed (that supports OpenGL). Windows Server 2012 requires either a video card, or that Hyper-V graphics emulation be installed in server OS. These server OS are most commonly found when using an VPS, and this OpenGL support issue only impact a very small number of users in community. You can use a freeware tool called OpenGLViewer from RealTech-VR to check if your OS is capable of supporting BS emulator. If you try to run Android emulator inside a Hyper-VM session on Windows server or Win 10, it might load; but you get similar unsolvable graphics issues due next item below. Black Screen and Virtual Machine (VM) or Virtual Private Server (VPS) Issues: Most all the virtual box based emulators (Memu/Droid4x) will not run inside a shared VPS/VM environment. This is because you are attempting to run a virtual machine (Android Emulator) inside another virtual machine (VPS). Besides BS, only one supported virtual box emulator (NOX - worst performing) is able to run inside an VM, due to it supporting use of Directx graphics drivers in VM, and supporting OpenGL based Android apps in emulator. It is not a recommended emulator, but it is only other one that runs inside a VM/VPS. How to troubleshoot these memory leak issues: (edit -added Feb 2017) Assuming you are knowledgeable on PC technology and software, it is possible to learn more about your memory leak issues. Most of development team uses "Process Hacker 2" tool as task manager to watch PC operation when tracing these issues. It helps to isolate where the memory leak happens (emulator or bot), and gain an idea of what emulator/Bot is doing at exact time that memory space grows. What we usually see is the emulator (HD-Frontend.exe for BS), or the AutoIt process running the MyBot.run.au3 file has resource requirements slowly grow. The resources should be stable. Meaning after ~30 minutes of operation; the resources used should stay about same forever. If you find the memory, or GDI handle counts growing forever; then you found a leak. Once you have the leak, things get much more technical quickly. Average person can only try switching hardware/software components to fix. If you are knowledgeable in AutoIt, you can start adding debug code to help isolate where the leak is being created, and maybe develop fixes. Note - This can take weeks/months to find these leaks, and test fixes. Some leaks inside emulator programs, can not be solved by you. Bot On!

Dec Update: Bluestacks versions below v3.0 have known compatibility issues with latest Windows 10 and Windows Server 2017 OS updates. 2017 Windows 10 OS "creators" update that is finally being rolled out to most PC worldwide. This update force enables HyperV emulation, and this is not compatible with Bluestacks v1 or v2. Compatibility information is available on Microsoft or Bluestacks support web sites. If you disable the new HyperV setting in control panel (and prevent latest virtual desktop features from working), BS v2.5 can be used on some Windows 10 PC. If you can not disable HyperV emulation, then you need to use BS v3+ on Windows 10 2017. It is possible to force BS versions prior to V2.5 to run with 2017 Windows 10 creators update, but it requires several permanent changes to system registry and other system setting changes (not recommended for typical PC user or PC being used for more than farming). Windows 7/8 users can continue to versions 0.10.7 unrooted, v2.2 and v2.5 described below. For all versions, SC game update sometimes require Google Play Store, Google Play Games, or Google Play Services updates to work properly.. Make sure you have latest versions in Play Store! Here are some notes on various Bluestacks versions for reference: -- BS v0.9.X - Not recommended Used by many community members. No reason to upgrade unless you have issues with Google Play Games and "Gamer ID". Has many reported problems with Google Play games and Google Play services auto app updates. These require you to remove/reinstall CoC app and Google Account with every major update. Since the October 2016 game update, this version now has issues randomly crashing game and returns to main BS home screen. -- BS v0.10.X - Recommended Windows 7/8 only >>> BS v0.10.7.5601 non-rooted Most older rooted BS versions crash since Oct 2016 update, but original version can be downloaded from FileHippo and is running fine for most community http://filehippo.com/download_bluestacks_app_player/64518/ Non-rooted version does require manual removal of free download games advertising. Just Disable 'App Sync' & 'My Bluestacks' Apps (Disable Option Is in AppInfo) To Remove Bluestacks Ads" or follow the instructions here > http://druss.co/2015/06/how-to-remove-bluestacks-ads-sponsored-apps-popup/ While BS is spamming older version BS users with messages to upgrade, and even forcing automatic updates to latest version; v0.10.7 is best emulator for running a single emulator on your PC. Fastest, lowest resources, and is heavily used by community with great success. Has had some minor issues with Google Play service updates not being applied properly and Google Play Games "Gamer ID" failing to operate. Unless you understand process for fixing app version compatibility issues, most problems with this version are solved with simple removal & installation, install latest Google Play Games, and the install latest CoC. -- BS v2.0.X - Not recommended for new installations >>> BS v2.0.2 rooted ALL versions of BS prior to latest v2.2 are being spammed with upgrade notices. Most stable version found by MBR community is v2.0.2. The rooted version available in our forums was created by a Russian user and has some minor language/keyboard settings that are easily to change, and it works well. Most of Google Play games updates experienced with v0.1.X are gone with this version. Requires more system resources and users of old Core Duo CPU report minor lag issues. A portion of community have reported that this rooted version has same CoC app crash as all v0.XX versions. -- BS v2.1X - Not Recommended for new installations ALL versions of BS prior to latest v2.2 are being spammed with upgrade notices. Most stable version with spam free download found by MBR community is v2.1.7. Some Win 10 users report lag issues with all 2.0.X versions is lower using v.2.1.X. I recommend you download spam free native BS installer for v2.1.7.5658 linked from XDA site: http://forum.xda-developers.com/wiki/BlueStacks_App_Player Look in table of BS versions for v2.1.7.5658 and it has a download link. Then use the instructions in this thread using BS Easy to create your own de-bloated & rooted BS: https://mybot.run/forums/index.php?/topic/15318-tools-auto-root-any-bluestacks-remove-ads-08103096-to-2185663/ This process is not hard. But, There is no shame in admitting that creation of your own rooted version of BlueStacks is too complicated for you to accomplish. You can use any recommended version. Update: The newer v2.2+ versions of BS2 fix internal bugs with app compatibility, and bot has been taught how to better control them. -- BS v2.2.X+ - Most releases up through v2.5.XX have been tested to work better on Win7/8 systems - may not work for every hardware configuration. All version of BS after v2.1.8 included 2 different virtualization engines in program. They have legacy mode for older PC, and new virtualization engine that is using Oracle Virtual box technology used by some of newer emulators. New virtualization engine allows BS to have multiple apps open in separate tabs (in halt state when hidden - not useful for bot), and quickly switch between them. Development team has been in constant update mode trying to deal with v2.2+ BS and fact that is installs/behaves differently based on users hardware configuration. Many users of i3/i5 CPU prior to Gen 4 hardware are having issues with new virtualization support, and get errors such as BS is stuck trying to start up. One of our long time top contributors has posted rooted v2.2.27.6431 & rooted v2.4.43.6254 in this forum. So if your PC is less than 2-3 years old; one of these versions may work well for you. Note: It appears the newest versions of BS are now setting a default Android DPI of 240 in registry. The bot image detection is trained with standard DPI setting of 160 used on older versions. You need to check registry and edit/remove this new setting as discussed here. -- BS v2.5.X+ - Supported on Windows 7/8/10, Recommend v2.5.43 All recent versions of BS 2.5.x should work. A copy of BS v2.5.43.8001 rooted can be found here: https://mybot.run/forums/index.php?/topic/23339-rooted-bluestacks-25438001/ MBR v6 had some issues controlling latest BS2 versions. Since V7 release these have been resolved and BS2.5 works well with bot. The v2.5.43 has fixed most of the installation issues on older PC where wrong virtualization mode was selected, and run well on older or resource limited PC. All above BlueStacks Versions: Will need to apply registry fix to stop BS phoning home and forcing auto update without your approval. https://mybot.run/forums/index.php?/topic/19107-tool-remove-bluestacks-shared-folders-stop-spam-in-taskbar/ Just remember to run BS and add your Google ID after installation AND before applying the reg file to make sure BS initializes correctly first. If you modify the registry values before BS is fully installed, it will get stuck forever at blue loading screen and you must reinstall. -- BS v3.X+ - Supported (actually based on BS v2.10.X) BS v3.X version seems to be based on BS v2.10.X and does work. Though, DPI must be validated and manually set in Windows Registry to 160. See HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BootParameters and find the DPI=xxx value and change xxx to 160. Full reboot with HD-Quit.exe required! Also, the Launcher is missing - so just install Nova Launcher using "ADB install" on the downloaded APK and all is good. Existing manual ads removal doesn't seem to work - for me this one did: 1. Launch adb shell using HD-Adb.exe or adb.exe 2. Within shell call /system/xbin/bstk/su 3. Then call pm block com.uncube.account Having Problem choosing which version? Read this thread: What is best emulator? Best Luck.

Bluestacks (v0.9.XX to v2.18 tested) has 2 bad behaviors that most users desire to change. 1) Bluestacks is constantly sending web requests to Bluestacks servers checking for updates and also sending time and app usage data home. Recently, many users of older versions of Bluestacks are receiving tray messages that V2 is available or even messages that versions prior to BS 2.0 are no longer supported and will be disabled. :This behavior can be prevented by changing IP address of BS servers to local host 127.0.0.1, so BS can longer phone home. 2) By default, Bluestacks always adds shared folder links inside registry to enable apps inside BS to access several of your shared folders. These folders include "My Documents", "Pictures", "Public Pictures", and Public Documents". If your BS is rooted than you are exposing these shared folders to any app running in BS. This represents a potential method for SC to find bot users, and ban them. : We can stop this behavior by removing path location to shared files so they are not available inside BS. The attached registry editor file corrects both these bad behaviors. >>> BlueStacks Registry Security Fix update06032106.reg Mirror link Here Mirror link2 Here Simply download, and from an account with administrator access, double click to run file, then reboot PC to have it active. It will permanently fix the BS bad behavior unless you reinstall or update BS. If you are paranoid and want to see exactly what file is changing, right click on file and select edit. Hope this helps! PS - have tested on a couple Win7 PC, should work for most other OS, but I can provide any support if it does not work on your PC. You can easily open file with edit to see keys edited, and find those same keys your BS installation. [Update June 3, 2016] Several users that already have been infected with forced update message from BS servers, suggested an addition to reg file to remove problem. File has been updated to remove information on update. Best Luck!

This thread is for users to post information after receiving ban notice from SC for using 3rd party software in violation of TOS while using MyBot.run. Note : ANY post that does not meet requirements below will be removed and poster will receive a forum warning. NO EXCEPTIONS!!! This thread is NOT a discussion thread. Anyone asking questions, or discussing ban notices will be warned, and post removed!! 1) Must include screen shot of PC desktop showing full emulator window, and MyBot.run Window! - Suggest you use Windows "Snipping Tool" available on the "Accessories" folder of start menu, but you can use any screen capture tool to grab image - Can not post images directly to forums, so you must use a image hosting site like imgur.com to upload your image and post link in your post. Your desktop image should like something like this: (Your emulator/bot window may be different.) 2) Include in your post answers to following questions (can cut & paste text below, then add your answers) Date received Ban notice Which version(s) of the bot did you use in last few weeks prior to ban notice? (official release, or MOD, specify version please) [Update] Which Emulator are you using? (BlueStacks, Memu, Driod4x, Nox & Include version #!) [Update] Have you ever bought gems? [Update] Which version of Clash are you using? [Update] How many devices is your Clash account used on? Which devices are they? What army composition was used? (goblin, BARCH, GiBARCH, etc) What attack search type were you using? (Dead only, Live only, Dead/live, or Dead/Live/Bully/TH combo) If you were attacking live bases, which attack type did you use? (1, 2, 3, or 4 sided; DE Side, TH Side, or Milk Farm) Did you use Scripted Attack feature? (yes/no, please list name of CSV script used FF, 8F, GoWiPe, AQWalk, etc) Did you have smart attack enabled for conventional attack types? (yes/no) If so, were you using drop near collectors? (yes/no) What was your attack delay unit? (1-9, or random) What was your Wave delay (1-9, or random) [Update]How much time per day did you use bot (24/7, or how many hours?)[Before ''Fair play'' news and after ''Fair play'' news] How much time per day did you manually play game? Were you in a clan? (yes/no) Were you in a clan specifically known for bot use? (yes/no) Did you use modifications of CSV files or other game files for CoC app inside Android emulator? (yes/no, and list type: Low GFX, auto zoom out, show traps, etc) [Update] Do you have other game modifications or TOS violating software like xmod or imod installed on your device since Fair Play notice started? (yes/no, if yes which one?) ^^^^ Answer yes even if you did a regular uninstall of xmod. It leaves files even after an uninstall. Have you EVER posted a picture of your base (even with name/clan blurred out), an attack log, or the number of resources you had in clan chat, bot forums, reddit, SC forums, etc.? Does anyone who knows your base name/clan know that you're using the bot? (yes/no) If you have a SC forum account, does it use the same IP/email as your clash account and have you admitted to using the bot or been banned on it? (yes/no) Do you have any prior violations of the ToS (offensive language, offensive base design, etc.) THIS IS NOT A DISCUSSION THREAD - DO NOT MAKE ANY POST THAT DOES NOT CONTAIN YOUR PERSONAL BAN NOTICE!!! Additional rules for this thread: - Do not post YOUR BAN notice unless you used MyBot.run farming software AFTER April 2016 "Fair Play" warning from SC. Bans are not supposed to be for retroactive bot use, so we do not care about any ban prior to April "Fair Play" news from SC. - Do not ask for more information from user posting ban notice! - Do not ask for settings data that may not be included by banned users! - Do not post asking community for settings that may lower risk of ban! Any post that is not a ban notice following guidelines in #1/#2 above from a MyBot.run user will be removed. Any User violating rules for this thread will receive a forum warning! Please follow guidelines above when posting. MBR Staff does not enjoy spending our time reading invalid posts, or giving warnings to users for not following rules. History: Due low past risk of using MBR we have created this thread to track if users are being targeted and to document our Bot use risk. Prior to April "Fair Play" notices from SC, there have been approximately 5-6 MBR users posting they received SC Ban in over one year of MBR available for download. All but one past user receiving a ban admitted to using other "high risk" bots, or discussing bots in clan chat. An example thread for previous ban information can be read here: https://mybot.run/forums/index.php?/topic/13535-just-got-31-day-ban-on-coc This past ban data translates into 6 out of 330000+ registered users, or less than 0.002% probability of getting banned (prior to April). In truth, Probability of ban was actually lower if allow for number of bases using bot software, as most users have bot working on more than 1 base. MyBot.run is considered a 3rd party program and violates SC CoC TOS. Any one using MBR software assumes all risk for using program. Your acknowledgement to accept this risk can be found on "About US" tab of Bot user interface. [Updated April 26 2016 23:30] Thank you for sharing your data on Bot use after receiving a SC ban. Following trends were found in data collected during initial wave of ban notices: Banned for "Using Game MOD's" = 27/29 [Includes xMod/iMod/CSV game file MOD] Banned for "Excessive CoC play time" = 2/29 [only unique data point was playing more than 12 hours per day in 24 hours prior to ban] Recommendations to avoid ban have been and will continue to be updated in "Fair Play" thread based on data collected. Bot responsibly and Clash On!