widget interaction buggy

[Tylersbored]

Does anybody else have bug problems when using .interact with RS2Widgets?

It is very hit or miss when they successfully perform the action for me. This varies from widget to widget, some are buggier than others. I have resorted to using .hover() to hover over the widget first and then getMouse().click(false) to actually press the widget. It works but just wondering if anybody is having the same issues or maybe I am using them wrong. If so, could someone tell me the correct process of using a widget haha. I perform null checks btw in case that has something to do with it.

 

[The Undefeated]

Could you give some examples on which specific widgets this happens?

 

[Tylersbored]

4 minutes ago, The Undefeated said:

Could you give some examples on which specific widgets this happens?

 

In the house options: "Call Servant","Building mode"

in the GE: "Abort offer","Collect"

[The Undefeated]

6 hours ago, Tylersbored said:

In the house options: "Call Servant","Building mode"

in the GE: "Abort offer","Collect"

Don't really have problems with them myself.

 

[Alek]

6 hours ago, Tylersbored said:

Does anybody else have bug problems when using .interact with RS2Widgets?

It is very hit or miss when they successfully perform the action for me. This varies from widget to widget, some are buggier than others. I have resorted to using .hover() to hover over the widget first and then getMouse().click(false) to actually press the widget. It works but just wondering if anybody is having the same issues or maybe I am using them wrong. If so, could someone tell me the correct process of using a widget haha. I perform null checks btw in case that has something to do with it.

 

The only difference between hover and interact is that hover doesn't click. hover() or setting it in interact, still uses the same core interactionevent.  Maybe a code snippet might help.

[Tylersbored]

2 hours ago, Alek said:

The only difference between hover and interact is that hover doesn't click. hover() or setting it in interact, still uses the same core interactionevent.  Maybe a code snippet might help.

could it also be that I am runnning my bots on low cpu? I heard that low cpu might cause some issues with hooks

Quote

 private RS2Widget servant;
 

servant = script.getWidgets().get(370,15);
        if(servant != null && servant.interact()){
            Script.sleep(Script.random(2000,3000));
        }

This is generally how I was using them before I switched over to using hover() instead. Do you have to grab widgets freshly before you use them? Also they must be visible right? Before you can call get() on them. I have also read in a different forum that hard coding the ids in order to find widgets is bad. Could someone point me into the right direction on how to find the widgets properly  thanks

[Alek]

Try calling something like:

bool b = servant.interact();

or

if(servant.interact())

Essentially we are checking to see if interact passed or failed on OSBot's end

[Tylersbored]

1 hour ago, Alek said:

Try calling something like:

bool b = servant.interact();

or

if(servant.interact())

Essentially we are checking to see if interact passed or failed on OSBot's end

I have done that as well, using a conditional sleep if the interaction succeeded. If the interaction failed I used the low level method of clicking the widget. It seemed to fail most of the time when I tried to use it but occasionally it would succeed