Token

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.

Other.

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

If it was up to me the beta would still be running

Your own ip.

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

Lots of stuff that I'll have to go through to get it on the SDN publicly.

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");

Patience The problem is unfortunately more than a SDN upload.

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

It might take quite long unfortunately as it's considered quite an odd release.

Well... the beta is over but yes Waterfall Quest should be working properly on lvl 3's.

Cook's Assistant Imp Catcher Priest in Peril Druidic Ritual Dwarf Cannon Witch's Potion Romeo and Juliet Vampire Slayer Doric's Quest Goblin Diplomacy The Restless Ghost Sheep Shearer Rune Mysteries Jungle Potion Plague City RFD Cook Subquest RFD Goblin Subquest RFD Dwarf Subquest RFD Guide Subquest* RFD Ogre Subquest* The Knight's Sword Ernest the Chicken Animal Magnetism Pirate's Treasure Prince Ali Rescue Lost City Waterfall Quest Fight Arena Fishing Contest Gertrude's Cat Big Chompy Bird Hunting* Tree Gnome Village* Mountain Daughter* *Quests marked may or may not be featured in the first public release but they will be added in the first update. This depends on how stable the version will be. Not yet decided as it's not all up to me.

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.

I have always been wondering if resources get depleted faster the more people attempt to collect them. This made it all clear.

If it was up to me, I would have kept the beta going for at least 1 more week