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

XP Decreases Despite Piece Already Having Been Upgraded #249

Closed
Monkey-bored opened this issue Mar 1, 2024 · 0 comments · Fixed by #284
Closed

XP Decreases Despite Piece Already Having Been Upgraded #249

Monkey-bored opened this issue Mar 1, 2024 · 0 comments · Fixed by #284
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Monkey-bored
Copy link
Collaborator

Monkey-bored commented Mar 1, 2024

Describe the bug

After you upgrade a piece you still have the upgrades tree of the original piece open and you can click on the same upgrade which will cause your xp to decrease for no reason

Steps To Reproduce

  1. Gather XP
  2. Upgrade a piece
  3. Click on the upgrade again

Expected behavior

You should not be able to buy the same upgrade more than once on the same piece and you should only be able to upgrade a piece once per turn.

@Monkey-bored Monkey-bored added the bug Something isn't working label Mar 1, 2024
@Monkey-bored Monkey-bored added this to the 0.2.0 milestone Mar 1, 2024
@Monkey-bored Monkey-bored self-assigned this Mar 1, 2024
@Ido-Barnea Ido-Barnea changed the title You can upgrade a piece twice XP Decreases Despite Piece Already Having Been Upgraded Apr 6, 2024
Monkey-bored added a commit that referenced this issue Apr 7, 2024
@Monkey-bored Monkey-bored linked a pull request Apr 7, 2024 that will close this issue
Monkey-bored added a commit that referenced this issue Apr 7, 2024
…e-already-having-been-upgraded

[#249] Fixed upgrading piece twice bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant