Current Bug/glitch list:
Below are some major bugs which needs to be fixed ASAP:

 

1) Osbot doesn't work proper on linux or mac:

People receiving the following error:

[ERROR][07/11 06:27:28 PM]: Uncaught exception!
java.lang.NullPointerException
at org.osbot.COm2.iiiiiIIIiI(ab:58)
at org.osbot.cOm8.run(rc:36)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744) 

 
2) Banking:

A. The scrolling of the bank doesn't work at all, it's not even scrolling.
This makes scripts which need some advanced banking impossible to function.
 
B. Dragging of the scrollbar, the client will drag the bar around the locaiton the item is in, but it never goes far enough, making the items visible for around 50-70%, which doesn't let the withdraw click the item. Which results in probably a bann if you got stuck like this for 3-4 hours.

 
3) Interfaces:

Some of the positions of the interfaces are a bit off.
For example: the childs of the skillTab are shifted over pretty bad.

 
4) Inventory selected item:

I assume the client is useing the left top message to check if an item is selected in the inventory,
BUT when you have an item selected and you hover your mouse over the tabs around the inventory the message will disappear.
Meaning that the client thinks there is no item selected while there is.
 
Pictures selected and hovering tabs:

Mouse not on tabs, Working method:

Mouse on tabs, text in left top disappears, Not working method:

 
Inventory#deselect()
This just clicks the inventory tab I assume, the problem is, when you hover the mouse to the inventory tab to click it afterwards, it won't click it.
Reason:client thinks there is no item select, thats what i said earlier and can been seen in the images.
This is making some of the script freak out.
 

 

5) Noted grounditems:

GroundItems#getName() doesn't work proper.

Which makes looting noted grounditems a pain.

 

Pictures of an unnoted item dropped and a noted item dropped + code:

Unnoted Pure essence:

 

Noted Pure essence:

 

Code used:

 

 

 

6) Random event Inventory full:

Randoms that require an inventory slot are broken if the player's inventory is full and the last item's drop option is "destroy".

The random handler will keep trying to drop the item, find that there's no "drop" option, and repeat until it breaks and enters a login/logout loop, which is obviously a really easy way to get banned.

 

 

 

If I forgot any bugs you came across, please post it in this topic so we can keep track of it!
This means only bugs caused by the client. (not scripts)

Edited July 13, 201411 yr by Khaleesi

Very good list. I'll post some when I get them  These problems are probably among the biggest ones that should be worked on.

Ty, will probably be a week before anything is done though, I haven't even used OSB2 once yet due to constant errors.

I've posted it before, but since I have no idea whether it was fixed since the last update, randoms that require an inventory slot are broken if the player's inventory is full and the last item's drop option is "destroy". The random handler will keep trying to drop the item, find that there's no "drop" option, and repeat until it breaks and enters a login/logout loop, which is obviously a really easy way to get banned.

Gives me this error, have to restart the client every time I want to run a new script.

(And I'm using proxies)

 

[DEBUG][07/14 12:21:03 AM]: Loading script id : 486

[ERROR][07/14 12:21:04 AM]: Error downloading remote SDN script id : 486

Looting noted items has always been an issue, even with OSBot 1.

 

You can do a quick workaround by simply finding the item by using it's ID (noted of course, it will be detected) and interacting with the position of the item with the action "Take".

Looting noted items has always been an issue, even with OSBot 1.

 

You can do a quick workaround by simply finding the item by using it's ID (noted of course, it will be detected) and interacting with the position of the item with the action "Take".

 

No one wants to get the ID. Most people don't even know how.

 

Gives me this error, have to restart the client every time I want to run a new script.

(And I'm using proxies)

 

[DEBUG][07/14 12:21:03 AM]: Loading script id : 486

[ERROR][07/14 12:21:04 AM]: Error downloading remote SDN script id : 486

 

Sounds like a connection problem.

No one wants to get the ID. Most people don't even know how.

http://www.runelocus.com/tools/rs-item-id-list/

 

??????

http://www.runelocus.com/tools/rs-item-id-list/

 

??????

 

Which isn't 100% accurate lol.

Which isn't 100% accurate lol.

Please show me where it is incorrect :p

Please show me where it is incorrect

 

It takes just way too much time,

The bug could be solved and people would not spend hours to get the ID's fo 50.000 items -_-

If you want, you can add to the list that getting "height" of RS2Object is sometimes not working, noticed this when checking height of a rock, after it was mined, it's height changed to 0, and stayed that way.

 

[iNFO][bot #1][07/14 04:48:45 PM]: Height: 0 | Position: [x=3181, y=3377, z=0] | ID: 6820

When in fact, the height is ~~ 60.

bank.depositallexcept return true when there is still item that need to be deposit.

usally its the last iventory slot that it doesnt recognize 

How about ummm..breaks?