happylittletree

It's not known if GGG checks more stuff on your pc like if you are running a VM or checking your mac locally (which is not too hard to code a check for) And even IF they check for VMs and flag them, they won't just ban you coz you are using a VM (benefit of the doubt and no real proof of botting) What they definitely do is monitoring low lvl accs. So if you bot for too long then you probably will get banned. It's easy to check online times for them tl;dr You are *most likely* at the same risk with or w/o a VM Note that the above is based on basic knowledge and educated guesses, most of it is NOT a fact.

I don't know your location but you can simply google it and look for reviews (user reviews as well as 'professional ones' for vpns with server in your location Apart from the fact that you are risking your main acc, nothing is gonna stop you from using a vm with your main. You can use the same ip (no vpn) and perhaps change the mac to match the one of your physical network card

Thats why you can set the bot to use movement skills when it gets stuck like flame dash, leap slam etc. That should solve problem #2 Regarding #1: my bot never runs out of ID scrolls. I set it to keep 80 of them and that's (so far) well enough. Issue #3 is indeed a pain in the ass and there is no solution yet, I really hope alk will implement some sort of walk around like [if mob with affix X do Z]

This is the main reason why we run VMs. I'm still not sure if GGG actually checks the mac (just assume they do) but as it was posted before you can easily change it in VMWare itself. This + a good vpn and you are relatively safe. What gets you banned in the first place is usually insane run times like 24/7.

That would be a really nice addition for the future. It doesn't have to be all the masters at once (I'd leave out Tora anyway), just the easy (to program) ones.

If it helps you to start out, you can actually monitor the output from the performance monitor if you set it up to monitor discarded packets. The specific powershell command would be Get-Counter.

or the bot killed I'm on the same page here. Good things take time

It might be possible relatively easy with powershell. Only if you are having packet loss on your end though. If the server crashes there is nothing you can do since no matter what you do on your end, their server won't register anything anymore since... you know, it crashed. This should disconnect you stright away anyway. Just google around. Powershell is quite easy to use, even with just snippets You definitely can exit processes through powershell, not entirely sure how powerful it is when it comes to network diagnosis but AFAIK microsoft added some stuff for it. EDIT: If you really wanna try it out and need some help with the scripting I encourage you to visit stackoverflow.com. There are many experts who can possibly help you with almost everything as long as you provide them with proof of your own attempts.

This may not be high prio. I think it would be quite helpful for some if the bot would have an option to manage the log files. Examples: x Split the logs after X MB or X Days ∟Keep last X logs (delete old ones) Also the option to view the log in realtime would be excellent for easier/faster troubleshooting. I.e The bot is not doing anything in camp. Quick view to logs says log is idling. All good. It might prevent some errors related to low spec machines (VM's etc) and it's just a nice to have feature. Again, this is by no means high prio. At least not for me nor for most ppl here I'd guess