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.6.4 RELEASED!   10/25/2018

      MyBot.run continues the legacy again with release of V7.6.4!!   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.6.4 Release

[Guide] What is Best Emulator?

Recommended Posts

40 minutes ago, zaha25 said:

Please tell me what emulator to download in order to work with latest verision of mybot

List of Supported Android Emulator
  Newer versions of Android Emulators listed here might work.
  The once listed here have been tested and do work.
  Versions,,,,,,,, 3.8.0.x, 3.7.6.x,, 3.7.5, 3.7.3, 3.7.1, 3.7.0, 3.6.0, 3.5.1, 3.3.0, 3.1.0, 3.0.0
  MyBot Command Line Key: Nox
  Default Instance Key: nox
  Second Instance Key: Nox_1
  Info/known issues/bugs: Only in low computer screen resolutions and when Android Window doesn't have android screen size of 860x732
  due to different window size, MyBot resizing fails for any version. Bot set Nox to fixed size to avoid any resize issues.
  Since 3.3.0 Nox support also DirectX that can be used for faster Screen-Capture. Newer versions since 3.7.3 support setting of
  framerates and 20 fps or lower significantly reduce CPU load.
  Versions,,,, 3.1.2.x,, 2.9.3, 2.9.1, 2.8.6, 2.8.5, 2.8.3, 2.8.2, 2.8.0, 2.7.2, 2.7.0, 2.6.6, 2.6.5, 2.6.2, 2.6.1, 2.5.0, 2.3.1, 2.3.0, 2.2.1
  MyBot Command Line Key: MEmu
  Default Instance Key: MEmu
  Second Instance Key: MEmu_1
  Known issues/bugs: **Newest versions , 5.3.2 or 5.5.5 doesn't work the _ControlClick with window not active
  Version 3.50.x, 3.7.x, 2.7.x, 2.6.x, 2.5.x, 2.4.x, 2.3.x, 2.2.x, 2.1.x, 2.0.x, 0.11.x, 0.10.x, 0.9.x, 0.8.x
  MyBot Command Line Key (0.8.x - 0.11.x): BlueStacks
  MyBot Command Line Key (2.x/3.x): BlueStacks2
  Default Instance Key: Android
  Second Instance Key (only for BlueStacks 3.x): Android_1
  Known issues/bugs: True Background mode using ADB not available for older versions (no ADB screencap & no ADB mouse click).
  ADB connection for BlueStacks2 can require one-time ADB daemon restart (initiated automatically by bot).
  ADB connection does interfere with LeapDroid default instance when running at the same time, review LeapDroid section to change ADB port.
  Versions 1.4.1055, 1.4.1049
  MyBot Command Line Key: KOPLAYER
  Default Instance Key: KOPLAYER
  Second Instance Key: KOPLAYER_1
  Known issues/bugs: None
  iTools AVM
  MyBot Command Line Key: iTools
  Default Instance Key: iToolsVM
  Second Instance Key: iToolsVM_01
  Known issues/bugs: Background mode only supported when iTools running in DirectX mode.
  Application is in Chinese and Android also. You can change Android language, but will not be saved.
  Tampering guestproperties and making the vbox VirtualBox file somehow read-only can work, see:
  Versions 0.10.6 Beta, 0.10.5 Beta, 0.10.4 Beta, 0.10.3 Beta, 0.10.2 Beta, 0.10.1 Beta, 0.10.0 Beta, 0.9.0 Beta, 0.8.7 Beta, 0.8.6 Beta
  MyBot Command Line Key: Droid4X
  Default Instance Key: droid4x
  Second Instance Key: droid4x_1
  Known issues/bugs: None
  http://www.leapdroid.com/, download available here: https://mybot.run/forums/index.php?/topic/22912-new-leapdroid-support
  Version 1.8.0, 1.7.0, 1.6.1, 1.5.0, 1.4.0, 1.3.1
  MyBot Command Line Key: LeapDroid
  Default Instance Key: vm1
  Second Instance Key: vm2
  Known issues/bugs: When docked, mouse outside bot window is not submitted to LeapDroid and if mouse state chances
  outside bot window when used for LeapDroid, mouse handling inside LeapDroid stops working, so be careful!
  ADB connection problems when mixed with other Emulators. Work-a-round: Close all LeadDroid instances at start bot again.
  As of version 1.5.0 only vm1 and vm2 support keyboard input, version 1.7.0 has that fixed.
  Window focus get changed a lot by LeapDroid, to fix this install custom qt4 libraries:
  Installation of BlueStacks and LeapDroid at the same time is not advised, as LeapDroid ADB device name is same as BlueStacks.
  You must change vm1 ADB port with command line, e.g. "C:\Program Files\LeapDroid\vboxmanage" guestproperty set vm1 adb_port 5510
  MyBot Feature & Functions Matrix (not complete yet!)
  Feature/Function | MEmu | BlueStacks | BlueStacks2/3 | KOPLAYER | Droid4X | LeapDroid | iTools AVM | Nox
  DPI Support* | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes (limited)
  Dock Mode | Yes | Yes | Yes | Yes | Yes | Yes, simulated | Yes | Yes
  Configure Android Screen | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes
  Configure Android Window | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes, unstable
  WinAPI/DirectX background | No | Yes | Yes, DirectX | Yes, DirectX | No | Yes | Yes, DirectX | Yes, DirectX
  AndroidScreencap | Yes | No | Yes | Yes | Yes | No, mem leak | Yes | Yes
  AndroidZoomOut | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
  AndroidClick* | Yes | No | Yes | Yes | Yes | No | Yes | Yes
  _ControlClick | Yes** | Yes | Yes | Yes | Yes | Yes | Yes | Yes
  AndroidClickDrag | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
  _PostMessage_ClickDrag | No | Yes, not used | Yes, not used | No | No | No | No | No
  AndroidSendText* | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes
  Feature & Functions Notes
  DPI Support*: DPI Awareness is available for all Android Emulators, but is different depending on the Android Emulator and background settings and dock mode.
  When Android is running in DPI Aware Mode (bot by default is running in DPI un-aware mode) docking and non background mode will turn bot also into DPI Aware
  Mode, resulting in smaller Window scaled at 100%. Also, when Android is running in DPI un-aware mode (e.g. iTools), docking will not change anything, only when
  disabling background mode.
  AndroidSendText*: Works only for ASCII Characters, most symbols, but no Umlauts etc.
  It falls back to WinAPI when unsupported characters are detected, but might fail also.
  If sending text is not working, keep it empty in bot and last entered text will be sent.
  AndroidClick*: Can be only enabled in config.ini, use adb.click.enabled=1 and adb.clicks.enabled=1


Share this post

Link to post
Share on other sites

hey there Friend im having trouble since the coc is updated i cant update it via memu, i tried many version, but it wont work can u pls help me with this this is my pc version what emulator with it be thx a lot

system version.png

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now