cosote

Ups, sorry that we missed that. We need to review most other languages as well Greeting from Rosenheim - cosote.

Hi @forcocgame2, sorry for the late reply. The bot doesn't save the password anywhere - it's a token stored in a file under your user account profile ".mybot.run.authentication" under AppData\Roaming. Cheers - cosote.

Hi there, wired, I've installed 6.2.8.5 and all (except new focus problem with that version and brings Nox window to front when a text input is detected in Android) all works fine... Can you check where the BigNoxVMMgr.exe file is on your windows? And send be the output for cmd.exe command: set prog Cheers - cosote.

We had some forum issues last 2 weeks since June 12th bot authentication and most features are restored... still patching the rest next couple days... Let me know if it now works or if you still have issues Cheers, cosote.

Hi @darksider007, unfortunately we have missed to implement a backup system. While the forum is up again and authentication works, we are working on a backup system to prevent similar outages in future Cheers - cosote.

Please replace this file zipped TcpTable.au3 in update_TcpTable.zip and run bot with AutoIt3.exe... I could not reproduce the error, but that array problem is now fixed

Hi, starting with MyBot.run 6.3 beta8 Android Emulator iTools AVM is supported. Though it only supports Chinese, it's fastest and uses least RAM of all emulators I've tested so far. Homepage: http://pro.itools.cn/simulate/ Offline installer download: http://serv2_avm.itools.hk/dlavm?p=28&c=thinksky_ova Support version is 2.0.6.8, 2.0.7.9, 2.0.8.9 DirectX mode must be used for bot background mode support (hidden under 3rd settings option and click right button button to save ). Use this itoolsavm.cfg and DirectX and 860x732 is already set (usually located here C:\ProgramData\ThinkSky\iToolsAVM\itoolsavm.cfg). Unfortunately there is a beta8 bug (fixed for next release) that doesn't create iTools shared folder probably. To fix this problem in beta8: Open Oracle VirtualBox.exe and add the shared folder manually, name must be: picture the host folder doesn't matter, create it where you like Oracle's VirtualBox GUI is usually here: c:\Program Files\Oracle\VirtualBox\VirtualBox.exe Though Android is set to Chinese and changing Android language option is not persistent after reboot, you can change it with VBoxManage and make the vbox readonly. "c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" guestproperty set iToolsVM iToolsVM_vm_country US "c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" guestproperty set iToolsVM iToolsVM_vm_language en (Assuming you're with cmd.exe in iToolsAVM program folder) attrib +r Repos\VMs\iToolsVM\iToolsVM.vbox I've notices when launching the instance with the multi-launch tool (where you can create multiple instances), very often the language is still in Chinese. If so you my batch file below and let the bot launch the instance! Here my batch file iTools_config.bat (hosted on mega.nz) First parameter is the VirtualBox guest name of the instance and optionally you can specify a 2nd parameter number 0-9 to reset all forwarding ports. To patch the first instance, you simple call the batch (keep in mind you need to run with Administrator / elevated rights). To patch the second instance, call iTools_config.bat iToolsVM_01 1, the third instance iTools_config.bat iToolsVM_02 2 and so on. I also saw some installs of iTools that removed the system and readonly attribute again from the vbox file resulting in language changes did not stay in English... Wired, but you can tamper with the security settings on the file, assuming your cmd.exe is launched as Administrator, you can remove all user access from that file and keep only Administrator with full access and Everyone with Read/Execute/List etc. access. Then iTools cannot modify that file anymore... (batch files uses now this method) You must run the batch file as Administrator! Just wanna test English immediately (won't be saved!) ? Here the screenshots: Now, at least your Android is English iTools runs in VMWare! To enable DirectX mode for iTools in VMWare you just need to replace the C:\ProgramData\ThinkSky\iToolsAVM\itoolsavm.cfg with a version that has DirectX configured. Otherwise launching iTools will stop at 55% or so... You can download mine here: itoolsavm.cfg To get CoC running (when you have problems in the loading page and the bar stops in the middle), just download and drag&drop google play games apk and launch CoC again: com.google.android.play.games.apk com.google.android.gms.apk Cheers - Cosote. iTools AVM ========== http://pro.itools.cn/simulate/ Versions 2.0.6.8 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. Having Problem choosing which emulator to use? Read this thread: What is best emulator? Update 2018-11-25 iTools_config.bat updated to fix language settings by copying vbox file also to a temp name. Update 2017-03-26 iTools_config.bat batch file updated with fix for non English Windows and fix for shared folder. Update 2017-03-20 iTools_config.bat batch file updated with automatic admin elevation and fix for shared folder. Update 2017-03-19 iTools_config.bat batch file updated with fix of removing readonly and hidden attribute of instance file and adding also picture shared folder by default. Memory is set to 512 MB, 1 CPU at 100% (can be also used as 3rd parameter). Update 2017-03-18 iTools_config.bat batch file updated with more options and CPU is set to 1, 100% and checked readonly to security tampering rather r/s attributes. You must run the batch file as Administrator now! Update 2017-01-02 iTools_config.bat batch file added to configure language and optionally all forwarded ports (WARNING!!! It's a zippyshare download link, be aware of those stupid popups!!!). New version 2.0.7.9 has been tested and is working fine. If you upgrade, click the right button when you launch iTools instance(s) first time of this popup to upgrade you Android:

Hi guys, inspired by good old bananas fan @monkeyhunter, I'm consolidating here useful information about MEmu support of the bot. MEmu is best emulator for running multiple instances of MEmu and the bot at the same time. See a short overview of supported Android Emulators and additional tech. details Here All versions starting from 2.2.1 till latest 2.8.6 are support. Quite a few users report that 2.5.0 runs best for them, download here from filehippo. Latest can be always download from vendor site memuplay. Starting with version 2.8.0 or so, MEmuConsole.exe is frequently executed when MEmu is running to check instance state. This consumes significant computer resources. To fix this, simply rename MEmuConsole.exe to MEmuConsole_.exe or so. Using multiple android and bot instances required command line options for the bot. GUI configuration is in the making and hopefully available soon. "c:\mybot\mybot.run.exe" "My Village 1" MEmu MEmu starts bot with village names My Village 1 in MEmu using instance MEmu "c:\mybot\mybot.run.exe" "My Village 2" MEmu MEmu_1 starts bot with village names My Village 2 in MEmu using instance MEmu_1 (usually the 2nd clone/new emulator instance in MEmu) Be aware that new name displayed in the MEmu Window Title or MEmu Console doesn't need to show the correct instance name. To list all available instances you can use MEmuHyperv command line tool MEmuManage.exe you find in MEmuHyperv program folder "C:\Program Files\Microvirt\MEmuHyperv" or where you've installed it: MemuManage.exe list vms Also, good fellow @Fliegerfaust created a great documentation and launch tool for the bot to handle multiple instances and launched the bot with right command line parameters: Useful MEmu Links: Experiencing LAG issues with Memu: Improve Memu performance How to enable Hardware Virtualization( Performance Improvement): http://www.memuplay.com/blog/index.php/2016/01/27/enable-hardware-virtualization/ MEmu Official FAQ Page: http://www.memuplay.com/blog/index.php/category/faq/ Having Problem choosing emulator to use? What is best emulator?

Hi, I'm using LeapDroid for some time now with the bot and it's running very good. Just need to be careful in docked mode with the mouse... if you click, move and release the mouse outside the android client area, the mouse will "break" and manual reboot of LeapDroid likely required. Also, LeapDroid has a very bad behavior bringing the window to front very often. This steals the focus and is very annoying when you try to use the PC while botting. I've patched and compiled the qt4 library used by LeapDroid to fix that. Just replace the qt4 files in LeapDroid program folder and that problem is fixed Tested with LeapDroid versions 1.3, 1.4, 1.5, 1.6.1, 1.7.0, 1.8.0 qt4 for LeapDroid.zip (64bit!!!) qt4 for LeapDroid (x86).zip (32bit!!!) Also Visual Studio 2015 Libraries are required (link) Another super terrible behavior of LeapDroid is that it constantly tampers with the clipboard when images or related objects have been copied into it. LeapDroid replaces / removes those with "(" character !!! To fix this use command like (e.g. for vm1 instance): "C:\Program Files\LeapDroid\vboxmanage" modifyvm vm1 --clipboard hosttoguest It is not advised to run BlueStacks and LeapDroid with MyBot.run as ADB connections are difficult to get established for LeapDroid. Also, default LeapDroid ADB device name is emulator-5554 for instance vm1 and same as BlueStacks which causes MyBot.run problems. Then you must change ADB port in LeapDroid using command like: "C:\Program Files\LeapDroid\vboxmanage" guestproperty set vm1 adb_port 5510 Multiple LeapDroid instances can be created as documented here: Link LeapDroid project is now officially closed, but still one of the fastest around... here installation files of latest version 1.8.0 for 64 and 32bit Windows: LeapDroid 1.8.0 x64 (64bit) here: LeapdroidVMInstallerFull(1.8.0).exe LeapDroid 1.8.0 x86 (32bit) here: LeapdroidVMSetup32(1.8.0.0).msi Found a modded LeapDroid 1.8.0 here Having Problem choosing emulator? Read this thread: What is best emulator? Changes: Update 2019-02-12 Updated download links to qt4 libraries. Update 2016-11-18 LeapDroid has been purchased by Google, and has announced there will be no more updates and they are discontinuing all software support. We have no control on this new business development and it may force MBR to stop supporting LeapDroid at some time in future. But: MBR will continue to support current versions already supported while it remains possible. Update 2016-11-05 Added download links of latest original & untouched LeapDroid installation files. Update 2016-11-03 Add x86 build of QT4 (sorry, cannot test - please let me if it works ) Update 2016-10-31 Updated post about clipboard issue. Update 2016-10-03 LeapDroid 1.8.0 support by MyBot.run 6.2.2, automatic screen adjustment fixed in next release. Update 2016-09-28 New LeapDroid 1.8.0 not yet tested. Update 2016-09-27 Just realized that my qt4 files causes VirtualBox.exe GUI to crash... will check what's going on there till then you can copy the original qt4 files together with VirtualBox.exe and VBoxRT.dll into its own sub-directory and VirtualBox.exe will just run fine when launched from there :D... Happy botting - Cosote. LeapDroid ========= http://www.leapdroid.com/ 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: https://mybot.run/forums/index.php?/topic/22912-new-leapdroid-support/ 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