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
I found a weird behavior while using the android client (it also happens with the desktop client).
While making potions using the lists, and I closed the storage window.
After the storage window was closed I was still able get things from storage and put them in my inventory using the lists.
But when using the Sto All button, the button does not work.
The behavior seems to be inconsistent, but might be by design.
Could someone clarify or provide some input?
The text was updated successfully, but these errors were encountered:
Its by design so you can close the storage when just using the item lists. But I agree its not consistent for store-all alt-clicking an item. If we change to enable store-all alt-click, we will get "You cannot access store from here!" messages but at least that makes sense.
…dow.
Items lists can access a closed storage window if in range.
Now the store all button and alt-click an inventory item can
do the same.
Added sound and visual indication of when access is not valid
for the store all button as already done for alt-click and item lists.
Access is not allowed after changing map locations until re-opened
via and NPC.
Fixed an issue where the storage window could be re-opened after a
map change if using alt-d hide all window before changing and then
restoring after the map change.
I found a weird behavior while using the android client (it also happens with the desktop client).
While making potions using the lists, and I closed the storage window.
After the storage window was closed I was still able get things from storage and put them in my inventory using the lists.
But when using the Sto All button, the button does not work.
The behavior seems to be inconsistent, but might be by design.
Could someone clarify or provide some input?
The text was updated successfully, but these errors were encountered: