welp, that didn't last very long lol.

 

What do you mean?

It's working

doesn't hop?

Awesome!

Opened it, pressed the + to add a tab, it just sits there and then eventually closes itself.

 

Got it to open.. now it just won't connect to server.  (I was logged on to it successfully, then it lost connection and I can't log back in thru the app)

Edited July 17, 201411 yr by skull burn55

After I press launch nothing happens.

Your shity bot got me perma banned and i was in the green zone and i was a 120 combat player in 2007 your bots suck nobody ever use them from here

Your shity bot got me perma banned and i was in the green zone and i was a 120 combat player in 2007 your bots suck nobody ever use them from here

Explain why I haven't got banned even though I have been running the bot 10h+ a day for the last 11 days? Just because you got banned doesn't mean the bot is shit. Botting comes at a risk and if you don't bot smart enough, you will get banned.

Your shity bot got me perma banned and i was in the green zone and i was a 120 combat player in 2007 your bots suck nobody ever use them from here

 

 

Explain why I haven't got banned even though I have been running the bot 10h+ a day for the last 11 days? Just because you got banned doesn't mean the bot is shit. Botting comes at a risk and if you don't bot smart enough, you will get banned.

 

Oh yea and not to forget that this is an outdated client, lol.

Your shity bot got me perma banned and i was in the green zone and i was a 120 combat player in 2007 your bots suck nobody ever use them from here

 

Have you considered OSBot 2?

I'm getting all these errors saying it can't access certain things, is there any way to stop this?

Sometimes I get this:
 

[INFO ][07/20/14 10:26:24 PM]: null
[INFO ][07/20/14 10:26:24 PM]: We don't have weapon, stopping!
[INFO ][07/20/14 10:26:24 PM]: Thanks for using my script, you have made 0gp in 0:00:38
[INFO ][07/20/14 10:26:24 PM]: Stopped script: DruidKillah

Even though I clearly have a weapon, other times I get stuff like this:
 

[WARN ][07/20/14 10:27:22 PM]: [T2] Attempt to access injected method [d.getId()] has been blocked!
[WARN ][07/20/14 10:27:22 PM]: [T2] Attempt to access injected method [d.getAmount()] has been blocked!

I'm seeing this with almost all of my scripts, and they are for OSBot 1.

 

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getName()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getActions()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getId()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getHeadIcon()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getModelIds()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getModifiedModelColors()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getOriginalModelColors()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getCombatLevel()] has been blocked!

[WARN ][07/21/14 02:42:40 AM]: [T2] Attempt to access injected method [as.getTransformIds()] has been blocked!

[WARN ][07/21/14 02:42:52 AM]: [T2] Attempt to access injected method [e.getName()] has been blocked!

Awesome job, thank you.!

Can someone please explain the warning of injections and whether we should be concerned ? I'm getting like 20 warnings a minute.

The warnings are no big deal. OSBot & OSBot 2 have the same protection against injection detection. That's why OSBot 1 now uses OSBot 2's loader. OSBot 1 simply is still printing the debug messages which I left in there months ago! I left them there because they were not being called as it depends on Jagex sending a specific packet to search for the methods of a class. The good thing is though is that they only see the code that THEY wrote AND NOT the code WE INJECTED. The debug mesages are kinda just showing off the protection feature by printing which methods Jagex COULD'VE DETECTED!

I however advise you to not bot on OSBot 1 any longer. Even though the random solvers may or may not work, I'm pretty sure the latest RS update broke an injector that OSBot 1 had for detecting the positions of interfaces/widgets. This will cause multiple symptoms of scripts failing.

 

I suggest for you to use OSBot 2. It's already proven more stable and has a better API.