October 26, 201312 yr So i come back on looking at the events at the bottom of osbot, why did it do the login over 4 hours long, like seriously i died from a random and my character would log out from being inactive, and the bot would log in back. bot meter detector should be off the charts
October 26, 201312 yr Random Events have become increasingly broken. Wait for the next update (when the developers are active) or wait for the release of OSBot 2.
October 26, 201312 yr Random Events have become increasingly broken. Wait for the next update (when the developers are active) or wait for the release of OSBot 2. I lol'd
October 26, 201312 yr So i come back on looking at the events at the bottom of osbot, why did it do the login over 4 hours long, like seriously i died from a random and my character would log out from being inactive, and the bot would log in back. bot meter detector should be off the charts Is is because the bot is programmed to log in if you are logged out to combat any dc or 6 hour kicks. Unless the script explicitly stops itself, the client will continue to log in.
October 26, 201312 yr Author So i come back on looking at the events at the bottom of osbot, why did it do the login over 4 hours long, like seriously i died from a random and my character would log out from being inactive, and the bot would log in back. bot meter detector should be off the charts Is is because the bot is programmed to log in if you are logged out to combat any dc or 6 hour kicks. Unless the script explicitly stops itself, the client will continue to log in. Maybe thats the problem the script was still running;/
October 26, 201312 yr So i come back on looking at the events at the bottom of osbot, why did it do the login over 4 hours long, like seriously i died from a random and my character would log out from being inactive, and the bot would log in back. bot meter detector should be off the charts Is is because the bot is programmed to log in if you are logged out to combat any dc or 6 hour kicks. Unless the script explicitly stops itself, the client will continue to log in. Maybe thats the problem the script was still running;/ Then that is the problem.