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

Only show # of poisons on enemy config if needed #5701

Closed

Conversation

deathbeam
Copy link
Contributor

Lock showing # of poison on enemy config option behind ifEnemyMult PoisonStack just like # of poisons on self.

Description of the problem being solved:

Config options should not be shown by default when they do nothing. The poison stack config option should only appear when there is relevant multiplier or condition it will fulfill.

Steps taken to verify a working solution:

  • See that config option is hidden
  • Equip wasp nest or use dagger mastery (or vile toxins)
  • See the config option appear

Link to a build that showcases this PR:

https://pobb.in/UrCgykdZKTSz

Lock showing # of poison on enemy config option behind ifEnemyMult
PoisonStack just like # of poisons on self.

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@QuickStick123 QuickStick123 added the enhancement New feature, calculation, or mod label Feb 19, 2023
deathbeam added a commit to deathbeam/PathOfBuilding-1 that referenced this pull request Feb 21, 2023
Same as PathOfBuildingCommunity#5701, this config option doesnt do anything by default and
should be shown only if there is check if enemy is bleeding or not.

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@QuickStick123 QuickStick123 added user-interface Changes that only affect the UI and removed enhancement New feature, calculation, or mod labels Feb 21, 2023
@deathbeam
Copy link
Contributor Author

#5712 in the end decided to include this change here

@deathbeam deathbeam closed this Feb 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user-interface Changes that only affect the UI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants