Token

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

Click a door 30 times during tutorial island -> instaban.

I have lots of friends who have acne and have been prescribed accutane. All I heard from them is that it's a very hepatotoxic drug. Most of them have cholesterol and liver problems after 3-6 months of treatment. I also had acne for over 2 years but I've never been prescribed accutane. I eventually found a doctor who would perform laser treatments for acne and went through 7 BBL (blue light) and 4 Thermoscan treatments. They are much less invasive and also seemed to work for me. All I can tell you is that acne has no cure. It will last until you are ~30, you can't stop it but you can control it. PS: Working out raises your testosterone levels, this is not caused by bodybuilding supplements. It is a normal consequence of working out but will be very severe if you decide to take steroids.

Most likely premium. That's not only up to me though.

I'll try to fix it. I initially tested it on lvl 3's as it's supposed to work with 10 hp. The beta unfortunately had to end yesterday, but the script will be available soon.

I hope it's going to be up by the weekend... but it's not up to me.

Unfortunately, I was told a few hours ago that the beta will have to come to an end and the script will soon be reviewed for public release. You can try it after the release if you want. Thanks to all beta testers who helped find bugs and suggested a few improvements. The first public version of the script should be up in a few days.

Authed

Authed

Lol. During which part of the quest did it die?

Authed

Thanks for the report. I've got an update pending on that, should be fixed when SDN updates.