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
A clear and concise description of what the bug is.
Continuing an Attack or Evade when the monster is fully damaged causes unintended behavior. This leads to the finished or cancel button in the subsequent actions to not be able to be clicked which means the monster has to be defeated to advance which can be frustrating if accidentally clicked.
Steps to reproduce the behavior:
Click on any monster.
Increase their damage to the full capacity of the monster
Click on Attack or Evade while the monster's health is full
The Cancel Button or Finished button is grayed out, inactive.
A clear and concise description of what you expected to happen.
Either prevent an attack or an evade from happening when the monster's health is full or activate the button when the monster's health goes below maximum value.
Screenshots
Valkyrie Version
2.5.6
The text was updated successfully, but these errors were encountered:
Using the new methods in UIElement, the buttons have been refactored to be inactive to solve issue NPBruce#1560 if the monster's health is fully damaged. This will prevent some unintended behavior going forward, but more work will be needed in other scripts to prevent this.
A clear and concise description of what the bug is.
Continuing an Attack or Evade when the monster is fully damaged causes unintended behavior. This leads to the finished or cancel button in the subsequent actions to not be able to be clicked which means the monster has to be defeated to advance which can be frustrating if accidentally clicked.
Steps to reproduce the behavior:
A clear and concise description of what you expected to happen.
Either prevent an attack or an evade from happening when the monster's health is full or activate the button when the monster's health goes below maximum value.
Screenshots
Valkyrie Version
2.5.6
The text was updated successfully, but these errors were encountered: