Butters

Thank you all. Any best practices to combat obstacles universally if walkPath would misclick or something (eg. enter a building whichs' doors get closed) ? Use DoorHandler or something similar?

try doing this: chmod +x /home/customer/desktop/bot.jar If that doesn't work post what you get after trying to launch osbot here

Hey, was wondering if any of you could provide details and key differences on webwlalking, walkpath and walk. Main concerns are: * Does walkPath handle obstacles * Does walkPath use less cpu and ram than webwalk

Still happening to me in 1.4.138. I think it has something to do with osbot threads. Seems like loginEvent doesn't always fire when it's logged out. Pausing and resuming the script helps.

Same for all, wait it out. Something wrong with OSBot servers

All fine and dandy, though sucks that mules can't launch

Did exactly that. Failed. Will try to mess around again later, thanks

Thanks, I do know what they are, but I failed to get that POST request to inspect. As I mentioned - a noob

I'm a noob at this, might want to share the POST params/screenshot? Failed to catch that pesky POST

To be honest I'm liking this not for the script, but for the "opportunity" to see how to code properly in general. Beautiful work

Need to pm Jagex with something like "Hello I'm a botter and I've found a bug in the client while making mass tutorial accounts"

This really gives me a headache. OSBot likes to eat quite a few resources during launch. Depending on the CPU power you have, I can launch about 18-20 bots with 60+ second sleeps without a problem. As the CPU usage spikes later bots tend to fail producing the error mentioned. So I started monitoring cpu usage and extending the sleep time if needed.

Widgets ID's didn't change (still 269). Seems like the customization screen is active for a shorter time and auto closes after like 5-10 seconds.

Lol thanks, dunno if this is a joke or not, but wanted an automated solution So as I see there's no "straightforward" way doing this, will try the methods you guys mentioned, thanks.

Anyone else have a problem that it not always logs back in after being logged out due inactivity or just before bans? Happens like 30% of the time. Pseudo usage: int onLoop() { if (client.isLoggedIn()) { doStuff(); else { execute(loginEvent); } } Just stays logged out. Pausing and resuming the script helps

I didn't find any method regarding this. Would like to do this without trying to hop to a p2p world. Maybe there's a config for it?

Pass in your main class to the method as a prameter where you want to use System.out then. Then do ParamName.log();

Use log() instead of System.out.

Actually a good question, I was using Status.PENDING_BUY or Status.PENDING_SALE after aborting a sale/buy. But works kinda funky.

sold 141m, went first

nah it was running, you just didn't see the output, cause you didn't add the -debug flag.

Once again I might be wrong, but through my trial and error I think OSBot launches a new process after it's login screen. This means you can say bye bye to all the output afterwards. Use java -jar osbot.jar -debug 5011 Or any other port. This will pipe the output. Also, if you're new to this install a Graphical environment and VNC to just play around.

Use this. Might need some tweaking to suite your personal needs but works well. I seriously doubt you'll have problems with "color detection" when running a VPS without a graphical interface. Correct me if I'm wrong

Using CLI. java -jar osbot.jar -allow norandoms This will also disable autologin. Also I think you can disable it in options when running from GUI if that's what you need

Thanks a lot! Maybe have a list of all the response codes?