March 19, 201411 yr Pretty much every day I wake up to see my bots logged out with the following message from Runescape: "Login limit exceeded too many connections from your address". Is there anything I can do to stop this from happening? Edit: Oh, and this was happening to me even when I was botting only 1 account. Edited March 19, 201411 yr by Deffiliate
March 19, 201411 yr Author maybe it is a warning. besides that they may have macbanned. idk. nahhhhh Homie.
March 19, 201411 yr Try going to random.dat in the folder that the osbot folder is in and change it to read only.
March 19, 201411 yr Author Try going to random.dat in the folder that the osbot folder is in and change it to read only. Just checked it, the folder was already read-only.
March 19, 201411 yr Just checked it, the folder was already read-only. Dude this happens to me too! It starts to get really tiresome when your trying to test, then suddenly D/C, then "Login limit exceeded!". I only run one account, and if I click login two or three times it will eventually log me back and not have anymore issues...
March 19, 201411 yr Author Dude this happens to me too! It starts to get really tiresome when your trying to test, then suddenly D/C, then "Login limit exceeded!". I only run one account, and if I click login two or three times it will eventually log me back and not have anymore issues... Yep, exactly man XD. Is your Java version up to date? I've been procrastinating on updating mine so maybe that is the problem? Edited March 19, 201411 yr by Deffiliate
March 19, 201411 yr Yep, exactly man XD. Is your Java version up to date? I've been procrastinating on updating mine so maybe that is the problem? Yea it should be completely up to date, just checked last week for a different reason. I really have no clue what causes it, but I feel as if it's only when a script is running most of the time, not all of the time, just most. Because after the client fails to log in three times, and stops the script; I can usually manually click login once, and it loads just fine.
March 19, 201411 yr Author Yea it should be completely up to date, just checked last week for a different reason. I really have no clue what causes it, but I feel as if it's only when a script is running most of the time, not all of the time, just most. Because after the client fails to log in three times, and stops the script; I can usually manually click login once, and it loads just fine. I don't think the script running has anything to do with it either, it just so happens that the script is running when the problem occurs. It's more likely to happen while your script is running because I doubt you play for hours straight legit. Anyways, if you see it when it happens you either have to wait a couple minutes b4 logging in or switch world to log in. Would be nice if OSBot could make it hop world when it gets that message.
March 19, 201411 yr I wonder if they're checking # of connections per IP. How many bots were you running?
March 19, 201411 yr I don't think the script running has anything to do with it either, it just so happens that the script is running when the problem occurs. It's more likely to happen while your script is running because I doubt you play for hours straight legit. Anyways, if you see it when it happens you either have to wait a couple minutes b4 logging in or switch world to log in. Would be nice if OSBot could make it hop world when it gets that message. Usually I only have to click login a few times, and it usually sorts it self out. I haven't had to switch over yet, but I do agree this isn't script side, something client side because I don't experience this anywhere else. I wonder if they're checking # of connections per IP. How many bots were you running? Like we both said in earlier post, only one bot. I personally know I'm the only one in my area playing this game too, so there shouldn't be one or more connection anywhere near my house.
March 23, 201411 yr This sometimes happens to me, it's usually when the servers are laggy I think, and it goes away after 5 minutes or so, but scripts stop after 3 failed attempts to login.