As of 12:52AM October 22, the bot issue has been fixed. Apparently, a third party host obtained my warden address(idk how) and used my warden to access my comp. My comp was like, "bitchslap" and data execution prevention closed down BNLS Warden. Since Warden is pretty important to the function of bots, this caused the bot to disconnect every 2 minutes, and then log back in again every 90 seconds. To prevent this from occurring again, I changed my Warden address, and placed both BNLS warden and GHostOne in the data execution prevention exceptions list. Of course, this means that people can use my warden to access my comp, but I intend to change my address regularly now, since it's only the push of a button basically.