Token

Estoy muy castana. El señor @Scotty es mi gran castana personal. Me gusta muchísimo este señor @Scotty. Siempre voy a apoyar a @Scotty para el veterano. Siempre he tenido una buena opinión sobre el señor @Scotty. Desde que lo conocí, él probó a sí mismo como un líder capaz. Vivo señor larga @Scotty.

Well the script is in a continuous development, but that will take some time.

There are generally 2 ways to filter the NPC/Objects/GroundItems collections. 1. Using OSBot Filter interface NPC monster = npcs.closest(new NameFilter<NPC>(NAME), new AreaFilter<NPC>(AREA), new PositionFilter<NPC>(POSITON), new ActionFilter<NPC>(ACTION)); You can add as many filters as you want in the above expression. There are some other classes that inherit Filter and can be used but you can also create your own. Filter<NPC> levelFilter = new Filter<NPC>() { @Override public boolean match(NPC n) { return n.getLevel() < 30; } }; NPC monster = npcs.closest(levelFilter); Which will find only NPCs having a combat level under 30. 2. Using Java 8 streams NPC monster = npcs.getAll().stream().filter(n -> n.getName().equals(NAME) && AREA.contains(n) && n.getLevel() < 30).findFirst().get(); These offer more flexibility but you will have to check the Optional returned by findFirst() otherwise you will get a java.lang.NoSuchElementException, so I advise you to use the OSBot Filter.

Yes.

An update has been pushed for the latest .58 fixes if anyone is wondering, lots of things were changed in the client. The .58 has been out only for a few hours but I noticed while running it myself that there is an error in webwalking.

The prequests are on the to-do list, Monkey Madness itself is not yet. It will eventually be added because it's a useful quests and has lots of continuations but not in the next updates.

I'll add it as one of the first quests in the quick start options, the bot will do quests with like 25 HP this way which should make it a lot safer.

Clock Tower Murder Mystery Tribal Totem Elemental Workshop I (starting this series) Hazeel Cult Witch's House If nothing goes wrong in the testing phase I need these quests to continue the RFD series.

Biohazard is not in tomorrow's update but maybe next week when I will most likely continue the Ardougne quest series (because indeed there is a huge demand for these, I guess Zulrah?).

Alright, thanks. I guess jagex modified configs so old accounts don't really have the same configs for that quest... It will be fixed when SDN updates.

No, the script doesn't kill him either. Someone told me about this a few weeks ago and I couldn't reproduce the bug. I think jagex modified some configs on that quest but I'll upload something that should fix it. Did you complete Fight Arena in 2016?

Did you kill General Khazard?

When did you complete Fight Arena?

If you use the quick start option for RFD yes it will attempt to do Waterfall Quest if you don't have it done. You can manually add the RFD quests on the 2nd tab and set your own gear if you want to go straight to them.

Yes the quick start option contains Waterfall Quest in order to get attack/strength levels for 2 of the RFD subquests. The quick start options are optimised for completion of these quests on fresh accounts. Eg: the NMZ/Pure option starts with Witch's Potion and Imp Catcher and will complete Lost City/Fight Arena/Vampire Slayer using earth strike, thus it can be ran on lvl 3 accounts.

Yes, the first version of this script had 18 quests in beta. Now it's at 31 and will have 37 tomorrow as I'm adding 6 new quests. Did this bug occur on mirror mode? What quick option did you run?

Authed Are you running it on mirror mode? What messages are printed in the logger?

Transparent background is better

Thanks for the report. I've pushed an update for this new bug. Until the SDN updates tonight I recommend you only use 1 bank tab.

Has this issue happened before the last runescape update?

Thanks for the report, is this tab issue happening only since last runescape update?

Pathing is handled by OSBot's webwalker which doesn't use predefined paths since february when they were improved and completely randomized. Dialogue spamming has 2 causes: the latest webwalking code fails to handle links properly in some cases resulting in looping through dialogues, or mirror mode dialogue hooks failing (they are unstable) which I have had a report on for over 2 months. All of them are implemented at API level and are not a local script issue. This answers the 2nd dialogue issue: http://osbot.org/forum/topic/94170-mirror-mode-dialogueswidgets/ There is nothing wrong with dialogues in this script as the dialogue code is entirely based on the Dialogues class in OSBot API. There has not been a ban report ever since beta launch in february.

Authed

sex