OSBot version number: 2.3.77

Description of the bug/error:

Following methods:

 

Inventory#interact(..)

Equipment#interact(..)

 

will get stuck if the correct tab is not already open. Prior to 2.3.77, the client would realize that we're (for example), not on the correct tab to interact with an inventory item, and then open the inventory tab first.

Instructions how to replicate the bug/error:

use an interaction method from the Inventory/Equipment API classes, with a different tab than the correct one open.

(IF APPLICABLE) SSCCE that causes the bug/error:

N/A

(IF APPLICABLE) Script name ran causing the bug/error. Optionally include relevant parts of source code:

FrostBarrows

(IF APPLICABLE) Screenshots:

N/A

Do you know if it's failing to switch tabs or not recognizing that you're not in the correct one? I'll try looking into it myself this weekend.

Do you know if it's failing to switch tabs or not recognizing that you're not in the correct one? I'll try looking into it myself this weekend.

 

My guess had been that the tab check isn't being executed anymore, perhaps within MouseDestination (?), since I'm fairly certain that tab-switching in general works fine.

 

But I'm not really sure

Edited July 1, 201510 yr by FrostBug

Can confirm.

 

The script will just try to click the item in the inventory while the equipment tab is open.

So I guess the check has been changed/removed.

 

I just rewrote some script to manually open the required tabs and it works fine.

 

Khaleesi

Edited July 1, 201510 yr by Khaleesi

I don't recall removing the checks but I'll certainly look into it. Thanks for bringing this to my attention.

So yeah.. I don't see anything about this in .78 notes; so I assume it's still under investigation?

So yeah.. I don't see anything about this in .78 notes; so I assume it's still under investigation?

i gave up and decided to add in the check myself

i gave up and decided to add in the check myself

 

Same, but I've now for the 3rd time found another rare-case piece of code that'll get stuck because of this. When you have more than 70 classes in a script, it's annoying having to read thru every piece of it, judging if anything could break because of this bug

There are plenty more cases than just Equipment#interact and Inventory#interact

 

Alek if you don't have time to be doing this atm due to education or work or whatnot, could you please relay it to @Zach ?

Edited July 7, 201510 yr by FrostBug

I believe Alek is still looking into it, but is this something that started being a problem in .77? Or was it also present somewhere between .74 (stable) and .77 (stable)?

Looks like the code hasn't existed for quite some time, added the feature (back in?) for version 2.3.79.