BETA v1.4.5

[iGotLube]

Thanks for the update

[GoldenGates]

Thanks, made life a bit easier. :P

[Kezman]

Download link seems to be down, click on the link and get the "Sorry, we couldn't find that!" message

[Lucy]

Thank you Maxi

waiting for the randoms now  

[arravs]

Thanks.

[yoyodo3]

After complaining about a lack of random support a second ago Its good to know that there is actually someone who is working on anti randoms.  This would put osbot on the top of oldschool botting if it can become flawless.

[bida]

  On 5/14/2013 at 1:37 AM, yoyodo3 said:

After complaining about a lack of random support a second ago Its good to know that there is actually someone who is working on anti randoms.  This would put osbot on the top of oldschool botting if it can become flawless.

 

agree with you 100%.  if it can be solved( i mean most of anti-randoms or even all)  then OSbot will be #1  bot of all 07 bots.

[Abuse]

I can confirm that openTab() is still broken (partially)

One time it works, other time it doesn't

 

Any chance of giving us the new api methods list? (Just general ones, out of your head)

 

Regards

Edited May 14, 2013 by sleziak

[runescaper1992]

thanks for the update, appreciate it. Btw you can manually add anti randoms to your osbot scripts and they run automatically. OSbot is dope already lol.

 

Edited May 14, 2013 by runescaper1992

[yoyodo3]

  On 5/14/2013 at 9:04 PM, runescaper1992 said:

thanks for the update, appreciate it. Btw you can manually add anti randoms to your osbot scripts and they run automatically. OSbot is dope already lol.

I've added the anti randoms from the compilation on the anti randoms section but the ones that were said to be working don't work..All we have to do is put them in our script folder right?  Freaky forrest,Sandwich lady,And the Pin ball randoms all still stop my bots every time.  Hopefully a perfected anti random system is being worked on because i Compiled all of the ones available now and they don't work for me.  

[beef]

RS2Object object = closestObject(int);

 

 

Was once working for me, now it will never get the object I'm try to interact with.

 

I've got a workaround at the moment, using

list = closestObjectList(int);

RS2Object obj = list.get(0);

Edited May 15, 2013 by beef