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

Loot screen continue button issue #7

Closed
JayL1F3 opened this issue Mar 21, 2018 · 4 comments
Closed

Loot screen continue button issue #7

JayL1F3 opened this issue Mar 21, 2018 · 4 comments
Labels

Comments

@JayL1F3
Copy link

JayL1F3 commented Mar 21, 2018

Occasionally while fighting a monster and looting it, on the second loot screen the continue button will sometimes do nothing.

Occasionally clicking an arrow will cause no feedback. Number does not increase or decrease. Reload is necessary.

@Amvoled
Copy link

Amvoled commented Mar 21, 2018

I noticed too that sometimes buttons stop responding.

I however have a clue as why the button on the loot screen do nothing sometimes. This happened to me when my inventory was full after a fight. This may have to do with the fact that the total loot is too much for the space left in your inventory. Since the popup tries to take every item, but you have not enough place, nothing happens.

The solution would be to add a "Leave this here" button so you can leave some loot or other objects from your inventory.

@nroutasuo nroutasuo added the bug label Mar 21, 2018
@nroutasuo
Copy link
Owner

Renaming this to reflect the discussion on the loot screen & making a separate issue for the arrows. Will look into fixing both.

@nroutasuo nroutasuo changed the title Couple things Loot screen continue button issue Mar 21, 2018
@iuriguilherme
Copy link

This particular bug is annoying because sometimes a page refresh will mess up the progress if it hasn't been properly saved.

I think I can reproduce this behaviour whenever I end up in a combat after scavenging at least once in a cell.

@nroutasuo
Copy link
Owner

This has now been fixed in master and the fix will be in the next update. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants