thelegacy0

Works perfectly after this update. I've done probably 4k alchs since it was updated, my lastest being a 2 hour stretch and it stopped after running out of alchs. Next time I'll try to get a screeny, but I'm not rich enough to stack up 10k alchs ;P

Strip it to the very basics and see if that works, then work on adding if visible and attackable and stuff. Like, this is all my fighter has: int fighting() { if(!myPlayer().isUnderAttack()) { NPC npc = getNpcs().closest("Guard"); if(npc.exists()) //add loop for finding attackable ones npc.interact("Attack"); else this.stop(); } return 1000; } Start with just attacking, then work on finding out if they're attackable and stuff. Use enums, don't having everything running in your onLoop(). My fighter has eating, teleporting, and attacking and is 75 lines long, finished

I know, right? I even added a TL;DR :P

Just say "I use a third-party client to track my xp/hour. I am a hardcore skiller (or if you're doing combat, just say you like to know how long to the next level, etc), and physically seeing my numbers is such motivation for me. If this is a problem, I will receive punishment but don't be too harsh on me, as I am just ambitious!" If they come at you with physical evidence of botting, oops! Otherwise, how're they to tell you're lying? Jagex is pretty lenient if you're "honest". One day I noticed my membership renewed when I didn't want to. I was over 24 hours into my "next month" of my subscription. I messaged them, said this isn't what I wanted, and they cancelled my membership and refunded the monthly fee. They're nice to their honest, dedicated player, because they don't want to lose your business. TL;DR - My client is for XP tracking, not botting, release your own tracker or leave me alone

Have you guys considered adding a timer for being stuck in a random, so you log out and close the script?

I was looking on the SDN, I guess I should clarify why there aren't any there. Yeah local scripts are probably a dime a dozen with these. Is OSBot just not pushing them or something?

Auto clicker would definitely get you banned due to the camera never moving, and never having random delays. The sleep you use depends on a few other things, and the time I'm using seems universally perfect. It might skip here and there, which is good, because that's what you want. But anyway, alching stuff is really easy to write because it's just left click. The antiban just needs to include: camera movement, random clicks, sometimes skip an alch (like wait 5 seconds), and sometimes look away from the screen, so anywhere from 10 to 120 seconds of inactivity. Not the best exp/hr (I'm getting over 1k alchs/hr with random 3-14 second pauses maybe once per couple minutes) but it's still good for if you don't want to do it. To me, it just seems too easy to not have. That's why I want feedback, to see if I'm overlooking something.

On the SDN, Why don't we have one? I understand that left clicking with subtle camera movements probably has a high ban rate, but seriously, it's not hard to write something up for human attention span... Does anyone have any legitimate reasons for it? I've alched 1k of 4k rune arrows with a script I whipped up... I'll keep toying with the human-like left-clicking powers every now and again, but I don't see why we don't have such a simple script.

if(client.getMyPlayer().isAnimating()) { if(smokingRock()) { //avoid that rock } } ^ In your loop public boolean smokingRock() { RS2Object rock1 = closestObject(15); if(rock1.getModel().getHeight() > 75) { //I THINK they start at 77... Change to 80 if you want if(client.getMyPlayer().isFacing((Character<?>) rock1)) { return true; } } return false; } P.S. in your code you'd want to check for the rock while animating... You have to rewrite your if statements, so that it's if(not animating) click rock, else if(is animating) check for smoking rock. Know what I mean? Edit: if a cast doesn't work, you could try the interactWith boolean. Ents are easier cause they're npcs

There's a tutorial on it http://osbot.org/forum/topic/44536-smoking-rock-detection/?hl=smoking+rock Edit: tutorial is for while you're selecting what to mine. Might wanna change that/add that for when you're already mining.

Did you check the script's forum post and make sure it's up to date? I haven't died anywhere from 30/30/1 to 67/63/40

Twice now I've gotten stuck in the pillar random.. It picks all 10 correctly, but doesn't leave unless I move the camera to the exit.

This, please. I'm going to start adding things like this to my scripts that I want running for long periods of time. I think this got me killed yesterday =\ I noticed myself in Lumbridge, but the log showed several SUCCESSFUL randoms, so a not-recognized would do the trick.

1) 1.7.98 2) [ERROR][04/06/14 12:48:45 AM]: Error on executing script worker! java.lang.NullPointerException at org.osbot.script.rs2.ui.Bank.getItems(bi:38) at org.osbot.script.rs2.ui.Bank.getAmount(bi:83) 3) When checking bank for item, script crashes. Take out the getBank.getAmount(int) line and the script runs fine. This is all I took out - if(client.getBank().getAmount(#)> #) { And no, client.getBank().getItemForName(String).getAmount(int) does not work.

If you're saying it's an object that doesn't change, then checking the object name/ID would be rather useless. However, in the case of mining, I believe you receive a message saying the ore has run out? It's kinda nooby, but using onMessage(String message) can cover you until you figure this out, so you don't stagnate in your script.