Token

Bids noted, thanks

I'm not in a rush to sell it.

Nope.

Bid noted, thanks

Script is down after the recent client update. It will be back up when the SDN updates.

Lol Bid noted, thanks

Sure. I'll auth you when it's back on.

It will only buy the items you don't have the required amount or more in your bank + inventory. It's not Demon Slayer not working, it's all quests. The script stopped working since the release of the .65 client yesterday and will not work until the SDN updates. If you feel something is not working though and it's not related to the OSBot client I would appreciate if you could write a bug report with as much info as you have. Bug report template can also be found on the first post:

They already get notified when I push the updates, if I put more pressure on the development team they will just ignore the updates. I'll talk to @Maldesto to see if there is something that can be done about that though.

I'll post when it gets updated. It can only be seen on a private script page on the SDN.

Try looking at the ConditionalSleep class, which you should use until the dialogue box is open. A static 1000 ms sleep will not always guarantee that this opened, a simple lag will cause it not to appear within 1 tick (600-630 ms) which will result in typing in the chatbox. You can also replace those mouse moves and clicks with a right click on a WidgetDestination and then select a menu option via the Menu class.

Script is down again until SDN updates. They released the .66 client to undo everything that was broke in .65. There is nothing more that I can do other than to push updates and wait for them to approve them since the broken code is in the client itself.

SDN just updated. Let me know if you are having any issues with the new dialogue system. The Golem is also available on the GUI.

A pack of condoms that don't expire

When the devs update the SDN. It can happen at any moment, they don't really have a fixed schedule. It usually happens once a day so most likely in a few hours.

Got 61m bid in PM from @iroll

I know, that's for most NPC dialogues. I figured out there must be lots of widgets than can be considered dialogues since it's written in the API that inDialogue() uses colors.

Bid noted, thanks Got 60m bid in PM from @JMS

It was, I already wrote a bug report on it like 4 hours after the release. It always returns true. public boolean inDialogue() { return widgets.isVisible(231, 2) || widgets.isVisible(217, 3) || widgets.isVisible(219, 0, 0) || dialogues.isPendingContinuation() || dialogues.isPendingOption(); } That should work until it's fixed. PS: the actual problem is completeDialogue() which calls inDialogue(). There's a while(inDialogue()) in there, the bot will be stuck forever if you call this.

Bid noted, thanks Bidding ends in 12 hours

Bid noted, thanks

Bid noted, thanks

As far as I know it gets stuck when attempting any interaction. The new client version was shipped with a broken dialogue class which causes an infinite loop whenever its called. I believe they attempted to fix the inDialogue() method which someone reported that it sometimes returns false when in a dialogue. It will now return true forever. I wrote my own version of those methods though, because it may take weeks before they update the client again, and the script should resume functionality when the SDN updates.

Bid noted, thanks