Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sto All buttom does not work if storage window is closed, but lists do #163

Open
brunoramoslu opened this issue Dec 25, 2021 · 3 comments
Open
Assignees

Comments

@brunoramoslu
Copy link
Contributor

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?

@pjbroad
Copy link
Collaborator

pjbroad commented Jan 2, 2022

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.

pjbroad added a commit that referenced this issue Jan 8, 2022
…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.
@pjbroad
Copy link
Collaborator

pjbroad commented Jan 8, 2022

I've made a simple change to make access more consistent,

@pjbroad
Copy link
Collaborator

pjbroad commented Apr 3, 2022

@brunoramoslu are you happy to close this one?

@pjbroad pjbroad self-assigned this Apr 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants