You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
You cannot use chests nor some items if they are near walls with borders on top. For some unknown reason entering the wall allow you to use the item. The problem seems to be related to #5 since when I click the item it tries to click in the border of the mountain in the above ground.
Also, you cannot use look in the item.
-> This also happens in v8 otclient <-
To Reproduce
Steps to reproduce the behavior:
put a usable item near a wall like this
put a border in the mountain above like this
Try to click the item, it will give you the message to go upstairs first.
Problem in the look:
1.
Expected behavior
It should click the item and not the border that is in the upperfloor. Strangely when I enter the wall (the client don't draw the upper part of the mountain) it allow me to click in the statue
Environment
Latest of this repository, but also applies to many variants and also v8 otclient
10.98
Any
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
You cannot use chests nor some items if they are near walls with borders on top. For some unknown reason entering the wall allow you to use the item. The problem seems to be related to #5 since when I click the item it tries to click in the border of the mountain in the above ground.
Also, you cannot use look in the item.
-> This also happens in v8 otclient <-
To Reproduce
Steps to reproduce the behavior:
Problem in the look:
1.
Expected behavior
It should click the item and not the border that is in the upperfloor. Strangely when I enter the wall (the client don't draw the upper part of the mountain) it allow me to click in the statue
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: