Token

Did you by any chance attempt to prevent OSBot's autologin? I remember discussing with lots of people about unregistering hooks.

What local scripts do you have in your scripts folder?

Fapping

I read lots of threads about keeping your accounts safe but no one ever suggested manually banking for your bots. That's kind of new I guess.

bot.setHumanInputEnabled(true); You won't find this in the API docs but it does exist.

Having java x installed is different from using java x to run programs. OSBot requires java 8 in order to run, and as far as I know, all linux distributions have java 7 preinstalled. After installing java 8 you have make it uses that one generally through "alternatives --config java" command.

What java version and update are you running?

Jagex is smert.

Your Script instance has a field called groundItems which you can use to access the whole collection of GroundItem instances currently available to your player as well as perform some other operations. For example the operation you mentioned is available to you in the following form groundItems.get(x, y);

Jagex bans lots of legit players, that's why mod weath's twitter was spammed.

Legit players manually botting get 2 day bans, the rest of us get permed.

I can quickly write some private scripts if you wanna do an exchange There's something I need and a purple @Scotty can obtain.

Scotty vip... something's definately on. What scripts do you need?

Walk of Shame

Your own ip.

I'm pretty sure all VPN's are flagged af, why would you consider botting on a VPN?

Yes something like that but the enum was Banks not Bank actually.

Walking: walking.webWalk(Bank.EDGEVILLE); Opening: bank.open(); Deposit: bank.depositAllExcept("Fly fishing rod", "Feather");

OMG new shitbox assistant. Unban me from the shitbox luv PS: Mia Khalifa, Sasha Grey and Kim Kardashian

Well, good luck with that but that I don't think the server kicking you out is a randomly defined behaviour so you may be able to study the case and find a workaround for that. But if you really want to dig into this when the API is up again, you could take a look at the LoginResponseCodeListener as Script implements that, so you have the onResponseCode(int) method in there which might help you define a behaviour when you get the response "too many login attempts" or "no reply from the login server".

Yes it might work, I'm not sure as I've been advising people to do this for months on the forums, haven't actually had to try it myself. No one told me it doesn't work so I guess no news is good news. Just wondering though, why would you try to login and fail on purpose?

Yes it disables the autologin and I believe the tries are internal to the login hook. Re-registering the hook from a parallel thread might do the trick.

RandomExecutor.unregisterHook(RandomEvent.AUTO_LOGIN);

Are you using static variables?

The API does not provide any method to obtain information about the npc you are in a dialogue with at any given moment. There are 3 methods you can use to determine the npc although all of them have exceptions. 1. Get the npc you are interacting with (easiest) myPlayer().getInteracting().getId(); Works when you click on the npc and your player starts moving towards the npc as well as for 1 tick after each response from the npc. You could use this to determine the id before the actual dialogue. 2. Find the npc that is interacting with you (least reliable) npcs.getAll().stream().filter(n -> n.getInteracting() == myPlayer()).findFirst().get().getId(); The npc should be interacting with you for 1 tick after each response from you. The main issue here is that other people might attempt to start dialogues with same npc leading to undefined behaviour. 3. Extract npc name from dialogue widget and then search for the npc (most reliable) npcs.getAll().stream().filter(n -> n.getName().equals(widgets.get(WIDGET_COORDINATES).getMessage())).findFirst().get().getId(); Where WIDGET_COORDINATES represents the ids of the npc name widget on your dialogue interface. The only drawback of this method is that you can only obtain the id of the npc once they are the ones talking. You can also filter the npcs using the API Filter class if you don't like lambda expressions: npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC n) { return n.getInteracting() == myPlayer(); } }).getId(); That's pretty much all you can do with the API right now, the main issue being that npc interaction is not a continuous thing, at least not for dialogues. It is continuous for instance if you are safespotting an npc and that npc keeps trying to reach your player but they can't. In this case, that npc will be interacting with your player. But anyway, there is absolutely no need for the npc id you are in dialogue with so we don't really have a method that provides that 100% accurate result.