RyanNZL Posted April 7, 2014 Share Posted April 7, 2014 Well today i logged in and i got dced and instabanned. Is this jagex detecting the OSBOT client, or is it from my previous botting? Mabye a player reported a while back Could anyone shed light on what gave them enough evidence to just ban me right there and then..? Quote Link to comment Share on other sites More sharing options...
Bjergsen Posted April 7, 2014 Share Posted April 7, 2014 same happened to my main months ago. Quote Link to comment Share on other sites More sharing options...
RyanNZL Posted April 7, 2014 Author Share Posted April 7, 2014 did you get an appeal though? Obviously this account is more of a throwaway, young account. Quote Link to comment Share on other sites More sharing options...
Proto Posted April 7, 2014 Share Posted April 7, 2014 might be they caught on to you. Quote Link to comment Share on other sites More sharing options...
Jordy Posted April 7, 2014 Share Posted April 7, 2014 are you aware of what world your in at all times? Quote Link to comment Share on other sites More sharing options...
RyanNZL Posted April 7, 2014 Author Share Posted April 7, 2014 I'm not in 385/386. I was mining at ardy. I logged in for the first time of the day into a specific world and then i was dced and banned. So was this the mere fact they were "On to me" or the fact that their detection system picked up OSBOT client? I'm trying to figure it out. If they were on to me why wasn't i banned prior to logging in? Why did it take me logging in to force the ban? Quote Link to comment Share on other sites More sharing options...
NotoriousPP Posted April 7, 2014 Share Posted April 7, 2014 You have already been caught, and they just waited to implement it; it's called a delayed banned. It happens quite often. Quote Link to comment Share on other sites More sharing options...
RyanNZL Posted April 7, 2014 Author Share Posted April 7, 2014 So why would they delay it? Quote Link to comment Share on other sites More sharing options...
shankfish Posted April 7, 2014 Share Posted April 7, 2014 They definitely didn't catch the client itself, it was a delayed ban no doubt Quote Link to comment Share on other sites More sharing options...