Isolate

Same, only updated a few hours ago though. Ruined my progress report of multiple ore+ prioritization

Version 33 quit my script upon logging back in. made it to the lobby page and then quit the script. No error logs

Question: can a bot only update the to version 1 above it? Reasoning: I was just running .31 waiting for a proggy for not that long then it only just about 30 mins ago popped up to update to 32 so i did straight away then the moment i ran that one it told me to download 33

nope.

u wot m9

You'd break the rules.

RS2Object thing = objects.closest("Blah");

This 'clamp down' is somehow going over my head. since f2p was released i've botted 3-4 accounts non stop without breaks... I dont know if its the nature of the accounts or what but its missing me

Appart from the riskyness of the sleeps its a clean file :P and thank-you

No offence but i am impressed that this can substantially run Because if one little thing is out of time, a fraction of lag, a miss click, this would fall to peices Please use if statements, and interfaces

I don't understand the purpose of what this does. please explain a case where this would be used

It hasn't been march this year :'(

of last year?

oh his signature

u wot m9 Sorry i cant hear you over the sound of this picture i just took ;)

Self written one, 27 mins til i finally hit 24 hours

Mad gainz.

http://osbot.org/forum/topic/65861-precise-aio-cows-banking-3-locatons-4-methods-power-fighting-any-food/ http://osbot.org/forum/topic/65873-project-pacts-cow-killer-death-walk-amazing-paint-stats-flawless-easy-start/ I swear.

lies

You used to have the little bald cartoon kid ava? :P

Botre is back!?

Ooo some of these made me remember you! Great work!

add a sleep after the button interaction and why isn't Script.sleep(Script.random(800, 1600)); //--------------------------------------- s.sleep(Script.random(800, 1600)); like the rest of them?

Use of a filter would be appropriate here A filter is a way of it only accepting a entity if it meets all the criteria. Currently your only criteria is for the entity to be named "Cow" which, even with the checks underneath will still find any cow at all. The only reason you dont attack one whilst fighting is because of some of the checks underneath. Your check in filter form would look like: NPC cow = npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC npc) { return npc != null && npc.getName().equals("Cow"); } }); Which checks would return the same but you only want to find a cow not in combat so you'd need to add more checks NPC cow = npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC npc) { return npc != null && npc.getName().contains("Cow") && !npc.getName().contains("Dairy") && !npc.isUnderAttack() && npc.isAttackable() && npc.getHealth() > 0; } }); This check checks for the name, and would allow inclusion of the little cows but excludes dairy cows after it has identified the fact its a cow it moves on to check: Is the npc under attack? is the npc able to be attacked by your player? is its health > 0? (avoid clicking on cows which are dying) you can add as many checks to this as you like. Sorry if my explanation is bad