Butters

You probably logged in when the morning ban wave hit. No way this is cause of new OSBot version. Btw thanks for the update. This is just a nicer version of this right? bank.getWithdrawMode() == BankMode.WITHDRAW_NOTE

for (int i=0; i< 28; i++) { if (inventory.isItemSelected()) break; Item item = inventory.getItemInSlot(i); if (item != null && item.nameContains(Constants.ITEM_NAME)) { inventory.interact(i); if (i == 27) Utils.condSleep(5000, 20, () -> inventory.getItemInSlot(slot) == null); } } A rough solution to your problem Pay attention to the if (inventory.isItemSelected()) break; part + What Shudsy say. Deselect item if it's selected before doing shift dropping

Very interesting to see that most of the experienced scripters, who I believe wrote preety complex scripts don't fancy the Node or Task based designs. Though in my mind it is true that for simple scripts there's no need for it, but if you're making anything that might have the word "progressive" or needs to scale eventually - I don't see how liverare's example would make my life easier. What I love about the node design that, if done properly, it scales easily and most of the classes are reusable.

As I mentioned before - OSBot blocks all external dependencies and correct me if I'm wrong. As someone mentioned you can extract the source of the external jar and place it in your script - should work but might be messy. I gave up playing around with this when I noticed that even simple JSON parser jars are blocked

As far as I tried, OSBot blocks external dependencies (jars), like jdbc or whatever else. Correct me if I'm wrong. To bypass this you can either do calls via POST from your script to something which will parse your data, or can communicate via sockets to an external program.

How did you "dismiss all randoms" actually?

Yep I noticed this as well. The problem is that the script itself works fine (does other stuff apart walking), though the listeners are basically dead.

Running only one additional thread regarding stat gathering and communication to a outer program. This really shouldn't be the case

Most likely you're using Java 9 and OSBot only works with Java 8. Open a terminal and type java -version if it says something like java version "9" Java(TM) SE Runtime Environment (build 9+181) Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode) You need to uninstall it and install java 8. Alternatively you can point to java 8 directly (if you have several java version installed) when launching osbot from terminal "C:\Program Files\Java\jre1.8.0_131\bin\java" -jar "osbot 2.4.147.jar"

Sold precious coins

Has anyone else had the probem when OSBot listeners sort of stop working? Having issues with MessageListener (onMessage) and LoginResponseCodeListener. Gonna be a little vague here and can't post source of scripts, cause they're preety big. Situation: I've put a log message at the start of onMessage just to monitor this behaviour public void onMessage(Message message) { log("Messages are ok!"); /* Other code */ } After the bot runs for about 30~ minutes, I stop getting the output "Messages are ok!" to terminal. At the very same time LoginResponseCodeListener stops working properly as well, eg (simplified code, using a variation of Explvs login handler): public final class LoginEvent extends Event implements LoginResponseCodeListener { @ Override public final int execute() throws InterruptedException { if (getClient().isLoggedIn() && getLobbyButton() == null) { setFinished(); } else { login(); } return random(100, 150); } @ Override public final void onResponseCode(final int responseCode) throws InterruptedException { if(ResponseCode.isDisabledError(responseCode)) { log("Login failed, account is disabled"); banned = "Y"; setFailed(); return; } } Usage: LoginEvent loginEvent = new LoginEvent(); execute(loginEvent); I end up never getting the response code and etc if the account is banned. There are sleeps that wait until the event is finished or failed and it seems that the event never finishes. That is lloginEvent.hasFinished() || loginEvent.hasFailed() doesn't return true, though the event already did what it supposed to do. Looks like onResponseCode() doesn't get called at all. The reason I'm asking is cause my other scripts that use basically the same code (and yes I checked an rechecked) don't run into this listener issue. Nothing special happens when the listeners stop working. I monitored carefully and it's just "poof" - no more message from onMessage(); I'm also using WalkingEvent and WebWalkEvent explicitly throughout my code. (other scripts I run have less of these): WalkingEvent walkEvent = new WalkingEvent(); walkEvent.setPath(s.toBankPositions); walkEvent.setBreakCondition(Utils.getPathBreakCondition(s)); s.execute(walkEvent); It works fine. Might it be that some events are blocking others? Basically I'm asking this: 1) More knowledge on how events work on OSBot. Might it be that some are blocking others, can't finish and etc and how to combat this if this is the case. 2) Anyone else had similar issues?

Sold precious coins

So need to run OSBot constantly and check account status. This little bit won't compile on it's own and switch accounts constantly Anyway lol I can sell you some if you want

Show me 5 lines of code and I'll give you a pancake. But yeah it's easy. Though still eats a lot of time and little profits. I stash my own accounts for later, being happy that oh boy I have a good reserve and then sometimes after two a few days Jagex plays dirty and bans them all

The actual pain to check if they're locked and selling at 50k each ... What do you expect

Sold precious coins

As basically everyone has said before - yes you can make 300$ a month and actually way more if you use the right stuff. The problem is that it is very unreliable. Best option I reckon would be to invest in knowledge and find a better job. For example you can try to write your own scripts here on OSBot, bot at the same time + learn Java. Bam. Could possible later apply for a junior java dev if lucky.

Sold precious coins

Sold some shinnies

Sold some shinnies

Sold shinnies

There are already AIO versions. Check SDN. I dunno if they're finished or not. If you stick with basic functionality without a ton of failsafes it shouldn't be too hard, apart skills like slayer.

Sold shinnies

Tbh love to see the old logger back. Thanks What exactly changed in quest API if I may ask? I remember quest.isComplete() and etc methods sometimes didn't work properly.

This is great, thanks