(05-06-2015, 12:17 PM)fxfire Wrote: if it closes the game exactly 3-5minutes after you started it, then your computer/game/bot was not able to authenticate aka send and receive a signal to and from our authentication server. This is usually the case when you are behind some weirdo / not proper setup proxies / VPN / shitty internet connection or have some really hardcore wannabekeepyousafe firewall/antivirus installed.
In order to not have each time such a thread about AV stuff, we therefore explain in the install guide to only use MSE for Windows 7 and the default defender antivirus for windows 8. Everything else is out of our control.
What you said makes sense, but what doesn't make sense is that it seems this issue only comes up when starting the bot from the launcher (hitting the 'Start' button). If you start the game yourself and then hit the "Attach Bot" button and supply the process it works just fine. From my understanding both ways need authentication and will ask for it accordingly. But what doesn't make sense is that one way will authenticate (if that is the issue) and the other will not. What really doesn't make sense is that I haven't had any issues at all with how my stuff is setup until the patch the other day. I was running it for a solid week without issues. I have been posting on here about the same issue these other people have been having but I keep getting told its basically my fault that it doesn't work. I'm in the same boat as the other people; I don't have a crappy internet connection, I closed/uninstalled all conflicting apps, I reinstalled/downloaded the bot again and still the same issue. But like I said, I can run the bot just fine by attaching it to a pid, but I cannot get the bot to get passed the 'frozen time hit' error when starting from the launcher. It seems weird that one way works, but not the other yet my (our) systems aren't configured correctly